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.
333 results found
-
Add ability to precision deploy custom applications and all other file types
The ability to select specific lines in files for deployments is crucial for org and project management, and should be expanded to all file types. For example it currently is not possible to only deploy a new tab in a custom application, without deploying all other changes in that custom app, which is not manageable with multiple projects/updates being worked on that application concurrently.
5 votesWe've added precision deployments for Custom Applications 🎉
Please get in touch if there's any specific metadata types that you'd like to see in precision deployments.
-
Partial environment variable replacement and wildcards
Some types of metadata, such as Platform Event Subscriber Configuration, have attributes identifying a user by username. As such, regardless of the value in the source environment, the value deployed to the target org must match the username pattern of that org.
For example, if the value in the source repo is <user>name@example.com</user>, when deployed to a sandbox, it must be <user>name@example.com.sandbox1</user>. From sandbox to sandbox: <user>name@example.com.sandbox1</user> must become <user>name@example.com.sandbox2</user>. And finally, when going from sandbox to production: <user>name@example.com.sandbox1</user> to <user>name@example.com</user>.
This could be solved by supporting environment…
7 votesYou can now use Regular expressions in the "Find what" field when defining environment variables, allowing you to do wildcard/partial replacements.
-
Option to exclude all custom fields during data deployment
Hi, We are doing data deployment from one production org to another production org and we have completed the migration of all records of a particular custom object but after completion of record migration the client wanted to migrate the files and attachments present in the records.
while doing so we do need to update all custom fields present in the records again as this could replace the updated records with old data from old production.
So we have used the exclude fields option but there is no option to select exclude all fields at a time we have to…
1 voteLive in the app as of 8th June 2023.
-
Precision Deployments for Lead Convert Settings
Precision Deployment is currently not enabled for lead convert settings metadata. 2 orgs may have different lead convert settings or we may not want to migrate all the mappings from one to other. Hence, this is a must have.
1 voteWe've added precision deployments for Lead Convert Settings 🎉
Please get in touch if there's any other metadata types that you'd like to see in precision deployments.
-
Refresh Comparison enhancements
When doing a "Refresh Comparison", allow only refreshing the source. Or to only refresh the selected items from the source and/or target.
Example, deploying from a git branch to a sandbox, refreshing the metadata takes a few seconds from git, several minutes from the sandbox (target).3 votesWhile not exactly one-to-one match, we think this UserVoice already delivers the desired outcome:
Thank you for upvoting this UserVoice request!
-
I would like the option to view the delta CI only changes within the comparison, like the agents who are helping me untangle issues
I would like the option to view the delta CI only changes within the comparison, like the agents who are helping me untangle issues. ask kevin slattery to show you.
4 votes -
support blank values and/or regex in the "Find What" field on Environment Variables
...support blank values and/or regex in the "Find What" field on Environment Variables.
I would like to replace the value in a field on a Custom Metadata Type with an environment specific value, regardless as to what the value is in the source file. Currently I need to specify an specific value in the source to be replaced.
5 votesYou can now use Regular Expressions with Environment variables.
Simply enter the regex value in the "Find what" field and tick the "Regex" checkbox before hitting "Add environment variable" button.
Thank you for submitting the requests.
-
Deleted matching rule not showing as difference when trying to commit
The deleted matching rule is shown as 'deleted' in the comparison but when trying to commit and moving to the overview screen it is shown as 'no difference' which makes it impossible to commit.
6 votesThanks for reporting this bug. A fix for this was released on the 30th June. You should no longer have any issues when trying to deploy deletions of the various "...Rules" types
-
Allow page layout field additions and removals to be selectable
As a user, when selecting page layout changes to include in my deployment, I would like to include only the fields I have added that are different from my destination environment.
Dev environments can be worked on by different people. There are times when a solution requires adding an existing field to a page layout to solve your user story.
At the same time, another user story may also be making changes to that page layout using different fields (removing or adding).5 votesYou can now select the exact fields and other layout items for deployment using Gearset's new Precision deployments feature: https://docs.gearset.com/en/articles/6407322-getting-started-with-precision-layout-deployments
-
Add an option to ignore package version differences in Apex classes
I see many differences between apex classes where the only difference is the package version(s), no difference in the code itself. It would be nice to have an option to filter these out so that only the apex classes are shown where the code is different.
18 votesThis was released on November 2nd, 2021.
Note this feature ignores package versions. Different package names will continue to be flagged as a difference.
-
re-add "re-authorize" link on compare view
After refreshing a sandbox, you have to re-authorize the sandbox-org. A while ago, there was a link to do so. Now we have to navigate to the list of orgs to re-authorize there.
Please give us back the re-authorize shortcut :)
4 votesWe have now added a 'Re-authorize' button to the access token expiry warning message that will typically appear when selecting Salesforce orgs with an expired token on the initial 'Compare and deploy' page.
-
Option to sort Custom Application XML
While this can be done with VSC custom plugins for SFDX, I think it would be really beneficial if Gearset offered the ability to sort Custom App XML in comparisons in order to see what's actually changing between a source and target for lightning page activations. Due to the way SFDC generates this XML, the way page activations are ordered is very difficult to follow, and I think it's an opportunity to make that easier especially for declarative config users of Salesforce.
6 votes -
Allow users to specify when to apply Environment Variables
A good feature would be to have some setting that lets you declare when you should apply environment variables. Since right now it is applied automatically during manual deployments and CI deployments. Perhaps in the wizard when you configure deployments there should be some option there to declare if environment variables should be applied or not?
We have some Custom Metadata and Custom Settings that always need to be updated post-refresh based on the new sandbox instances and it would be useful to use environment variables to set these values and deploy them one-time without them being deployed in every…
2 votesEnvironment variables will only be applied if its configuration as specified by the user (metadata type, item name, and a field for some types) matches the type and item name in the deployment package.
In all other cases, environment variables won't apply.
Added clarification in the Environment Variables config page:
"Environment variables will be applied automatically during both manual deployments and continuous integration deployments if the metadata item is included in the deployment package."
-
Add an option to ignore location changes for Flow
Hi, when reviewing changes for flows that are being deployed, it would be great to have a toggle option to hide or alternately color location changes which are just the location of elements on the flow canvas editor.
<locationX>1353</locationX>
<locationY>1305</locationY>Sometimes there are hundreds of location changes and it obscures the important information about what else changed.
22 votesThe "simply differences" toggle in the comparison grid now hides location changes in flows to make it easier to identify important changes. The location changes are still included when deploying changes to the flow.
-
add an option to sign commits with GPG key
If a source control space has enforced GPG key signature for all commits, gearset is not able to push any commits.
2 votesYou can now sign commits with GPG keys in Gearset. This article explains how to set up commit signing in Gearset. Commit signing is available on the Deployment Teams and Enterprise licenses.
Please let us know if you have any feedback via the in-app widget or by emailing team@gearset.com.
-
Identify that metadata is the same, even if ordered differently by metadata API
There are a lot of instances where the comparison will identify metadata as different, but the only difference is the way the API is ordering the XML. I've seen it happen a lot with picklist values on multi-select picklist fields. It would be nice to be able to turn this on/off somehow so that metadata that isn't truly different won't show up in the difference compare.
14 votesPlease see if anything else could be improved on in the feature description released in Nov 2021.
-
Populate Pull Request Templates from git providers
When creating a pull request directly in Gearset, it would be ideal to pull in the existing templates defined in BitBucket or GitHub.
A middle of the road solution (if GiHub or BitBucket's API doesn't support this) could be defining a pull request template in Gearset.
2 votes -
Ability to activate / deactivate Flows / Processes as part of the meta data and/or data deployment process
It should be possible to have gearset to deactivate flows and/or processes based on a selection. And to roll-back afterwards. Similar to what has been created here: https://sfswitch.herokuapp.com/
11 votesHi, thank you for voting on this UserVoice.
Flows can now be deactivated in Gearset alongside validation rules and triggers before data deployments.
Click the View and disable rules... button in the bottom-right of the pre-deployment summary page (next to DEPLOY DATA) to prepare a special metadata comparison.
To deactivate a flow, simply select & deploy its corresponding flow definition.
https://docs.gearset.com/en/articles/4536761-disabling-validation-rules-triggers-and-flows
-
Clone CI job without delta enabled
As the Gearset administrator for my team I want to be able to clone a CI job that is set as a delta job without the delta flag enabled so that I have less effort to create a brand new CI job.
Acceptance criteria:
- When closing a CI job with the delta flag enabled, give the option for the new job to now have the delta flag enabled.
- If the source and target are the same as an existing job, provide a visual warning of the potential consequences of replication of the job.
1 voteHi, this feature has now been released.
When cloning a CI job with delta enabled, you should now be able to toggle the delta CI checkbox when configuring the cloned job -
Ability to Name a Backup Run
It would be great if you could name a backup run.
Sometimes when backing up its handy to label in in case it was done for example before a deployment or large data load. Then this can be identified in the future or to refer back to it. Otherwise you need to remember the date and times! :)
1 voteWe've added friendly names to data backup runs! 🎉
Please get in touch if there's any specific places you would like us to display this friendly name in place of timestamps.
- Don't see your idea?