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.
1437 results found
-
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 -
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 -
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 -
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 -
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 -
The Importance of Data Analytics in US Logistics Solutions
Data analytics has become a critical driver of efficiency in US logistics solutions. By analyzing real-time data, logistics companies can optimize routes, reduce fuel costs, and improve delivery timelines. Predictive analytics helps businesses forecast demand, manage inventory levels, and avoid costly delays or stock shortages. It also enhances transparency, allowing companies to track shipments accurately and make informed decisions quickly. In warehousing operations, data insights improve space utilization, labor planning, and compliance monitoring, especially in specialized areas like food grade product warehousing. Overall, data analytics empowers logistics providers to increase reliability, cut operational costs, and deliver better customer experiences…
1 vote
- Don't see your idea?