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.
1236 results found
-
Inline Editing of metadata
Inline Editing of metadata
In order to make our deployment successful we had to download the package, modify the version numbers on the flow definitions, and then compare the local package to the target org. It would be very helpful if we can edit the metadata XML in the UI so we can fix the version numbers.107 votesHello. A large number of commenters requested the ability to carry out value replacements as part of metadata deployments.
Gearset now offers a feature called Environment Variables that lets you do just that!
It works with both manual and CI deployments and lets you target either a Salesforce org or a Git repo of your choice. And, for a number of key metadata types, you can even specify the exact 'field' where the replacement should take place.
If you have any feedback on the Environment Variables feature, please open a new feature request or simply let us know in the in-app chat.
Thank you for upvoting this feature request and we hope that you will find the Environment Variables feature useful.
Blog post: https://gearset.com/blog/environment-variables/
Support doc: https://docs.gearset.com/en/articles/5557015-using-environment-variables-in-gearset
-
Add merge functionality to the diff tool
Extend the diff tool to allow the user to perform a merge, creating a new version of the component that contains some changes from the source version and some changes from the target version. This would be very useful in a team development scenario where multiple devs are working on features in individual dev sandboxes and then pushing completed features into an integration sandbox.
82 votesMerging differences between Apex classes and VisualForce pages is difficult to do automatically due to the understanding required by the developer. For differences between two orgs in other object types, Gearset helps you sidestep that with our granular comparison results. This blog post explains more: https://gearset.com/blog/merging-salesforce-metadata
-
Provide the option to ignore whitespace differences in Apex
It would be great to have more control over the diff process - particularly to be able to ignore whitespace changes.
If I've made an actual function change to a class, and also auto-indented it, then it would be a lot easier to see the important change if I could hide the whitespace-only changes.
Having the ability to suppress whitespace-only changes on the list of changed objects would be really useful, too.
70 votesThanks for the suggestion.
We have plans to improve the way the diff viewer handles changes and whitespace in the future, though it’s not currently under development.
Thanks,
Jason. -
Add an auto-save feature while building deployment packages
As Gearset is run through a web browser, if the browser happens to freeze while a package is being built, you don't have the opportunity to save it as a Draft Deployment. An auto-save feature would allow someone to pick up where they left off, or when the last auto-save was done, without having to start from scratch.
51 votes -
Allow individual lines to be selected for inclusion or exclusion of a deployment
Allow individual lines to be selected for inclusion or exclusion of a deployment
46 votesEDIT:
Gearset now lets you select specific fields in layouts for a deployment.
Here's a quick article on getting started with precision deployments for layouts:
https://docs.gearset.com/en/articles/6407322-getting-started-with-precision-layout-deployments
We are working on adding support for more metadata types such as record types, value sets, Lightning pages and other XML types.
-
create an option to have chained deployments
create an option to have chained deployments so complex deployments can be broken down and sequentially deployed or slaves can be ran
allowing for multi staged deployments under one CI job
41 votes -
Support package.xml filtering when using Git comparison with a SFDX folder structure
When using a git repo with a SFDX folder structure + package/xml (in the /manifest folder) gearset dos not take into account elements in the package.xml when checking the option (filter with package.xml)
41 votes -
Ability to chose multiple targets for a deployment
It would be nice to be able to deploy to multiple environments all at once from one source.
35 votesWe're currently reviewing how we can facilitate deployments to multiple Salesforce instances simultaneously. Please let us know how you manage this currently, or how you would like to manage it - thanks!
-
Allow adding "No Difference" items to package. To help with package reuse to multiple orgs
Allow assets with "no difference" to be added to a promotion to allow the same package to be used to both promote as well as sync other sandboxes (without having to manually check if asset was changed in each).
31 votes -
Stop the reordering of XML when deploying to git
At commit to branch, Gearset reorders large chunks of the XML file. This causes additional deltas (seen in the hundreds of lines) and merge conflicts.
30 votes -
Ability to copy Territory models from one org to another
It would be great to be able to copy Territory models from one org to another, as per this request in the SFDC Community...
https://success.salesforce.com/ideaView?id=08730000000DgemAAC29 votes -
Integrate with Agile Accelerator instead of just Jira
Integrate with Agile Accelerator instead of just Jira.
It would be great if Gearset (and ideally the Pipelines-feature) could integrate with Agile Accelerator.Since we're a Salesforce-partner we want to use as many Salesforce-native solutions. That's why we've been happily using Agile Accelerator for many years.
It would be great if Gearset can also integrate with Agile Accelerator instead of just Jira.
Right now the Gearset Pipelines feature isn't useful to us, because of this sole reason.Thanks for considering this!
28 votes -
A configuration to prevent deployment from certain Sandbox Org into Production org
In most of Tech industry deployment lifecycle, all code or config changes are ideally pushed into production only from a FullCopy Sandbox(Commonly Known as Staging Environment).
It would be very good to have a feature in GearSet App which if enabled shouldn't allow user deploying data from Dev/DevPro/Partial Sandbox into Production Org.
28 votes -
Choose Delete action per Metadata Type for CI jobs
In the past we had troubles deploying reports via CI, they were not showing/deploying, the workaround was to enable the filter to include all reports. This works to solve that, but now I am looking at including more into the repo and start using delete actions in the CI jobs as well. The downside is that because we have to have all reports in the filter, the CI job will delete reports created by users in non-private folders. A freedom we want to give certain users in Production.
What would be an epic enhancement (and solve this challenge) is if…
27 votes -
Add possibility to save custom filter RegEx for subcomponents
If you want to deploy new fields and field level security, I want to create a custom filter that hides all profile setting except of field level security and make that custom filter reusable.
Unfortunately RegEx only works on top level elements. In this case profile names. That doesn't make sense since that would hide field level security too.26 votes -
Explicitly set object-level permissions, even if these are omitted from XML provided by Salesforce API
Valerio recommended that I post this suggestion following a discussion on 29 August 2019.
Issue reference:
https://docs.gearset.com/en/articles/3226459-a-note-on-deploying-custom-object-permissions-on-new-profilesIssue:
1. Remove all object-level access for "Lead" from a custom profile in a source org
2. Deploy this profile to a target org
3. The profile in the target org will have access to the "Lead" object ENABLED, because this access is included in the Standard User profile (see document link above)The workaround (deploying and then deploying again) is cumbersome and not always practical, e.g. if making automated, one-step deployments outside of Gearset. Failing to make a second deployment means that…
25 votes -
Create Change set without comparison
Allow user to directly create a change set without doing the comparison. If user has a list of items that needs to be migrated then allow the user to add items and skip comparison step.
25 votes -
Quick deploy in pipelines
It would nice to be able to use the Quick Deploy feature once a release is validated, instead of either hitting deploy or scheduling the deploy and having it validate one again.
22 votes -
Set time on CI Jobs instead of running every 4 hours or 24 hours
Is it possible to set time Instead of running CI Jobs every 4 hours or 24 hours.
22 votes -
Skip CI Jobs to source control when there are no changes.
After setting up a CI job from a Salesforce sandbox to a Bitbucket repo, it looks like the CI job always runs a commit, even if there are no actual changes. It would be great to not have this happen to avoid having many commits where there are no actual changes.
21 votes
- Don't see your idea?