It would be great if there was a way to create a metadata comparison filter, and not just filter with regard to metadata types, but also filter by which user made the change, or the timeframe when the change was made? For instance, it'd be great if I could create a filter based on changes I made within the past 30 days, or a specific timeframe. Filtering by metadata types takes very long for large orgs, even if I reduce the metadata types down to 1 or 2.

It would be great if you have JIRA connected, to make it easier to create your branch. So basically type-forward (-ish) functionality to identify a JIRA ticket and take the issue ID and description as branch name.

Say your JIRA ticket is ISSUE-1234 Implement this awesome feature.

The default branch name would be issue-1234-implement-this-awesome-feature.

(Where it reads JIRA could be Azure or any other support tool of course).

When creating a new branch from the 'Create new branch from...' model, it's hard because of the small size of the modal/dialog. Just sizing the modal/dialog larger would make it easier to work with.

The backup job color (or a colored tag) should be introduced so you can clearly see which backup job is for Production and which is for a Sandbox.

At the moment they all look the same and you have to make sure you are clicking on the correct one, only by looking at the username to understand if it is a Production org or not.

This is confusing and risky

I would like to be able to monitor daily changes made without those monitoring jobs being visible to the entire team. We have some super motivated people as well as the other end of that spectrum. I would like to have some data to visualize daily without the entire team seeing what I am doing.

If a source control space has enforced GPG key signature for all commits, gearset is not able to push any commits.

Gearset does not support PR validation for AWS code commit. We are cloud-native and use AWS extensively, thus missing out on most important feature of gearset. If you can support it it will be amazing and lifesaver for us.

https://gearset.com/blog/set-up-automatic-validations-of-pull-requests/

We would love to schedule a deployment from GitHub source to a few sandboxes at the end of each 2-week sprint.

It would be useful to be able to set individual retention policies on core objects, rather than on the entire backup job. This is for an old org (c.10 years), ideally you'd be able to set differing retention policies on different objects; e.g accounts after 7 years but contacts after 5 years.

If the State and Country lists have been updated so the API values are set to ISO country codes the Masking of those fields during a data deployment does not work.
Data Load errors: '"FIELDINTEGRITYEXCEPTION:There's a problem with this country, even though it may appear correct. Please select a country/territory from the list of valid countries.: Billing Country:BillingCountry --"'

Disabling masking works around the issue.
It would be great if the application could check the State/Country list and utilize the API values for masking.

Given that the actual download files for Data Download expire after a short amount of time (which is completely logical), it would be beneficial to be able to know what objects were included in the data downloaded, and potentially any filters used.

The main reason behind this is from a security stand point, if an employee with access were to go rouge and decide to download sensitive data to sell/take with them, there is no way of telling what kind of data they may have if you were to miss the window of the backup being available.

Currently you can only push to 1 Salesforce org, however, we manage multiple organizations and would like the capability to push the same package to multiple organizations

Stella outlook pst password recovery software software is the improvement software software to get better all pst record password using great password recuperation methods. This software application is recover all pst report encrypted password and any key mixture pst record password an useful resource all model 32bit and 64bit pst record. This software is help to take away all pst file password without corrupting authentic pst file.
For greater data go to this hyperlink
https://www.stelladatarecovery.com/pst-password-recovery.html

Within Azure Devops you can group commits and changes into a release based on a tag. So for a user to be able to add that tag when they are associating a workitem to a commit would mean they didn't have to go into Azure Devops later to add the tag.

Sometimes, you carefully craft a comparison between source org and VCS only to discover that you have targeted the wrong branch!

It would be nice to go to the Comparison History tab, select your completed comparison and click Clone so you can change the source/target but preserve your selected metadata filters and selections

Current Environment Variable feature uses search/replace logic across the entire metadata file. This is a bit "scary". Add optional 3rd argument for the specific XML tab within the file that you want to limit the scope of the search/replace to

Right now Gearset supports the set up of webhooks into azure devops which trigger deployments when a branch is updated.

I'm looking for an extension to that feature to also include "approval completed" steps. These are already available to hook into within Azure DevOps, so I'm hoping it'd should be a relatively small piece of work to extend GS to support this