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.
1494 results found
-
Enable getting updates to developer environments from an integration branch rather than only from our base branch (main)
We'd like a pipeline setting option to specify a branch that updates to developer sandboxes come from, rather than being locked into using our base branch, which is main. We often have features sitting in our integration branch for up to a month before they work there way to main/production. Sometimes we take on new stories that have dependencies on another story that is not yet in main, but only in our integration branch/environment. We'd like to be able to specify a branch that updates to developer sandboxes come from so that we can use our integration branch instead of…
2 votes -
Expose all Gearset operations through APIs
Gearset can only be configured by a human through the UI. This leads to long, manual, and error prone setups with no way to create reproducible automation for common scenarios. We'd greatly benefit from having the ability to automate these setups through APIs or some Infrastructure as Code framework. Here are some examples of operations I'd love to automate or integrate into other workflows: initiate CI job PR validations, clear existing Updates from a developer sandbox, manage org connections, manage developer sandboxes in a pipeline, manage user permissions, manage monitoring jobs, manage unit testing jobs, mark manual steps as completed,…
2 votes -
Add the option to select specific metadata items before a back promotion fails.
We have multiple dev sandboxes. If there is a metadata item that is identified that should not be included in ALL back promotes, it's a waste of time for every dev to wait for this failure in order to remove the metadata item. Please provide an option to select specific metadata items before receiving the failure.
2 votes -
Body: When a Config Data / CPQ deployment fails or partially succeeds, there's currently no way to export the list of failed records and the
Body:
When a Config Data / CPQ deployment fails or partially succeeds, there's currently no way to export the list of failed records and their error messages. You can only review them on screen.For Metadata deployments this already works well — from Deployment history you open the deployment, click "View errors", and an export option is available there.
Please add the same export capability to the Config Data errors page. With larger data deployments, the number of failed records can be significant, and having the full error list in a file would make it much easier to triage the…
2 votes -
Allow us to mark deployment failures on the pipeline as fixed without the need for a new deployment
When there was an error on deployment and we fixed it, by doing a compare and deploy. We would like to mark the Error as fixed. So other users can see that the error already has been solved.
2 votes -
Notify When Metadata Is Not Enabled for Deployment
It would be helpful to have a warning/notification when metadata is added to a branch through a comparison but is not enabled for deployment.
We recently ran into a situation where the comparison allowed us to select managed package components and add them to the branch. However, the related metadata was not enabled for deployment, so those components were present in the branch but were not actually deployed to the target org.
It would be useful to have this notification either:
During comparison, when selecting metadata that is not enabled for deployment, or
When promoting the PR, if the PR…2 votes -
allow a second sandbox to pull PR changes before PR is promoted to main
Currently I have to manually apply a PR from another developer to my sandbox. It would be great if we could sync back a PR before it reached main or sync across from one sandbox to another
2 votes -
Quick Fetch Latest Changes
The quick fetch feature would just ensure that the components that already exist in that feature branch, are refreshed i.e. their latest version is fetched and automatically added to the commit with the click of a button, without having to go into the comparison view again, from which, now the user can create a new pull request.
2 votes -
Pay as you go Pricing
There has to be a pay as you go pricing model for Contractors who have random uptime and downtime in using Gearset.
2 votes -
Upload a screen shot of the Flow Application error and get details on how to fix it
I saw a demo from Copado today where they are able to upload a screen shot of the Flow Application email into their AI agent and it spit out details on how to fix the error in the flow. Is this something Gearset offers or plans to offer in the future?
2 votes -
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…
2 votes -
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 -
Notifications/Reminders for Promotion Pre/Post-Deployment Steps
When a deployment is waiting on a pre or post deploy step, send a Slack notification or email. These are easy to forget about (or they are completed, but the dev forgets to check them off). Even better would be if the Slack message tagged or emailed the user it was waiting on.
2 votes -
Conflict Resolution Comments
It would be great if there were a way to leave notes or comments for each specific action I take or selection I make during conflict resolution in Gearset Pipelines. This would really help other people understand the reasoning and history behind conflict resolution activity for future reference.
2 votes -
Suggestion for Org Intelligence Enhancement
Add a dashboard within Org Intelligence that tracks metadata changes. Provide the ability to select a date range and view changes across key metadata types such as Objects, Fields, Validation Rules, Apex, Page Layouts, and more.
The dashboard should include interactive filtering functionality that allows users to drill down into individual metadata components. It should also allow customization of which metadata types are included and display rollups summarizing changes, deletions, and modifications, along with details on who made each change.
2 votes -
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
2 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 support for Jira Service Accounts
Jira has (finally) added Service Accounts, so that full Jira users are no longer required. Would be great to take advantage of this. For reference: https://support.atlassian.com/user-management/docs/understand-service-accounts/
2 votes -
Add Webhook Error Logging and History for Outgoing Webhooks
When configuring outgoing webhooks (e.g., to GitHub Actions or Slack), errors and failures are not surfaced to the user, making troubleshooting difficult and time-consuming. Currently, after a webhook is triggered (or fails to trigger), there is very limited visibility into what payload was sent, what response was received, or whether an error occurred. If a webhook fails silently or returns an error, I have no way to view detailed logs or the history of webhook attempts. Furthermore, error messages (if any) seem to clear out whenever CI job settings are saved, and there is no persistent record of webhook activity.…
2 votes -
Add the ability to track who configuration changes to pipeline, CI jobs, etc...
It would be nice to see when there's a configuration was changed such as required test configuration on a CI job or pipeline configurations.
2 votes
- Don't see your idea?