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.
1285 results found
-
Don't mark data deployment as successful if some records were excluded due to invalid picklist values
Currently if you deploy data and one object had records excluded, the top of the window says "Deployment completed successfully." However, in reality, part of the deployment was NOT successful. The only way to find out is to find that the record is missing or to slowly scroll looking for yellow exclamation. This should be extremely obvious since it's a failed deployment.
1 vote -
Don't mark data deployment as successful if some records were excluded due to invalid picklist values
Currently if you deploy data and one object had records excluded, the top of the window says "Deployment completed successfully." However, in reality, part of the deployment was NOT successful. The only way to find out is to find that the record is missing or to slowly scroll looking for yellow exclamation. This should be extremely obvious since it's a failed deployment.
1 vote -
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…
1 vote -
I would expand my request to if a sort has been applied to *any* column other than Name, apply a secondary sort to "Name" so the rows always
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…
1 vote -
view only user
A free "View Only" user role
We have setup notifications on changes for specific use cases - eg. all changes to custom fields only.
We have configured these to send to Slack and Teams channels - but detailed information has to be surfaced in Gearset.
We would like to give "view" access to many users for the comparison result in the notification, and no other permissions. This should not encroach on the licenced user count.1 vote -
Create a functionality which can Export all the Open PRs for Pipeline
Dear Gearset Team,
We recently encountered a challenge where we had approximately 250 open PRs in production. To streamline the process, we needed to submit a report listing all open PRs, which were then reviewed by the Dev team. If a PR was deemed unnecessary, it needed to be declined. Additionally, some tickets were withdrawn, which required the associated PRs to be declined as well.
Currently, this task requires us to manually open each PR, copy the PR link, add the story linked to the PR, and include the assignee of that story. We then input all this information manually…
1 vote -
Adaption of Deployment frequency of CI jobs
While setting up a CI job, I recognized there are only automatization options up to every 24 hours, which is once a day. Currently there is no possibility to deploy e.g. every second day or even more important to us, every week/ every second week. Please add this possibility when adding CI jobs, to have a slower Deployment cycle to e.g. demo sandboxes, that don't need daily deployment.
1 vote -
Add stacktrace column to Test Outcomes
There is no Stacktarce information on the Test Outcomes from the Unit Testing page. That information is important to help the developer team investigate the issues.
1 vote -
Audit history on Data Backup Jobs
For SOX compliance, we backup our Salesforce production data with Gearset. However, there is currently no way to determine the last time the job was modified. If at the bare minimum we had the last modified date & the user that modified the job, we would be able to confirm for the auditors that no changes have been made. Ideally, we would have tracking on the job for the different features - adding or removing objects, cadence of job, etc. For now, we're having to do a manual review.
1 vote -
Add testing steps to Jira ticket
Like the new feature for adding pre/post deployment steps, it would be good to be able to add testing steps to a feature in gearset.
1 vote -
I would love to be able to edit the name of a feature while it is in progress in the pipeline.
We include the release date as part of the feature title, but sometimes the release date changes after we create the feature and while the feature is still in the pipeline. It would be great if we could update the name of the feature at any point up until deployment to production.
1 vote -
Add Pre/Post Deployment steps for Data deployments
Some data deployments require manual steps pre and or post deployment.
Scenario we had was that a rule for whatever reason couldn't be turned off by GS so I had to manually switch it off or the deployment failed then back on after it deployed,
1 vote -
Add Pre/Post Deployment steps for Data deployments
Some data deployments require manual steps pre and or post deployment.
Scenario we had was that a rule for whatever reason couldn't be turned off by GS so I had to manually switch it off or the deployment failed then back on after it deployed,
1 vote -
Audit changes to the "Require issue tracking" setting
As a result of a query by our auditors it would be helpful to have changes to the 'Require issue tracking' deployment setting audited. They are concerned that a team-owner could alter this to perform a deployment then reinstate it, resulting in change deployment without tracking.
1 vote -
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.
1 vote -
Fix comparison default date range
- Click new compare and deploy
- Select a source and target.
- Notice the date range says "Today" but DON'T change it.
- Click Compare
- Notice the date range now says "All Time"
Repeat...
1. Click new compare and deploy
2. Select a source and target.
3. Notice the date range says "Today"
4. Change the date range to anything else
5. Change the date range back to "Today"
6. Click Compare
7. Notice the date range now says "Today"1 vote -
Fix pre/post deployment steps from disappearing.
- Add Pre or Post deployment step
- Click "Specific environments only"
- Click the "x" to remove all the environments Notice, the entire "Environments to run against" section disappears To get it back you have to cancel, and do it again.
1 vote -
Add Omnistudio Features to Scratch Org Features list
When using the 'Create new scratch org' screen the following features are not available in the 'Scratch Org features' list
OmnistudioMetadata
OmnistudioRuntime
OmnistudioDesignerThese are available features according to the Salesforce documentation
1 vote -
Pull Request Changed Items View Fix
When viewing the items in a pull request in the 'Changes in this PR' section of the pipeline you only see the file name.
I would like to see something more similar to an actual comparison view where you have a tab with one column for the name and then another for metadata type.
Having just the full file name does not give me that instant information I need, especially when its a long file name and the type runs off the page never to be seen unless you hover over the file.
Converting to a table format might also…
1 vote -
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.
1 vote
- Don't see your idea?