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.
293 results found
-
Do not add Pre/Post Deployment if there is no value.
The current behavior is when the developer do not have any Pre/Post deployment steps added in his/her PR even though Gearset adds the comment in VCS and Jira, and as a result, it creates lots of noise.
Gearset: Deployment steps for UAT1 #4062 (do not edit)
Pre-deployment steps
TitleCompleted at
Completed by
Post-deployment steps
TitleCompleted at
Completed by
7 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
8 votes -
reduce the size of the "maintenance" banner and/or allow me to dismiss it.
reduce the size of the "maintenance" banner and/or allow me to dismiss it. It cuts into my available screen size too much. Dismiss with an option to not show "this" maintenance message again would be ideal
4 votes -
Add the ability to use attachments (e.g Screenshot) in Pre/Post in GS Pipeline
Adding the screenshots in Pre/Post deployments is very essential to streamline the deployments. Sometimes the steps could be complex and confusing, and if the build team could add the screenshots, then it will help the release team to execute those manual steps without the need to get in touch with the developer.
4 votes -
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.
3 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 -
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 -
Make pre/post deployment steps conditional on developer sandboxes.
Pre/Post deployment notes can be set to pertains to various static environments but they always apply to sandboxes after a back deploy. This should be conditional-- most of the time I only set them applicable to prod and they aren't applicable to developer sandboxes.
2 votes -
Add "Open Branches" Tab to Development Sandbox Environments in Pipeline
The only way to deploy an existing feature branch into a development sandbox is to perform a manual compare and deploy. Previously, we had our developer sandboxes set up as static environments which allowed us to create PRs against them for "re-deploy". This is not possible with the new Development Sandbox format. I suggest another tab be added called "Open Branches" which will allow the developers to select a feature to pull and work on in their development environment. That way we get the benefit of easy compare & deploy instead of having to manually compare and deploy. This will…
4 votes -
It would be great to have a centralized way to view all components and static code analysis results for every commit within a branch.
It would be great to have a centralized view for all components and static code analysis results across every commit within a feature branch. For example, if a developer makes five commits to the same branch, it would be much more efficient to review the components and static code analysis results for the entire branch in one place, rather than checking each commit individually through the deployment history. Additionally, there should be an export option to easily share the results with developers. Thanks
3 votes -
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 -
Allow developer sandbox updates to be qued 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 -
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
- Don't see your idea?