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.
1430 results found
-
Automatically create a ServiceNow change request when a release has been created
We use ServiceNow for a change management processes. All changes to a production system require a change request. We release changes to production multiple times a week and even multiple times a day so this manual creation of ServiceNow change requests becomes tedious. It would be great is gearset could provide a way to automatically create a ServiceNow change request and auto-populate the description in servicenow with a list of changes included in the gearset release. It could be taken further like default assignment groups etc, but just creating a change request with the gearset changes and leaving it in…
1 vote -
New commits pushed during PR validation aren’t picked up until manual re-run
In Gearset Pipelines, if a PR validation is already in progress and a new commit is pushed to the same feature branch, Gearset does not automatically trigger a follow-up validation for the latest commit after the current run completes. This leaves GitHub showing “checks not triggered yet” for the newest commit until we manually re-run validation.
Expected behavior:
When a new commit is pushed while validation is running, Gearset should automatically schedule/trigger another validation after the current run finishes (or cancel + restart, depending on design), so the latest commit is always validated without manual intervention.
Actual behavior:
The in-progress…
1 vote -
During Data Deployments, allow us to relate records to the User using an External ID instead of the Email and Profile.Name.
During Data Deployments, allow us to relate records to the User using an External ID instead of the Email and Profile.Name. In sandboxes, the email address is changed. It's frustrating, for me at least, to change many email addresses so I can use the current process of linking the User Email and Profile.Name. It would be much simpler to be able to use an External ID.
1 vote -
Allow OR operator at the top-level of object data filtering
Currently when creating field filters, we only have AND at the top level. I would like to have OR at the top level as well:
( Field {operator} Value )
OR
( Field {operator} OtherValue AND OtherField {operator} OtherFieldValue )1 vote -
Allow Automations For Job Configuration Changes
This could also go under: Problem Analysis and Deployment Failures, as it affects how you can analyse why pipelines may be failing.
I would be nice to be able to have the ability to set up an automation which alerts one or more GearSet users that when a Job's Test configuration for Apex Unit Tests -> Run Tests is at a certain value for a specific amount of time or at a certain time.
e.g. the value for Run Tests is not set to "All your tests" and it is 8am in the morning, I want to be able to…
1 vote -
Add into Problem Analyser InstalledPackage that will default to AllUsers
Currently, Gearset’s Problem Analyzer correctly identifies issues with InstalledPackages, such as suggesting activateRSS be set to false to avoid deployment failures. However, it does not yet account for the securityType field.
When an InstalledPackage is deployed without a defined <securityType>, Salesforce defaults the access level to AllUsers. In a production environment, this is a significant security risk, as managed package components and data access should typically be restricted during the initial deployment.
I am proposing an additional check within the Problem Analyzer for InstalledPackage metadata:
Detection: Identify any InstalledPackage in the deployment package that is missing the <securityType> tag.
Recommendation:…
3 votes -
Change the build view in Bitbucket Pull Requests
In the Pull Requests build checks summary on bitbucket, I’d like the view to only display builds that are failing for the current pull request. Right now it shows what is failing for the repo at large.
1 vote -
Syncing Clayton Code Review Findings
Having an easy way to dismiss Clayton findings directly in Bitbucket—and have that dismissal sync back to Clayton’s code reviews—would be extremely helpful.
1 vote -
Receive Email Notifications for Backup Job's Successful Backups and Text Message Notifications for Failed Backups
I would like to get an email for every run our backup job does, but I would like a text message if the backup job fails.
1 vote -
User Access audit Report to contain "role"
Please update the User Access Report to include the Roles a user has been granted.
For User Access Review and Role Review audits, need to provide this information to auditors.1 vote -
Delete configuration data records
Gearset currently does not allow deleting configuration data records.
For example, in advanced approvals, you cannot delete an approval condition. There are workarounds but those records that can't be deleted are just tech debt.1 vote -
How Wiki Page Creation Services Ensure Notability Compliance
One of the biggest challenges in publishing a wiki page is meeting strict notability guidelines. Professional wiki page creation services begin by conducting in-depth research to determine whether a subject has sufficient coverage in reliable, independent sources. They gather credible references from reputable media outlets, journals, and publications to establish authenticity. These services also ensure that content remains neutral, factual, and free from promotional language, which is essential for approval. Proper citation formatting and adherence to editorial standards further strengthen the page’s credibility. In some cases, providers also offer a Wiki page translation service to maintain consistency and compliance across…
1 vote -
Collective list of release components
It would be great if we have a way to find out details regarding the components being deployed to lower orgs or part of the release/sprint that team is working on. For Example, we have Gearset integrated with Azure DevOps (boards) and if Gearset can pull the iteration path along with work item details and when I specifically click on the iteration path for a sprint or release, I should get a list of all the components that are linked with work item deployment. This will help us a lot before the release to check the list and see if…
1 vote -
Add the ability to lock down Releases in Pipelines
My team has a release cutoff of Thursday EOD, we've recently begun exploring scheduling our releases to begin at 5:00 PM on Friday, and we had slight concerns that other coworkers may add items to the release after the cut off since it isn't being manually monitored anymore. I would like to add the ability to prevent additional items from being added to releases in Pipelines after a certain day, perhaps add it to the same section to schedule the release.
1 vote -
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 -
Allow deploying fixes / linking work to closed Jira tickets without reopening them
Currently, deploying a fix related to a closed ticket requires reopening it, which triggers unnecessary notifications to the reporter.
It would be helpful to allow linking or deploying fixes to closed tickets without changing their status, or alternatively make it easier to search and reference closed tickets.2 votes -
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
- Don't see your idea?