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.
1308 results found
-
Add more information regarding team shared metadata filters
Hello, I have the following suggestion.
When a team shared filter is created, it would be a good idea to see who is the user that initially created it.
Also, it would be beneficial to see who last modified it and when was it last used.When we have a lot of team shared filters, such functionality will greatly help with the clean up efforts.
1 vote -
Show "When to Run the Flow for Updated Records" in Flow previewer
For record-triggered flows you either set the flow to run
1) Every time a record is updated and meets the condition requirements
or
2) Only when a record is updated to meet the condition requirements
It would be helpful to view these settings within the flow previewer window of a comparison.1 vote -
Show "When to Run the Flow for Updated Records" values in the flow previewer
For record-triggered flows you either set the flow to run
1) Every time a record is updated and meets the condition requirements
or
2) Only when a record is updated to meet the condition requirements
It would be helpful to view these settings within the flow previewer window of a comparison.1 vote -
Install managed package from sfdx-project.json
I would like to get the possibility to track my managed packages and their versions in the sfdx-project.json file and automatically install it from this file. Could this be a possibility?
1 vote -
Add the ability to put CI jobs into folders
It would be great if we had the ability to put ci jobs into folders. We've accumulated a number of CI jobs. Some of these jobs are no longer in service and we're a bit reluctant to delete them as they may have historical information that we may later want or need. It would be great to be able to put things like this into folders to help reduce clutter and organize our CI jobs page. thanks for your consideration.
7 votes -
Add sharing to comparison view
When you look at the comparison of the list view the "shareto" metadata is not available in the nice clean view. Its only available in the XML view.
1 vote -
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 -
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 -
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 -
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
- Don't see your idea?