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.
298 results found
-
I would like the ability to auto promote updates to inflight feature branches
When using feature branch promotion in pipelines, I often find myself in a scenario where I’ve pulled a new feature through the pipeline to one of my static environments. I then test it, discover something that needs to be changed, make the change in the dev environment, and pull that change through the pipeline again so it reaches the same static environment for retesting.
I would like functionality that enables me to release a new change to that branch from dev and have it automatically promote through all static environments, stopping at the current one where the original pull request…
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.
Let users select the record to restore directly from the related list in Salesforce.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 -
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 -
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 -
Allow environment variables be applied to all environments except specified
Allow environment variables to be applied to all environments and specify exceptions for which they should not be applied.
For example, if an email address is stored in source control as prodsupport@example.com it should be transformed to sandboxsupport@example.com for all environments except prodcution.
1 vote -
Allow developer sandbox updates to be queued instead of failing
When you update developer sanboxes you can only do a max of 2 at a time or else the extras fail and do not automatically retry when the other are done. I would like if they would just enter into a que so that you could click update on all of them and not have to wait until the first 2 are done to then click the next two.
1 vote -
Update all developer sandboxes with one click
Deploy updates to all developer sandboxes with one click
1 vote -
Promotion PRs should show the original author on GitHub enterprise
Hello, according to the documentation here - https://docs.gearset.com/en/articles/8545155-why-are-my-prs-showing-the-pipeline-owner, promotion PRs created by Gearset in GitHub can show the original author of the PR. After talking with support, they told me that this feature is not supported for GitHub Enterprise. Could this be made available in Github Enterprise, as it is now in GitHub?
1 vote -
Git Delta Deployment
I think it would be great if Gearset pipeline feature changed to do a pure Git delta deployment instead of a Git/Org delta deployment. The reason for this is that then you only deploy your work (or what has changed) instead of deploying potentially any differences between the given branch and your org. Here's more information on this concept: https://developer.salesforce.com/blogs/2021/01/optimizing-unpackaged-deployments-using-a-delta-generation-tool
1 vote -
Auto pull in Commit descriptions into pull request description
Create a button in the pull request creation screen that allows you to pull in all commit messages into the pull request description field automatically.
1 vote -
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 -
Automating/Scheduling DevSandboxUpdate aka Back promotions in gearset pipeline
Automating/scheduling DevSandboxUpdate, aka back promotions in the gearset pipeline, sometimes it becomes challenging for developers to update their sandboxes whenever there are frequent releases to production in a short span of time.
1 voteThis is currently planned for later this quarter and next.
Users will have the option to:
- Bulk update selected dev sandboxes
- Automate developer sandbox updates; they will be immediately tried as and when ready
If users want to automate dev sandbox sychronization now, they can use CI jobs to deploy changes from their desired source of truth - this comes with some risk of affecting work in progress though.
-
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 -
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 -
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 -
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
- Don't see your idea?