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.
1379 results found
-
Pick up test classes to run from the apex class
Add a variable in apex classes where we can specify which test classes to run.
Recently you added the ability to specify the test classes to run on a pull request, which is great!
I know <ApexClassName>Test are automatically picked up by GS, but would be great if we could specify with
@TestClasses('CaseTestSuite,LeadTestSuite') or similar in the actual Apex Class and Gearset would automatically pick it up and add those test classes to the pull requests .3 votes -
Customizable Metadata Deployment Order - Destructive change and reference changes
We should be able to define the order of metadata deployments. For example, when deleting a custom field and updating its references, we currently need two separate deployments: one for modifying references and another for field deletion. Allowing us to set the deployment order—modified references first, then field deletion—would enable this in a single deployment, streamlining the process.
2 votes -
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…
7 votes -
Allow environment variables be applied to all environments except specified
Allow environment variables to be applied to all environments and specify exceptions for which they should not be applied.
For example, if an email address is stored in source control as prodsupport@example.com it should be transformed to sandboxsupport@example.com for all environments except prodcution.
1 vote -
Add the ability to hover on the New, Changed, Deleted bubbles on the COMPARE & DEPLOY Results Screen and see the meanings
Can use the wording from the documentation :)
1 vote -
After a package is validated, link to the Salesforce Deployment ID
Gearset already does this for a deployed package, that on the Deployment Summary page it shows the Salesforce ID of that deployment. Can we provide the Salesforce ID for a validation build against a Salesforce environment as well?
1 vote -
scroll bars
Get rid of the scroll bars in the open pull requests tab caused by the queue section overflowing its bounds.
Also, allow us to post screenshots here. :\
1 vote -
Stop Off-setting Partial Selections when a Package is 'Fetched' for the Latest
Hi,
Our team creates individual draft deployment packages and then we consolidate it into one package and fetch for the latest before validating. In some of our individual draft deployment packages we are selecting partial changes to a page layout or a lightning record page but it is off-setting this partial change and we are given the prompt: 'Precision selections have been reset for these items'. Is there a way we can fetch for the latest without off-setting these partial changes?
Thanks!
2 votes -
sandbox seeding size
When deploying data to sandboxes, it would be helpful to get an approximation of the amount of data and file space a seeding job will need. I have on numerous occasions hit storage limits as a developer sandbox only has 200 megabytes of usable space.
1 vote -
Add an option to ignore ".forceignore" files
When a repository contains a forceignore file, deployments to that repo will not include these elements.
Sometime however it might be necessary to explicitly deploy these elements (e.g. manually).I propose to add a flag "Ignore .forceignore" at least for manual comparisons + deploys to be able to still push generelly ignore components to the repository.
1 vote -
Show duration for comparison jobs
While the Comparison History screen shows when a comparison job was initiated, it would be extremely helpful to display the duration of that comparison job, from when it was initiated, to when it was completed.
Ideally, this would show on the Comparison History screen, and/or on the actual Comparison screen itself after it was completed.
2 votes -
Seed Data alongside Feature Branch Promotions to Orgs
The idea is to bundle the data that should be tested along with the feature branch, so that once a story is deployed the data is also available (similar to one of Copado's features).
This allows us to test regardless of dev, partial or full copy sandbox type. Allow for a set of data to go along with a feature for testing reports and analytical tools. Possibly integrate existing Seeding Templates that can be paired with a feature branch. Allow for configuration of data deployments to environments through the CI job for feature+data deployments. Allowing some environments to refuse the…
1 vote -
Add navigation into elements of LWC bundle in difference viewer
The current LWC difference viewer shows the components linearly from top to bottom - meta, css, html, js. Just like you did with the side bar navigator for layout, add a side bar navigator for the LWC bundles
1 vote -
Allow developer sandbox updates to be queued instead of failing
When you update developer sanboxes you can only do a max of 2 at a time or else the extras fail and do not automatically retry when the other are done. I would like if they would just enter into a que so that you could click update on all of them and not have to wait until the first 2 are done to then click the next two.
1 vote -
Update all developer sandboxes with one click
Deploy updates to all developer sandboxes with one click
1 vote -
Promotion PRs should show the original author on GitHub enterprise
Hello, according to the documentation here - https://docs.gearset.com/en/articles/8545155-why-are-my-prs-showing-the-pipeline-owner, promotion PRs created by Gearset in GitHub can show the original author of the PR. After talking with support, they told me that this feature is not supported for GitHub Enterprise. Could this be made available in Github Enterprise, as it is now in GitHub?
1 vote -
Promotion PRs should show the original author on GitHub enterprise
Hello, according to the documentation here - https://docs.gearset.com/en/articles/8545155-why-are-my-prs-showing-the-pipeline-owner, promotion PRs created by Gearset in GitHub can show the original author of the PR. After talking with support, they told me that this feature is not supported for GitHub Enterprise. Could this be made available in Github Enterprise, as it is now in GitHub?
1 vote -
Git Delta Deployment
I think it would be great if Gearset pipeline feature changed to do a pure Git delta deployment instead of a Git/Org delta deployment. The reason for this is that then you only deploy your work (or what has changed) instead of deploying potentially any differences between the given branch and your org. Here's more information on this concept: https://developer.salesforce.com/blogs/2021/01/optimizing-unpackaged-deployments-using-a-delta-generation-tool
1 vote -
Auto pull in Commit descriptions into pull request description
Create a button in the pull request creation screen that allows you to pull in all commit messages into the pull request description field automatically.
1 vote -
Prevent Pipeline Paths from crossing Static or Developer environments
Sometimes depending on how you setup the pipeline you can end up with pipeline paths crossing/going under static environments and developer sandboxes.
This gives the impression that they are connected when they are not.
I would like it to look like this: https://drive.google.com/file/d/1s59BS47wEuHFA8Grb0SLdFSH00AgWw0W/view?usp=sharing
But it ends up looking like this: https://drive.google.com/file/d/1BLFrHd0HTR9LTLSoUw_34BqAWgvDa1SO/view?usp=sharing
1 vote
- Don't see your idea?