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.
1447 results found
-
Add AWS Bedrock Integration for AI-Powered Deployment Reviews and Release Automation
As more teams adopt generative AI in their DevOps workflows, it would be valuable for Gearset to offer an AWS Bedrock integration.
Potential use cases include:
Generate AI-assisted deployment summaries before promoting changes.
Review metadata differences and highlight potential deployment risks.
Explain deployment failures with actionable recommendations.
Produce release notes automatically from deployment changes.
Help identify dependency or configuration issues before deployment.
Support organization-approved foundation models through Amazon Bedrock to meet security and compliance requirements.Many enterprises already use AWS services, so an AWS Bedrock integration would allow them to add AI capabilities without relying on external AI providers. It…
1 vote -
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.
1 vote -
Auto-delete feature branches only after final deployment. Current deletion can hinder troubleshooting if pipeline promotion fails.
The current "Auto delete feature branches when there are no PRs open against the branch" setting works well for general cleanup. However, in pipeline-driven deployments, a branch can be deleted even if the change fails to progress to the next stage.
Consider adding an option to delete feature branches only after the deployment successfully reaches the final environment (e.g., Production). This would preserve troubleshooting visibility when pipeline promotion fails and help teams investigate root causes before the branch is removed.
5 votes -
allow CI jobs to run Apex tests regardless of which metadata changed
When a CI job has Apex unit test behavior configured to run specific test classes or a test suite, these tests will only execute if the deployment contains any Apex changes. I would like to execute certain Apex tests every time my CI job runs so I can be confident that my changes haven't caused any unintended behavior.
I'm building a feature and have maintained an Apex test suite which covers all of the Apex which supports that feature. I would like this suite to execute for every CI job run, regardless of whether any Apex code is changing, to…
1 vote -
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.
1 vote -
Ideas for improving the automated testing feature
I have a few small ideas that I’d like to share:
- It would be useful to support wait times in minutes, not only in seconds.
- After the last step, it is currently possible to add a wait or another action, but only via the dropdown menu. It would be helpful if a plus button was also shown after the final step, consistent with the other steps.
- It would be useful to have additional date variables for Last Month and Next Month.
- It would be useful to have an auto-incrementing integer variable, where the value increases by 1 each time it…
1 vote -
Org Intelligence Feature Request
Import impact analysis from Org Intelligence directly into Azure Boards, Jira etc. Copy paste doesn't work due to format issues.
For example, I asked impact of updating a trigger to gearset agent, it did return impact analysis in detail but I would like this information to be sent to Azure notes or some other field so that BA's, Dev's and everyone within the team has access and can see what they are dealing with and be aware of what to test for a particular update/change.
1 vote -
Validate configdata deployments
We are implementing RCA and storing the configdata in source control. Because it is a data deployment and not a metadata deployment, no validations run to ensure the data will deploy correctly. It would be great if there was some way to run validation for the data deployment before merging a pull request that merges it to the org as a check similar to metadata validation.
3 votes -
Migrate a user to different login method without new acount or allow same user with multiple login methods
For each login method a user gets assigned a new account and has to re-setup all of their person connections. Please allow an Enterprise Gearset Admin (Owner) to update or migrate a user from one login method to another. Or allow the user to authenticate using any of the allowed methods without creating a new user account.
1 vote -
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?
1 vote -
From the gearset pipeline view, i wish there an option to export all the pull-requests including the respective git branches in a csv or .xl
From the gearset pipeline view, i wish there an option to export all the pull-requests including the respective git branches in a csv or .xlsx format
1 vote -
When we have the problem analyzer suggest to remove things (like fields) an option to also add that field would be great
Having the ability to add a field instead of just remove it et al in the problem analyzer would be sweet
1 vote -
Pipeline: a more selective developer sandbox alignment
In the pipeline, let's say there are more developer sandboxes and a feature-branch is created from one of them and merged until the main branch.
At this point, only the other developer sandboxes must be aligned from main, there's no need to align the one where the feature-branch was created from.
Therefore, the pipeline should show the symbol 'need of alignment' only on the other sandboxes.1 vote -
license
Update Audit Report to include License assigned. This is on the user export list, but missing from the Audit. Role(s) assigned is also needed (idea already in the list for that one).
1 vote -
Limit file size for download of Data backup Snapshots
When trying to pull a complete snapshot of a previous history databackup (including files) the file generated can be quite large (> 500GB). This is difficult to download using traditional methods.
Need a way to have the file(s) broken down into small chucks (500mb to 1gb in size) [i.e batched] so thats is more manageable to download.1 vote -
Support for decomposed permission sets
Please add support for decomposed permission sets: https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_ws_decomposed_md_types.htm. Permission set decomposition makes large permission sets much more manageable. Decomposed permission sets currently fail to deploy through Gearset. I confirmed with Gearset support that it isn't currently supported.
4 votes -
export
Ability to queue up multiple exports. As part of internal processes we are looking to download the final Org snapshots from the end of FY25. We have 10 prod orgs being backed up. Seems like we can only have one export job running at a time.
Please add the ability to queue up the backups.1 vote -
Allow more than one top level object for seeding.
The latest Sandbox Seeding tool requires a single top-level object. This isn't useful for us as we have multiple entry workflows. I would like to be able to have multiple.
As an example
We have users who work on Cases via Service Cloud. Almost all of those Cases have an Account, but not All.
We have users who work on Orders. All of those orders have Accounts but few have Cases.
We have users who work on OurCustomObject. All of those OCOs have Orders and Accounts but not all Orders or Accounts have OCOs.1 vote -
PMD Rule - Detect Escape Single Quotes
Introduce PMD rule to detect any Escape Single Quotes in Apex.
1 vote -
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
- Don't see your idea?