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.
1130 results found
-
1 vote
-
default repository
Allow to set a default repository when you have multiple repositories.
- Navigate to Compate and Deploy
- Select Source Control and select a VCS(in our case Gitlab Self Managed)
- If you have dozens of repositories they all show up on the list
- Need ability to specific a default repo which will be auto selected
2 votes -
Roll back feature branches all at once
The tool works really well in the UI promoting things forward through the pipeline. You can select one or more feature branches and promote them one at a time or all at once. It would be great if you could do the same thing with roll-backs. This would make things clean simple and alleviate the fear that you accidentally left something out or accidentally roll-back something you didn't mean to
given that the need for roll-back functionality is inherently somewhat urgent, the tedious nature of having to carefully pick through a larger subset of metadata items to roll-back makes it…
1 vote -
Show Created by and Created Date in Comparison view
I'd like to see created by and created date in the comparison view. Sometimes we have multiple users working on items and I may not be the last to modify something but I am the one to deploy it and if I am the creator, I know what it is named but it makes it hard to sift down if I can only show modified by and modified date.
2 votes -
Bulk resolving merge conflicts across multiple PRs (set resolution as Feature or Environment)
It would be great if there was the capability to bulk-apply Feature or Environment when resolving merge conflicts across multiple PRs. I have a few dozens that all need to be set to the same option, and it would be useful to handle this quickly rather than click on each one individually.
3 votes -
Add to Flow Navigator the flow version description
It would be very handy if the new Flow Navigator view was able to display flow version description. We update this frequently to describe new changes, so being able to read this documentation in the Flow Navigator would be helpful to understanding the flow.
Adding this either as a banner along the top (like some flow xml views) or as an element in the navigator sidebar would be acceptable.1 vote -
Expand integration for our Pipelines to allow us to enable tools like SonarQube and Veracode to run as part of our DevOps process.
We use tools like SonarQube and Veracode within our company to improve our security and code quality. It would be extremely helpful to have integrations with these tools or an open integration we could configure to work with them. Especially if that could be triggered as part of our pipeline process so this interaction is automated.
1 vote -
Improve Github Authentication and Access Control
While authenticating with Github, GearSet asks for too many access request including read/write access to all public & private repos which doesn't make sense.
Alternate Custom Git Auth does not allow teams to create team wide CI jobs.
And with User - specific CI Jobs, It does not allow us to setup "Validate open PR" jobs.Please provide better resolutions on authentication and job setup processes.
1 vote -
Environment variables - Clone
Hello Team,
We would like to have the possibility to clone already existing Environment Variables when setting up a new Environment.
This functionality will allow us to refresh and create new environments faster and prevent us from performing specific commits in branches and specific configs per new environment.
3 votes -
Create releases in Pipelines not at final stage
Right now you can only create releases at the last environment in a Pipeline. We'd like to have 2 stages so we have a true dry-run of deployment. Our pipeline is
Dev > QA > UAT > Staging > ProductionCreation of the release branch before Staging would allow us to effectively cherry-pick what we want deployed into Staging as we get UAT approvals, do a test deployment where QA does a sanity/smoke test and have greater confidence when we get to our Production release.
7 votes -
Add to Problem Analysis option to auto remove DelegatedAccount tab settings
Add to Problem Analysis option to auto remove DelegatedAccount tab settings since it's an invalid tab and can cause validation/deployment errors. This saves a step of having to change Custom Object filter to Named Items and manually exclude DelegatedAccount when moving new profiles.
1 vote -
Option to not run job periodically
In the "Run job" field allow an option to don't run job periodically at all. Sometimes we nedd a job to run only manually, when needed, and now I need to remember to disable it manually each time
1 vote -
Have you all ever thought of putting GPT into this and having AI built release notes?
Have you all ever thought of putting GPT into this and having AI built release notes? Sonar has an AI Data Dictionary which we're trying to hack to use for this purpose, then i realized...HEY...this would be easier to do on the release layer right in gearset. Figured I'd share that I would bet a lot of customers would use that.
An AI that explains the change between the feature branch and the main branch for the releases built would be so nutty on administrative time saved.
1 vote -
Terse Slack/Teams Notifications
Provide a Terse Notification format for Teams and Slack Notifications.
Currently, the amount of information in Teams and Slack notifications is satisfactory, however the presentation in the chat app is very dense and can take some time to grok when you're browsing the history of these messages either scanning the jobs that have run over the past few hours in your channel, or just trying to understand what just happened from the push notification that went to your phone.
Ideally, the first sentence is terse and is separated by white space from the remainder of the current paragraph format.
The…
1 vote -
More efficient spacing on Pipeline environments
We can only see 4 sandboxes at a time when fully zoomed out. We have 9 sandboxes. Since we aren't able to zoom out further or rearrange the sandboxes we are constantly dragging the screen to pan up and down, to see the state of the orgs.
There is so much whitespace in each node, any chance you could lessen the padding/spacing between the lines in each box/env/node, or between the nodes themselves? Maybe proportional to the max nodes in a single column?1 vote -
Bulk resolve merge conflicts
We occasionally run into a situation where there are quite a few files with conflicts to resolve. We almost always are just wanting to accept all changes from the feature (not the environment). This takes an excessive amount of time through the Gearset UI to accept changes in every file. Would it be possible to add a button accepting all changes from feature across the entire PR?
1 vote -
1 vote
-
1 vote
-
Comparison of draft deployments
Two teams who are supposed to be working on different parts of the sandbox org have created two draft deployments. I would like to compare these draft deployments to see if there is any overlap of selected items.
1 vote -
Deployment pipeline view personalization
Currently, the view in continuous integration (deployment pipeline) is sorted by ABC, which is not user friendly when there are many team members. In this case I appear last and I need to find myself in this screen.
I suggest you to either:
1. allow creating personal views per user, so I can see only my dev sandbox, full sandbox and production.
2. change the scroll into a "regular" scroll, and not the current drag scroll2 votes
- Don't see your idea?