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.
1413 results found
-
Scheduled deployment freezes
Prevent deployments during certain periods of time for a team or for production environments
10 votes -
Allow for selecting which repositories to display for github in org settings.
It would be helpful to be able to select repositories to display in the selection under Manage Orgs. Some of our repos in Github aren't related to Salesforce deployments, and filtering those out so they don't even show in the list would be really helpful in getting to selections faster.
10 votes -
Allow comparisons of a single commit from a VCS
Currently, you can select a VCS repo and branch to use for comparison. It'd be great if you could select a specific commit from that branch, so that you're only looking at an atomic set of changes. This would allow for fine-grained comparison and deployment of changes.
10 votes -
Provide an API for querying deployment info
Please provide an API for querying deployment info such as friendly names, components, deployment notes, etc...
10 votes -
Automatically revert PR in GitHub CI Jobs
When a CI job fails, the bad code remains in the GitHub repo. I'd like to see a way to revert the commit/PR that caused that failure so that any CI jobs for new, unrelated, commits/PRs won't fail while the developer is working to resolve the issue.
10 votes -
"Changed on" date on source control side of comparison does not show
We have no way of knowing when the files were last changed on the source control side. Tried only with BitBucket though.
10 votesThat is something we should definitely show. We’ve added it to our investigation list to see if it can be added into the app.
Thanks,
Jason. -
Ability to Select and Merge Specific Changes in Lightning Components and Flows
We are using Gearset to compare and merge changes in Lightning and Aura components, as well as Salesforce Flows. While the tool works well overall, we’ve noticed that it currently lacks the ability to select and move specific changes during a merge. Instead, it requires replacing the entire file, which isn’t ideal in many cases.
It would be extremely helpful if Gearset could allow selective merging of specific lines or sections—similar to how it works for Apex classes. This feature would greatly improve control and efficiency when working with Flows and Lightning components.
Thanks for considering this enhancement!
9 votes -
Permission set changes not displaying without drilling down
You shouldn't have to drill in to see the changes in a permission set. I was stumped b/c it showed no difference, but in reality I had to drill down to see the difference. This is bad UI
9 votes -
Introduce Import/Export feature for Custom Filters
Expose the underlying JSON/XML for Custom Filters so that we can export it, modify it in a text editor either by hand or with python scripts, then load it back into the custom filter.
For example I have my main CI filter with 50ish metadata types, and every other filter is a subset which I establish by cloning the "master" filter and deselecting metadata types. Whenever I make a change to the master filter I am forced to nuke all the the "detail" filters and recreate them off the master using the above approach.
So many clicks. My preference would…
9 votes -
Ability to accept/disregard repo cleaner changes
I would like the repo cleaner to work more like the problem analyser, offering a chance to accept or disregard the suggestions before executing it.
Currently Repo Cleaner can only be enabled/disabled only at team level settings, thereby forcing the setting team-wide, which effectively rolls onto all the projects/repos using Gearset for deployments.
I have come across a situation where I would not like to alter the repo with changes any more than what I have actually changed, but since its a team-wide setting the repo cleaner was getting triggered in and bringing in more changes to my repo than…
9 votes -
Expose Salesforce Validation Errors within Github PR
Currently when a PR Validation fails (Deploy CI Job with Validate Target setting turned on), the user can click the Gearset "Details" link to go into Gearset to see the exact error.
Many of our devs use VS Code and Github for their daily work and only rely on Gearset for the CI job. Having them jump into Gearset just to see the error is time consuming and not very intuitive for them. Sure we can find the same errors within the target org of the CI, but at that point the list of validations is large and it's hard…
9 votes -
When Field is Deleted Permission Set changes are not recognized for the Field
Let's say we have only one object in the system. Addressc. And we have one Permission Set -> "System Administrator" with only "FieldPermissions" for all fields in the "Addressc" object.
Now I wish to Remove 2 Fields from "FieldPermissions" of the "System Administrator" Permission Set.
1st Field I'm removing just because I do not want the permission to be in the Permission set
2d Field I'm Removing from Permission Set, as I have physically deleted the Field.On Compare And Deploy Page I will See Deleted Field and I will see only one Section to be removed from…
9 votes -
Compare metadata by "Changed Date" for both "Source" and "Target"
In "Compare and Deploy", is there a way to add a column for "Changed Date" for the Source item, in addition to the Target item?
I want to select all the items which were more recently changed in the Source than in the Target. In my current large org compare-and-deploy, I see many items which are different but the one in the Target was more recently changed, so I don't want to overwrite that item in the Target.
9 votes -
Email notification selection: none, success, failed deployemnts
In account settings allow me to choose what kind of notifications I want to receive to my email.
[ ] Send me success deployments notifications
[ ] Send me failed deployments notificationNo selection means do not send any notifications.
Why? With many deployments my email is bombarded with notifications. Last two weeks 65 emails which I do not read as I see status on screen. Therefore I want to turn off those notifications.
9 votes -
Offer to push components that passed validation even if some items failed
For large payloads (thousands of artifacts) it can be tedious to try to resolve a few minor issues when 99% of the package will deploy successfully. Having a feature to push stuff that passes validation would be helpful. Included in this in the deployment summary and deployment reports will be a count and list of items that failed validation and were omitted from the package so they can be investigated
9 votes -
Default to Object View
Option to default to Object View vs XML for metadata types that have it available
9 votes -
Allow custom rules in PMD
PMD support is great, but it would also be useful to be able to have a set of custom rules for my team
e.g. we have a code library of classes that they ought to use instead of coding their own solutions every time. Some of these cases could be spotted by a PMD rule, so it would be great to be able to add my own rules for this.
9 votes -
Improve PermissionSet comparisons by providing an option to ignore fieldPermissions when their editable/readable are set to false
Current Metadata Behavior:
When a new object is added, objectPermissions are only added to a PermissionSet only if one of allowCreate, allowDelete, allowEdit, modifyAllRecords, viewAllRecords are set to true
When a new field is added, the new fieldPermission is added to all PermissionSets by default (with editable and readable set to false).
NB. PermissionSets are additive in behavior and can only open up access not revoke. Values of false have no meaning and are only noise.Current Gearset Comparison Behavior:
Comparing PermissionSets show these new fieldPermssions as New Items even when default values for editable, readable are set to false.…9 votes -
Display which apex triggers have low code coverage if a deployment fails
It would be great if Gearset can surface which Apex trigger has 0% code coverage when a deployment fails.
9 votes -
Provide option to disable parallel apex testing in Scheduled Tests
Scheduled Test runs can fail due to UNABLETOLOCK_ROW errors. This is due to what amounts to a bug in SF: accessing public custom settings in tests which are run in parallel can cause deadlocks. Really, the tests ought to be isolated from each other, but they are not. See:
The workaround in SF is to disable parallel apex testing.
If Gearset could do that during the scheduled test run, it would prevent false test failures.
I guess I could change the option on the SF org, but sometimes parallel testing is useful, so I wouldn't want to…
9 votes
- Don't see your idea?