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.
1309 results found
-
Simple visualization showing Process Builder differences
Assuming the high-vote count Idea for matching on latest version Process Builder flow between source and target (and not by version #) is implemented; make the visual comparison between source/target PB not solely XML.
Process Builder in XML can't be deciphered by a human mind. Hence, a simple indented text-based visualization could be done to make it more readable
- Decision 1.1 Entry criteria 1.2 Immediate actions 1.2.1 action 1 details (XML here OK) 1.2.2 action 2 " " 1.3 Scheduled actions 1.3.1 scheduled action 1 (XML here OK) ...
- Next decision ...
There's an implicit tree layout in the PB…
3 votes -
Deployment of pre-valided package doesn't include accurate test counts
We did a deployment last week and noticed that as part of the deployment report that went out that it stated the Tests Run was zero. We did a pre-validation the day before where we ran all tests with all passing.
Could this test section on the deployment report again include/include the pre-validation tests that were run for the deployment?
3 votes -
Filter out Custom Field differences based on Field Tracking History
If the only difference in the field is that History Tracking is turned on, it would be nice to filter these results out.
Running checks on our app with multiple customers, who all set history tracking differently, can create a lot of noise to filter through to find actual differences.
3 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.
3 votes -
False positives in managed code
When I enable comparing managed packages (e.g. when I have added a field to a managed custom object), I get lots of false positives saying that there are differences in apex code.
On the source org, the code is show as "(hidden)"; on the target it is shown as empty. And Gearset lists this as a change.
Obviously, I know it's not a change, but it adds a lot of clutter to the comparison view.
3 votes -
Compare org monitoring from an arbitrary date to the current state of the org
In Monitor ORG's tab, we have a daily set of cached metadata that can be used to troubleshoot issues in an ORG. This is great that we have this data. What would be even better (if there is not a way to do it currently), is if we could take the metadata cache from the monitoring job, "x" days ago, and compare it to the current state of an ORG.
Maybe an ideal way to achieve this would be to select a cached version in the Compare Organizations screen. Alternatively, a button can be added in the Monitoring Job history…
3 votes -
A count of differences could be grouped by type
If the count of differences could be grouped by type/color that would be helpful.
Ex: 20 differences: 5 red, 7 green, 8 yellow. It gives a better sense of how drastic the differences between Source and Target are at first glance.3 votes -
3 votes
-
Update Test naming convention matching to work with implementation classes
We are using fflib and the AEP enterprise design pattern. As part of this design pattern we have interfaces and implementations for our Service layer classes. E.g. we will have something like ILumpSumService and LumpSumServiceImpl. When we create a test class it would be something like LumpSumServiceTest. So it would be great if the logic could be updated to match use cases where you have an implementation class like that. Also, I think any net new test classes added should be executed no matter what
2 votes -
Add an integration for Google Chat that includes an integration for Change Monitoring and Unit Testing.
Recently, it seems that Google Chat has reached some feature parity with Slack in that it has a defined integration avenue for adding notifications to Google Chat. I have found that I can set up a custom webhook to Google Chat for the CI jobs, but webhooks are not available on the other 2 features I am looking for notifications from.
I would either like to have:
a.) An integration for Google Chat with an app on the Google Chat side that we would add for the connection to our Gearset
b.) Webhook availability for more notifications, so I can…2 votes -
Stop Off-setting Partial Selections when a Package is 'Fetched' for the Latest
Hi,
Our team creates individual draft deployment packages and then we consolidate it into one package and fetch for the latest before validating. In some of our individual draft deployment packages we are selecting partial changes to a page layout or a lightning record page but it is off-setting this partial change and we are given the prompt: 'Precision selections have been reset for these items'. Is there a way we can fetch for the latest without off-setting these partial changes?
Thanks!
2 votes -
Always sort results by Name (alphabetically) as a second-level sort
If a sort has been applied to any column other than Name, apply a secondary sort to "Name" so the rows always sort alphabetically by Name.
This is most useful when sorting by Metadata Type, I'd like the results to be grouped first by Metadata Type, but then I'd like to see the results sorted alphabetically by their name.
Even if the user is sorting by Changed On, for example - if there are 100 fields all deployed on the exact same date/time (ex. Mar 26, 2025 1:19pm), you might as well sort them alphabetically by Name as well
I…
2 votes -
Add option to send notification to the Webex Teams for the Unit tests with the failed tests
Add option to send notification to the Webex Teams for the Unit tests with the failed tests. While setting up a new unit test job for one of our Salesforce orgs I have observed that there in no option to send the notification to the Webex Teams chats. It would be critical to our org as we use Webex.
2 votes -
Show doesRequireRecordChangedToMeetCriteria on Flow Navigator
The doesRequireRecordChangedToMeetCriteria toggle on flow Decisions doesn't show on Flow Navigator, making it harder to check for issues on builds when using the comparison tool.
doesRequireRecordChangedToMeetCriteria should show in the flow navigator, same as the rest of the decision configuration.
2 votes -
Customize the columns in the Compare and Deploy view, such as replacing 'Changed By' with 'Created By
Currently we cannot modify or customize the columns in the list view. So if I wish to see the records having created by instead of last modified by then there is no direct option available on UI at 'Compare and deploy'. It is really useful to have the choice over choosing the right columns as per the deployment needs.
2 votes -
add the name of the draft deployment somewhere on the comparison view
Allow the user to be able to see the name of a draft deployment somewhere on the screen when in the comparison view. Often times, team member will share links to draft deployments but we have to follow up in order to find the actual name of it.
Since the user is taken to the comparison view when they click on a draft deployment link, the name should be visible somewhere on that comparison view page. Even better if that name can also be copied to clipboard.
2 votes -
Clickable Jira Request within Pipeline Promotion History
I would like the ability within the pipeline promotion history to make the Jira tickets clickable. That way a user could simply click the ticket reference to navigate directly to the request.
2 votes -
Add regex or other means to "exclude" strings in monitoring job
The Wave dashboards have a key field that changes every day and causes false positives in the Monitoring jobs. I would like the ability to exclude that string pattern from the results so I don't have a bunch of changes that don't matter showing up every day. Regex seems like the most robust way of defining it.
2 votes -
Check for maximum flow versions reached as part of the pre deployment error check
The problem analysis does not detect that the deployment will fail due to max number of flow versions
2 votes -
precision deployment for Record types
precision deployment for Record types is required. currently when i try to deploy a record type gearset automatically adds all the picklist fields in that object. if we wanted to deploy only record type or only selected picklist fields currently its not possible. hence, precision deployment is needed for deploying record types
2 votes
- Don't see your idea?