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.
1461 results found
-
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 -
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
4 votes -
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 -
allow automatic publishing of an experience site after deployment
Just like you can automatically activate Flows in Gearset upon deployment; it would be nice to automatically publish deployments of Experience Bundles. This is especailly true for deploying Experience Bundles to staging/qa orgs but applies also to PROD.
There's an API to do this: /connect/communities/communityId/publish documented https://developer.salesforce.com/docs/atlas.en-us.chatterapi.meta/chatterapi/connect_resources_communities_publish.htm
7 votes -
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 -
Add support to deploy Digital Experiences (LWR) using Digital Experience Bundle Components
Similiarly to how you can deploy metadata for non-LWR Digital Experiences (Aura templates), where you can select different metadata changes individually using Experience Bundle Components, rather than deploying all your changes at once, it would be great if that option is available for Digital Experiences running on LWR (Digital Experience Bundle)
5 votes -
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 -
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 -
Add Salesforce Data Cloud sandboxes as an option for deployments
Salesforce Data Cloud sandboxes are now generally available but to promote changes from sandbox to production, the only options are through Data Kit and change sets, CLI, or DevOps Center. Having the option to use GearSet would be helpful so all deployments were managed the same.
3 votes -
Save Problem Analyzer Changes to Deployment Set
When using the Problem Analyzer to identify and fix issues within deployment sets, it's common to add or remove items to address specific problems. Currently, these changes are not automatically saved, which can lead to recurring issues in subsequent analyses.
Suggested Enhancement:
Introduce an option that allows users to save their modifications directly to the existing deployment set or create a copy of the set with these changes. This feature would streamline the problem-solving process and ensure that resolved issues do not reappear in future analyses.Benefits:
Efficiency: Reduce the time spent on re-analyzing and re-fixing recurring issues.
Consistency: Ensure…6 votes
- Don't see your idea?