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.
1441 results found
-
Add a notes field to environment variables to contain the scenarios it's addressing.
For example, the RegEx allows finding of many different patterns that can all be handled by a single regular expression. Down the road it's less obvious which situations the regex was intended for. Having a simple notes field could be quite helpful.
1 vote -
Restore feature branch when a mid-flight promotion branch is restored
Have just experienced a scenario where closing a PR that is mid-flight in the pipeline caused the promotion branch and underlying feature branch to be deleted. So far, so good in terms of expected behaviour due to my pipeline settings. However, after restoring the promotion branch in order to reopen the PR and promote it in the pipeline, the next environment on the pipeline did not then show the change. This, I believe, was because restoring the promotion branch DID NOT restore the feature branch. Therefore there was no source to create a new promotion branch from in order to…
1 vote -
Create a mass back propagation button
Its very time consuming to have to back propagate one by one to each org. Please create a mass back propagation button.
Also when back propagating where more than one connection to an org exists for instance our techdebt org has several admin connections and I have to hit update on all of them. Make the back propagation smart enough to know that it only needs one update rather than on each connection to the same org
1 vote -
Feedback Search Bar
On the Feedback page place the Search bar at the top. Its odd that it sits at the bottom of the right panel
1 vote -
Grouping more than five sandboxes should not hide them
When grouping sandboxes, having more than 5 in a single group adds a scrollbar, and hides any additional sandboxes added to the group. This decreases visibility into sandbox status. I missed that there were several sandboxes that were very out of date simply because I couldn't see them on the pipeline. All sandboxes on the pipeline should be visible for visibility.
1 vote -
Please update your "Configure and deploy" option to allow the user to limit the records that will be masked in an object. We only want to m
Please update your "Configure and deploy" option to allow the user to limit the records that will be masked in an object. We only want to mask our homeowner records in Account and Contact. We do not want to mask our dealer records. If we could limit the records that are being masked by using record types, this would enable us to use your solution. Thanks!
1 vote -
Pipeline Notification for Metadata filter for Missing components
If I am committing some code via pipeline, in my feature branch that includes a metadata not present in my current CI Job filter, Can I get notified from Gearset that commited/merged metadata not present in the CI Job Filter?
1 vote -
Ability to "Hide" Sandbox Groups on Pipeline Page
In the Pipelines page, it would be very helpful if we had the ability to "hide" entire sandbox groups from view. This would make it much easier to quickly find and focus on the environments that are relevant to the logged-in user.
Ideally, this "hidden group" setting would persist across logins and page refreshes, similar to how the "collapse group" feature currently works.
I'm sure an "unhide groups" feature will be needed with this as well, in case a previously hidden group becomes relevant again.
1 vote -
Allow Archive Notifications for both successful and failed runs
Currently, when an archiving policy runs, you can send out a notification if a run has been successful or a notification when a run has failed. I cannot see a way to have both notification types as I would like to see at a glance how many records have been archived in each run, but I also need to know when it fails with permission issues after deployments or major releases. I do not go into the Archive section every day.
1 vote -
Display the developer who opened the PR throughout the entire pipeline flow.
As a Release Manager, I have difficulties identifying the developer responsible for the PR.
The developer's name only appears when they open the PR at the beginning of the process, and in the following stages, it shows the system user's name from git that Gearset uses to open the PRs up to production.
Since I need to easily know who opened the PR during the release creation, I have to open the feature card to find the developer. ...
1 vote -
Enable multiple orgs to act as build agents for single pipeline step
Occasionally our queue is backed up waiting for dozens of PR's to validate, this happens because a single org can only validate one PR at a time. It would be helpful for a solution that allows us to attach multiple orgs (sandboxes or scratch orgs) to a pipeline step such that multiple PR's could be validated in parallel. Then when a PR is deployed it could easily be deployed to all of the attached orgs.
1 vote -
Solution for enabling parallel builds validations, i.e. multiple build agents
Occasionally we have a backup in our queue PR validations where dozens of tickets all have to individually wait for there spot in line to validate. It would be great if we could spin up multiple orgs (sandboxes or scratch orgs) and attach them to a single pipeline element such that each org could help load-level the validation queue.
1 vote -
Preserve Precision Selections through Fetching the Latest
You're precision selections feature is absolutely amazing! Every time I use your tool it just gets better and better and this feature has me hooked. It's been huge with lightning web pages which often have multiple changes in UAT and need to be separated for deployment.
We prep deployments before sending to UAT. Occassionally, there has been a big delay since the package was originally validated. If I need to go back to the original draft deployment and refresh the selected items to ensure I'm not overwriting something else that went out, the precision selections are cleared.
- There is a…
1 vote -
Deployment Failures in Pipeline
The flow of a pipeline promotion is as such:
- Validate deployment to org
- (on success) Merge PR into base branch AND move PR to "Recent Promotion History" tab
- Deploy to org
IF the deployment fails at that point, or is partially successful it would be great to denote that somewhere within the CI job within the pipeline. This would give the devs.admins more visibility into the true state of their features. Maybe we don't even move to the next environment until after a successful deployment.
1 vote -
Automatically Backfill Dev Environments with Pull Request When Changes Are Promoted Downstream
Description:
Currently, Gearset’s pipeline tool does a great job of back-propagating changes between static environments when a change is made further down the pipeline. However, this behavior does not extend to developer environments, even if the change originated from a feature branch tied to that dev environment.Problem:
If a developer starts work on a branch in their dev environment, and then that branch is promoted down the pipeline (e.g., through UAT, Staging, etc.), and changes are made to the branch further down (e.g., hotfixes, last-minute edits), those updates do not automatically get proposed back to the original dev environment.…
1 vote -
Add Monday.com as a source for User Stories
Add Monday.com as a source for user story integration
1 vote -
Enhancement Proposal: De-merge Option for Gearset Branch Management
Currently, Gearset provides a helpful feature to merge branches, which is ideal for creating a Release branch that bundles all related components. However, it would be a valuable enhancement to introduce a de-merge or selective unmerge capability. This would allow teams to easily remove specific feature branches from a Release branch particularly useful in scenarios where some stories are pending approval or need to be excluded from the release at the last minute.
Such a feature would improve flexibility during final release preparation and reduce the need for manual branch adjustments or rework.1 vote -
Deploy CustomLabel by label separately
The automated deploy (CI) filter does not have the resources to deploy isolated CustomLabels, so that specific labels can be included or excluded.
1 vote -
load more items
Please stop using "Load more items..." as the way to load more table items. It's very annoying to have to say show me the last 30 days but then click the button 20 times to get there.
I'm referring to the Promotion history page but anywhere this concept is used should be ripped out.
1 vote -
View webhook pipeline settings and error history even when promoting
When any pipeline is promoting most of the options in the pipeline settings menu are disabled, e.g. 'View Webhook Errors'.
We want to be able to access these features, as we might need to reference a webhook error, and not have to wait until the pipeline is finished promoting. Our team is promoting at least one feature to one pipeline most of the day so we have to wait until after business hours to reliably access this information.
1 vote
- Don't see your idea?