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.
1313 results found
-
Darkmode option
It would be really helpful having a dark mode of gearset UI. A big number of devs prefer dark mode over bright mode. Since gearset is a tool mainly used by devs, would be good to give to devs the option to customize their UI.
9 votes -
Auto merge of PRs
Once the validation process is successfully completed for the respective PR, it would be very helpful to have an option for automatic merge and deployment. This would streamline the release process and reduce manual steps.
Additionally, it would be great if we could have control at the org level to enable or disable auto merge functionality. This way, teams can decide whether they want to use auto merge based on their workflow preferences or organizational policies.
Thank you for considering these enhancements!
5 votes -
Pick up test classes to run from the apex class
Add a variable in apex classes where we can specify which test classes to run.
Recently you added the ability to specify the test classes to run on a pull request, which is great!
I know <ApexClassName>Test are automatically picked up by GS, but would be great if we could specify with
@TestClasses('CaseTestSuite,LeadTestSuite') or similar in the actual Apex Class and Gearset would automatically pick it up and add those test classes to the pull requests .3 votes -
Delay Jira status updates until after post-deployment steps are completed
Currently, when using the Jira integration with Gearset pipelines, status updates happen immediately after the initial deployment completes, but before any post-deployment steps are executed.
We need the ability to configure Jira status updates to occur only after ALL post-deployment steps are successfully completed. This would ensure tickets only show as ready for validation when they're truly ready to be tested.
This is important for teams that have mandatory post-deployment steps (like data imports, configuration changes, or additional verifications) that must be completed before a story is actually ready for testing. The current behavior can lead to confusion when testers…
4 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 -
Allow multiple team members to be assigned to a single sandbox on the pipeline view
Currently a single team shared sandbox can have multiple users with delegated access. However, only one of the users can view the sandbox in a pipeline view. In order to allow multiple people to see the sandbox -
Current solutions:
- Add the same sandbox multiple times and assign each to the required team members
- Or, allow all team members to see all sandboxesSuggested solution:
- Allow multiple team members to be selected via the "Assign sandbox to team member" function.3 votes -
Ability to Select and Merge Specific Changes in Lightning Components and Flows
We are using Gearset to compare and merge changes in Lightning and Aura components, as well as Salesforce Flows. While the tool works well overall, we’ve noticed that it currently lacks the ability to select and move specific changes during a merge. Instead, it requires replacing the entire file, which isn’t ideal in many cases.
It would be extremely helpful if Gearset could allow selective merging of specific lines or sections—similar to how it works for Apex classes. This feature would greatly improve control and efficiency when working with Flows and Lightning components.
Thanks for considering this enhancement!
3 votes -
Remove "No Difference" items when commenting on jira tickets
when i connect a jira ticket to a commit, I like the way gearset posts a comment on the jira ticket listing the changed items. what I dont like is the long list of "no difference" items posted on the ticket. It makes the ticket comments super long and annoying to scroll through. can gearset update this to only post the difference metadatas, or at least give us the option to include or exclude
9 votes -
Changing API Version should make it obvious to save filter before CI Job can be saved
It's a usability bug, I think.
When you change the API version in a CI Job, the button to save CI Job greys out but has a spinning dial of 'Something happening'. Actually the system is doing nothing, it is waiting for the filter to be saved (even if the filter wasn't saved before) but this is completely unclear.
Changes then
1. auto-save filter or bring up the 'save filter' modal
2. Show a toast message saying "save filter"
3. Button should grey out with hover text of "save filter", no spinnerI waited longer than I care to admit,…
1 vote -
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 the ability to set a Profile Picture
Honestly I'm actually surprised it's not possible to set an avatar at the moment, it seems a pretty basic feature in today's online world!
As a neurodivergent team, we want to increase accessibility by being able to distinguish our team members within the platform faster and more easily, so that we can increase our productivity.
It's simply easier to recognise my user in GS if it's "the one with the funny cat" instead of just my initials. Similarly, since we have team members with the same initials that also makes it harder to distinguish them in GearSet since their profile…
5 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 -
Feature Request: Deployment Blocking Based on Daily Unit Test Job Status
Currently, Gearset lacks a feature to block deployment CI jobs to the respective environments when the associated daily unit test job fails. Implementing this feature would be advantageous in ensuring that appropriate testing quality gates are established to prevent changes from being deployed in the event of test failures. This enhancement would significantly improve our deployment integrity and testing processes.
4 votes -
Please add support for decomposeCustomLabelsBeta
Salesforce added the option to configure multiple features in the DX Project Configuration file. One of the is breaking down the big CustomLabels file into individual files where we no longer need to deploy the whole file but just a file (label) that has changes in. Please see SFDX Documentation here - https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_ws_config.htm
11 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 -
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 preview of archived files and let admin choose fields to show on the related list in Archive Viewer
Please improve Archive Viewer with a preview of the files Archived, like the current document viewer on SF and consider to add more functionalities on the related list shown on Archive Viewer, like choosing fields to show and search bar incorporated.
These functionalities are already available with other Archive apps connected to SF.1 vote -
Using Back Promotion for single Environments only and selective PR's only
We normally update our developer orgs with the "update sync" function after the PROD release. However, sometimes we have changes that are build on top of each other but developed by multiple devs and therefore orgs.
In that cases, it would be nice to turn on "back promotion" but only for certain environments where it is needed and not globaly. In addition, being able to selectively create back promotions for PRs would be nice as well.
At the moment, if the feature is activated, Gearset is creating a back promotion for every PR, regardless if it is needed or not.…
1 vote -
Select All PRs for promotion
When promoting PRs from one environment to another in the pipeline, it would be useful to have a "Select All" option
1 vote -
Have the ability to see the metadata comparison between a merge-branch and the destination environment in Pipelines
Greetings,
I would like to request the ability to see the metadata comparison between a merge-branch and the destination environment.
For example, my pipeline is setup:
Developer's sandbox --> QA sandbox --> UAT sandbox --> Production
with the repository branches (merge-branch) for each sandbox respectively:
merge-QA
merge-UAT
mainAfter a feature-branch passes its validation and is merged into the merge-QA, I would like to be able to see the metadata comparison of what is about to get deployed to the 'QA sandbox'. We have the ability to see the contents of the commit via the link to our repository hosting…
1 vote
- Don't see your idea?