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.
1434 results found
-
I would like to download a CSV file from any stage in the Pipeline that includes all the PR details.
I wanted to know the PR's that are pending between the pipeline environments, so I copied the screen data into a spreadsheet and had to spend time to make it usable. I used the information to understand the outstanding work by team (we follow naming conventions for our work), identify stranded stories from departed developers, and have a deeper understand into the backlog. I am using the information to talk to the pod leaders discussing process improvements, release timing/scheduling, and other operational improvements.
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 -
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 -
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 -
Post pull request descriptions to linked Jira ticket
It would be good to have the ability to post pull request descriptions to the linked Jira ticket of a feature. Currently there is limited visibility of the pull request description as its only visible in the code repository, therefore it would be good to see it on the jira ticket as a comment.
*05/11/25 With the addition of AI generated PR descriptions the information is even more valuable and should be more visible across the devops process.
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 -
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 -
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 -
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 -
Problem Analyzer while building the deployment
Surface problems with building the deployment to allow users the correct in the deployment.
1 vote -
Feature that allows users to post Deployment information to custom object in Salesforce
Gearset has feature to allow users to send depolyment information to Jira. Provide the ability to do the same to a custom object in Salesforce.
1 vote -
Please add 'Type' and 'Priority' field from Jira to Reporting API.
In the absence of 'Type' and 'Priority' field from Jira in Reporting API, it become significantly challenging to report on Cange Failure Rate and Mean Time To Resotre and rely on either on the Jira title or description, which is again a heavy lifting in order draw the report.
1 vote -
Feature Request: API Endpoint & Webhook for Validation Errors
I hope you’re doing well.
I’d like to propose a feature enhancement for Gearset’s API that would greatly improve integration and visibility across systems like Slack, GitHub, and Jira.
Feature Request:
• API Endpoint:
Expose the existing endpoint as part of the Gearset API: https://us.app.gearset.com/api/validation/started/{jobId}/result that returns specific error messages for failed components after a validation attempt.
This would allow us to programmatically retrieve validation outcomes and integrate them into other systems for better tracking and visibility.Webhook Support (Bonus Feature):
Even better, adding webhook functionality to push validation results directly to external systems (e.g., Slack) would streamline our workflow.…1 vote -
Visibility settings for 'Shared Sandboxes' in the gearset pipeline
Currently, Gearset only supports the binary visibility settings for sandboxes; either the developer could see his/her sandbox or everyone's sandbox. But in the case of a 'Shared Sandbox,' there is no ability to give visibility access only to a specific subset of users in the pipeline.
1 vote
- Don't see your idea?