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.

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

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.

Hi, when reviewing changes for flows that are being deployed, it would be great to have a toggle option to hide or alternately color location changes which are just the location of elements on the flow canvas editor.
<locationX>1353</locationX>
<locationY>1305</locationY>

Sometimes there are hundreds of location changes and it obscures the important information about what else changed.

When selecting a branch from source control, it would be great if Gearset had an ability to mark certain branches as favorites so they appear the top of branch selection dropdown.

I originally was going to request the ability to append the items found in problem analyzer to the list of selected components, when going back to view the comparison, but then I thought why not take it one step further, and move the problem analyzer feature to the comparison screen? Then, the items it finds/suggests, the user can add them to the package there, or choose to ignore them.

We only use on source control service, so having to select 'Azure DevOps' before being able to select the repo/branch, is a small step that adds up over time.

Being able to either hide services that you do not already have a connection for, or being able to default to a service, with the ability yo navigate back up and over, as needed. would be welcomed.

If there are multiple users making changing the metadata in Salesforce and when one has to deploy their changes, it is not possible to pick the changes that are specific to one person, For this we have to go to VS code and use git patch mode to add only the necessary changes for a specific user. If we have an option to edit the xml after the comparision and pick only necessary pieces and deploy it to next org will save time and also switching between multiple orgs. Currently the comparison editor is read only mode.

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

Idea is to have the Delta CI for Validation only Job, so the as well, so the validation process will become faster .

The option of validating a PR in the deployment job does the same task, but is comparing too many items of metadata and it is taking too long.

Add an Undo button to the comparison UI in case someone accidentally de-selects a component from the Selected Items tab. It would save time rather than having re-search for the component and lose your train of thought. You have this feature in Google Docs and sheets.

It would be nice if we have the select all option in the deployment history to select multiple packages to combine in one go and deploy as one package into target.

Allow Backup job filters to be configured for specific records/files rather than entire objects.

When a deployment is completed, you have an option to clone that package. For many of my deployments, I want to push a package to source control, and then on to production. The second comparison could be limited to just the items in the cloned package. Would be great to have an option to limit second comparison to only the meta-data items in the clone. Would allow subsequent comparisons to run much more quickly, if the user is confident that the package has everything needed for that specific deployment.

A lot of time we would like to have data out of SF not just for backup purposes but for data analytical purposes as well. Ownbackup currently has this functionality via APIs.

https://documenter.getpostman.com/view/12146739/TzJuAxgY#0f1fc918-7616-4b58-8d52-0e8370f57d9b

https://ownbackup-kb.magentrixcloud.com/articles/knowledgebase/Using-the-OwnBackup-API-5-6-2020

If gearset has this, it would help us move to GS for all our SF problesms

Our Apex Classes reference managed packages that are updated automatically in our sandbox/production environments. This causes many classes to get picked up unnecessarily in our comparisons/CI deployments.

Unlike https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/43917792-add-an-option-to-ignore-package-version-difference this is specifically for different package namespaces between the source and target.

In this example the source has one namespace and the target has 2 package namespaces.

It would be very useful to be able to choose to ignore all package differences in comparisons and CI jobs.

Edit "Existing Saved Filters" on an "Existing CI Job"

If using a saved filter on CI job, there is no easy to update an existing saved filter from the CI job directly.