Help us improve Gearset
We love getting feedback from our users on how we can make Gearset even better. Post your ideas for improvements, new features, and bug fixes alike, and vote for others – let us know what’s important to you.
1494 results found
-
Have a timer on the compare page to indicate how long the compare is taking
Sometimes a compare can take us 30-45 minutes depending on the complexity of the org. I would like to see a running timer on this page of how long the compare is taking. I don't expect it to say how long is left, just how long it has taken so far. This will help to highlight if any abnormalities are happening, ie. if it's taking a very long time and is only at the Downloading phase for example.
4 votes -
Support deleting comparison data
Having the comparison history is a great feature, but it would be very beneficial to be able to delete any data in the system, especially when working with a trial account. Part of testing could include working with test environments that you don't want to persist after going live. Also, peace of mind when ending the trial that your data has been removed.
4 votes -
Expand the user security model to restrict user compare / deployment access to defined comparison filters
Hi guys -
In many instances, we would like to restrict user access to certain compare / deploy metadata filters. In our case, it would be rare that all metadata changes are to be deployed and we would like to give our engineers access to only certain filters. This would reduce the risk that items that should not be deployed at a high level will not be deployed. In the current model, if a user has deploy access, they can deploy anything and everything. This is what we are looking to avoid.
Thanks in advance for your time!
Best,
Richard
4 votes -
Modify the email address for manual deployment notifications
Being able to modify the default email address for deployment notifications, as for automated jobs, would help keep the others in my team notified of any manual deployments we run.
4 votes -
Unselect all standard profiles & related permission
Often you want to deploy Admin profile and (x) custom profiles. Compare and deploy picks up hundreds of entries for standard profiles which are surplus to requirements. A single click way would be veryuseful.
4 votes -
Support a .gearsetignore file to exclude non-metadata paths from CI triggers
Salesforce DX repositories hold more than deployable metadata: AI agent guidelines, documentation, package.json, .prettierrc, lint configs, scripts and so on. A push that only touches these files still starts a CI job. The job deploys or validates zero components, and on a production pipeline it can still run the full test suite, which can take an hour or more.
Gearset has no way to exclude paths from this. .gitignore isn’t a fix because it stops the files from being tracked at all, and we need them in version control.
Proposal
A .gearsetignore file in the repository root, with the same…3 votes -
Audible Notification when Pipeline Updates have Deployed
The ask: an audible 'pop' sound (like the Support chat reply 'pop') when Pipeline updates are done processing
We have dev sandboxes, a Full sandbox, and production as our 3 layers to our Pipeline. When my personal dev sandbox gets really behind on updates, I hit errors when running ALL updates, so I do ~10 updates at a time. I fire up one wave of updates and navigate away from Gearset.
If I remember to come back to Pipeline in a timely fashion, it almost always is still processing. Or I often forget to come back to fire up a…
3 votes -
Commit test class selection
When initially creating a commit, the only way to specify tests is to manually create a comma or new line separated list. If the validation fails, there is then an option to add tests with a nice searchable/selectable list before revalidating. Can this test class selection UI be added to the initial commit process?
3 votes -
Validate configdata deployments
We are implementing RCA and storing the configdata in source control. Because it is a data deployment and not a metadata deployment, no validations run to ensure the data will deploy correctly. It would be great if there was some way to run validation for the data deployment before merging a pull request that merges it to the org as a check similar to metadata validation.
3 votes -
Add into Problem Analyser InstalledPackage that will default to AllUsers
Currently, Gearset’s Problem Analyzer correctly identifies issues with InstalledPackages, such as suggesting activateRSS be set to false to avoid deployment failures. However, it does not yet account for the securityType field.
When an InstalledPackage is deployed without a defined <securityType>, Salesforce defaults the access level to AllUsers. In a production environment, this is a significant security risk, as managed package components and data access should typically be restricted during the initial deployment.
I am proposing an additional check within the Problem Analyzer for InstalledPackage metadata:
Detection: Identify any InstalledPackage in the deployment package that is missing the <securityType> tag.
Recommendation:…
3 votes -
Add Link to Comparison in Gearset to VCS PRs
Include a direct link to the corresponding Gearset comparison in the description or as a comment to the PR in Github (or other VCS). This would greatly streamline the review process, particularly for Flows, because Gearset's flow diff viewer is the best way to review those XML changes. Without this link, reviewers must manually jump to Gearset and select the proper source and target to perform the necessary comparison.
3 votes -
Allow Metadata Filters to be Version Controlled
Represent a metadata filter as a file (e.g., JSON/YAML/XML) that can live in the repository, similar to a package.xml. When configuring a compare/deploy, Gearset would automatically use this file if it exists in the selected repo. This would allow the filter configuration to be version controlled, which would be especially useful for CI jobs, as filters play a critical role there.
3 votes -
Allow for Simplify Differences to be performed on metadata type before showing it as "different"
Currently, Gearset performs a "Simplify Differences" on Clean data service and
Connected app before reporting these metadata types as "Changed" in the comparison results.There are other metadata types, such as "Custom field" that sometimes show up as "Changed" in comparisons because the internal order of some of the tags are different in a sandbox vs production. Re-deploying these files from one environment to the other does not "fix" these differences. Gearset provides a "Simplify Differences" toggle in the UI that shows there is no effective difference with the file.
It would be nice to provide a configuration toggle for…
3 votes -
Add an account setting to "Mute Live Chat"
As an experienced Gearset user I'd like to mute the live chat so the pop-up notifications don't block buttons. Pop-up notifications have been rather disruptive.
In particular:
after selecting two orgs for a large compare operation, I try click "Compare", and walk away while the comparison runs.
When I return to my computer, I discover that the compare never initialized, and it turns out that although I could see and click the button "Compare", it was behind a live-chat pop-up "Hi David,...", and the button would NOT execute until I closed the live chat pop-up (x) button.I'm experiencing an…
3 votes -
Provide a visual indicator on upstream systems when out of sync with master
Often times we see drift items added to PR's in our upstream systems. It would be nice to have an indicator that shows if a static branch is out of sync with master.
3 votes -
Delete Flow by Version Number
It would be beneficial to delete specific inactive flow versions. Examples where this would help streamline deployment changes:
You need to delete a custom field that is used in a flow. You create a new version of a flow, remove the dependency on the custom field and activate the new flow. Now you want to remove the flow version that still has the custom field dependency. Something like a checkbox to select the version(s) to remove.
You have inactive versions of a flow and you want to clean up the historic flow versions. Something like a checkbox to select the…
3 votes -
Pick up test classes to run from the apex class
Add a variable in apex classes where we can specify which test classes to run.
Recently you added the ability to specify the test classes to run on a pull request, which is great!
I know <ApexClassName>Test are automatically picked up by GS, but would be great if we could specify with
@TestClasses('CaseTestSuite,LeadTestSuite') or similar in the actual Apex Class and Gearset would automatically pick it up and add those test classes to the pull requests .3 votes -
sandbox seeding size
When deploying data to sandboxes, it would be helpful to get an approximation of the amount of data and file space a seeding job will need. I have on numerous occasions hit storage limits as a developer sandbox only has 200 megabytes of usable space.
3 votes -
Allow IN Operator for Data Deployments
When filtering for specific records with ID's, would be handy to have an IN operator for record selection.
3 votes -
Trigger CI Jobs on Gearset deployments
When setting up a CI Job originating from SFDC, we only have the option to trigger the job based on a time interval. Which makes sense since there are no events to subscribe to in SF for this.
But, I think it'd be helpful to be able to trigger a job to run on the completion of another Gearset deployment. This would be useful for automating the addition of metadata items like fields or layouts into source control, which are less-than-fun to create as xml files.
So rather than running such a job every 1hr, we'd ideally be able to…
3 votes
- Don't see your idea?