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.
1419 results found
-
Add a button or option to run an ad hoc "Policy preview" for archiving jobs
When an archiving job is first created, the "Policy Preview" is run. This shows the records that the policy will find and archive, once the job is actually initiated for the first time. After the job is run for the first time, there is no longer an option to run a "preview". It would be helpful to be able to run a preview at any time in order to see what the policy will archive the next time it is run.
1 vote -
AI PR Descriptions With Custom PR Template
Using the AI PR descriptions and the 'Summarize changes' features needs to be extended to include the use of PR templates pulled from VCS.
Currently, you can only use the 'Summarize changes' without using a custom PR template. The AI output is helpful but using any of the suggested content has to be copy and pasted into your PR template. Instead, it would be more useful if the suggested content (##What has changed?specifically) can be injected into the use of an existing PR template.
1 vote -
Exclude inactive flows from metadata deployment easily
We often have flows that are in an org but inactive that we don't want to include in our deployment. It would be nice if we could filter on the inactive status and exclude them - similar would be helpful for other metadata like apex triggers.
1 vote -
Subscribe for notifications
Would it be possible to have the option to subscribe / receive wider Gearset platform notifications or updates, please? (e.g. release updates, maintenance items, etc)? This will help ensure awareness of any recommended items which require attention. Thanks!
1 vote -
Extend permission to enable ArchiveViewer connector for users
Enabling ArchiveViewer connector is limited to only the Archive Owner. Ownership can be transferred but maintaining Archive Owner is crucial to organization structure and should not be changed. However, the ability to enable ArchiveViewer connector for Archives should be extendable to other users as Archive Owners are usually Platform Owners/Management that does not perform deployment/development work.
1 vote -
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…
8 votes -
automagically refresh the list of salesforce connections when I add a new one.
When I am choosing a source or destination salesforce organization, I can add a new connection, but when I save it and return to the choice page the new connection isn't listed in the drop-down unless I refresh the page. Seems to me that you could trigger a background refresh on save so that the drop-down is auto-updated.
1 vote -
Ability to bulk download filtered records from Archived Data
We Archived over 50GB of data and business wanted to get a list of leads from the last 6 months. There were over 30,000 records and I had to click thru every page, let the page load before I could download them all. There were over 60 pages to click thru. One click button to download them all would a time saver.
1 vote -
Ability to bulk download filtered records from Archived Data
We Archived over 50GB of data and business wanted to get a list of leads from the last 6 months. There were over 30,000 records and I had to click thru every page, let the page load before I could download them all. There were over 60 pages to click thru. One click button to download them all would a time saver.
1 vote -
Add a feature to ignore queue members when deploying queues
When deploying Queues with Gearset the members section is automatically included and the member list is deployed to the target org. Gearset has a suggested fix to sync the queue members with the target environment but it doesn't always work.
Salesforce supports deploying queues with an empty list of users as queue members are more like data than metadata I suggest a feature toggle in Gearset where the users section of the queue is ignored for deployments to preserve the user list in the destination org.
Our company and many others probably maintain the queue users directly in production as…5 votes -
Notification on job start, end with the Salesforce deployment/validation Id
When a new Job is created, it would be great to have the notification/webhook sent on start and end the job, that way, we have a monitoring outside of the Gearset on it. As well as this, to be able to build soe automations based on it
1 vote -
Auto-cancel the old CI/CD process on new commit pushes.
When a validation is runnnig based on PR changes, it would be great to cancel old validation job on gearset, as well as the validation on the salesforce on new commit pushes. That way, redundant jobs are not stacking to be validated and increase the CI/CD flow when multiple PRs are there
1 vote -
External Client App
I have been testing out the ability to promote External Client Apps through a pipeline. I found that if I include the 5 files (.eca, .ecaGlblOauth, .ecaOauthPlcy, .ecaOauth, and .ecaPlcy) that define the ECA, I receive an error of 'We couldn't update your OAuth Link...'.
But, if I edit the .ecaOauth file and remove the oauthLink tag/value then the promotion succeeds. This is an optional tag is set from the source org, and can be removed before promoting. It would be great if this was handled automatically, maybe with the problem analysis tool.
1 vote -
Compare UI feedback after large salesforce project
- Preserve location when switching between new/changed/deleted views. When reviewing a compare with hundreds of components, it's annoying to have to re-scroll when returning to a view. We could filter the lists, but that often means less scrolling, not no scrolling.
- Make the XML view sticky. I'm old school, but after I click on XML view 5 times, 10 times, 20 times, my default should be switched to XML.
1 vote -
Using GitHub Apps to Replace Service Account for Team Shared Connection
Problem Statement / Current Situation:
For enterprise security compliance, organizations are moving to a model where all third-party integrations must use pure application-based identities (like GitHub Apps) instead of user-based accounts.
Currently, Gearset's CI/CD jobs require a "Team Shared Connection," (https://docs.gearset.com/en/articles/8455568-team-shared-source-control-connections) which uses a combination of a GitHub App for authorization and a separate GitHub "service account" user for commit attribution. While this is a functional workaround, it still forces us to create, manage, and secure a user entity in GitHub. This goes against modern security principles that aim to eliminate the management of all user credentials, even…
3 votes -
Add originating Sandbox(es) as a PR comment
It would be awesome to be able to see what Sandbox/org each commit (and thus PR) originated from. There is not many places to add the information to VCS as you can add comments only in the PR stage, but could you for example add comment to PR when promoting with the list of all commits + their origins?
2 votes -
Add Metadata Filter Requirements/dependencies for Deploying Product Records via CPQ
It would be really helpful if Gearset provided a dedicated document that clearly outlines all metadata filters required to successfully deploy Product records through Salesforce CPQ. Having a reference would make deployments more predictable, reduce trial‑and‑error, and improve consistency across teams especially who use pipelines. Adding this documentation to the platform would streamline CPQ-related deployments and save users significant time.
1 vote -
If a Branch fails to create in Github, display the error
We have enabled Rulesets in Github to enforce naming conventions. If a Gearset user tries to create a branch the ruleset will block it. Gearset then displays a generic "Could not create branch X from Y. Please try again or contact support" error to the user, but the error received from Git should include the ruleset's error message.
1 vote -
Visual Sync Alerts for "Commit more changes" Workflow
Summary:
Introduce a sync indicator for features in the pipeline. This would alert users when a feature branch has received additional commits (via the "Commit more changes..." button) that have not yet been promoted to downstream environments.Problem:
When an admin or developer adds metadata to an existing feature branch that is already sitting in a downstream environment (like UAT or Stage), a "parity gap" is created. Currently, the pipeline doesn't visually signal that the version in UAT is now "stale" compared to the version upstream.This creates a risk where a user might promote a feature from UAT to…
1 vote -
Mobile Support
Support mobile devices.
The CSS Used for the Pipeline Environment popover prevents the browser from scrolling horizontally. You can try this be logging into Gearset on your phone's browser or by narrowing the browser width on your desktop.
- I want to deploy from my phone.
- I want to monitor PRs from my phone.
- I want to browse my Scheduled Jobs and Monitoring Jobs.
2 votes
- Don't see your idea?