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.
375 results found
-
Allow searching for specific fields in backups
Backups are currently only helpful if we know when an object was changed or deleted. However, we often run into an issue where an object was changed an unknown time ago, we have to spend a lengthy amount of time searching through backups. This is a very, very tedious process as you can't open backup runs in new tabs, so you have to click the link, go back, reset the date filters, and find where you left off. If we could use search criteria to filter data and metadata changes, that would help tremendously!
2 votes -
Ability to transfer Salesforce Org Connections to another user
I'm setting up my Salesforce Org Connections using an integration API Salesforce user account. It's a neutral account that isn't tied to any real person. Once these Org Connections are setup, I'm going to delegate them to other users, so they won't have to duplicate effort setting up their own Org Connections. It would be nice to be able to transfer these neutral connections to another user if I happen to leave the company or whatever.
4 votesTeam owners can set up team-shared Salesforce org connections. These connections aren't tied to a single user on the team, and any team owner can delegate access to the org connection.
-
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.
17 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.
5 votes -
Offer Canadian data residency.
We have clients in Canada that require data residency for data backups/deployments and even metadata deployments/processing.
Please add the option for a Canadian hosted Gearset account.
6 votesHi there,
We have now added Canada as a data storage location. You can head over to app.gearset.com - click on create new account and sign up for the same.
Thanks
Gearset team.
-
Create GitHub App as alternative to GitHub OAuth
Gearset currently uses OAuth to connect to GitHub, and the way that works is that the OAuth connections have permissions to all repositories that my user has access to, which from a security perspective is a problem, because if the github key were ever compromised, it would provide very broad access to customers GitHub organizations.
Security teams would feel much better with the ability to limit the scope of access to just one repo instead of all the repos that my GitHub user has access to, which can be accomplished by creating a Github App which can be installed for…
10 votesThis is GA for GitHub Cloud https://docs.gearset.com/en/articles/9965863-integrating-with-github-through-a-github-app
-
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 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.
-
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.
21 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.
-
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.
13 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 -
Filters
Edit "Existing Saved Filters" on an "Existing CI Job"
If using a saved filter on CI job, there is no easy to update an existing saved filter from the CI job directly.
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/
10 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.
-
Support org shape parameter for creating Scratch Orgs
Currently definition files are required for creating scratch orgs but there is no support in GearSet for the use of the sourceOrg parameter as per the sfdx documentation here : https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_shape_scratch_def.htm
4 votesWe’ve now released support for the Org Shape feature which is available when creating a scratch org.
-
Show deployment friendly name on Deployment successful page
On the "Deployment successful" page, I'd like to see the Deployment friendly name displayed. This would be much more useful than the Salesforce Id that is currently displayed.
3 votesReleased this week
-
Retain Deployment Friendly Name and Notes After Failed Deployment
When attempting to validate a deployment, and the validation fails, Gearset retains the deployment's friendly name and notes fields from the validation. The user can make any necessary changes to the deployment, and won't have to re-type this information when attempting it a second or third time.
I'd like to see this same functionality when dealing with a failed deployment that doesn't use validation. Validating a package takes two steps (long steps), and typically I only want to use this option when delaying a deployment. However I often use it anyway just so I can retain my data in these…
3 votes -
Select the fields to deploy during a data deployment
Hi we use the data deployment feature is it possible to only select some fields to deploy data from one org to another and not always all the fields on an object.
19 votesYou can now select fields to exclude during a data deployment
- Don't see your idea?