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.
1307 results found
-
Add an Ignore option for change alerts
Sometimes metadata comes back from Salesforce in a different order, which makes it look like there was a change when there really wasn't any. It would be nice to have a way to flag such comparisons as Ignored so I know I looked at them and decided that they didn't need to have any further action.
1 vote -
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 -
refresh comparison UX - echo the filter used in the original comparison
When you click Refresh Comparison, the dialog does not echo anywhere the original filter name used in the comparison-being-refreshed. You just get a x/y filters being used.
Always good to remind the user as to which filters were originally selected without having to scroll through the list
1 vote -
Issue with Namespace while deploying from Org A to Org B
the namespace if referred in code, we try to deploy to target Org, the target Org will not have the same namespace name, or will be a different namespace, it gives errors, can something be done to fix this?
1 vote -
Provide link from standard field to Standard Value Set
Some of the standard picklist fields in Salesforce have their values defined in Standard Value Sets. This means when you add a new value in the Salesforce UI, for example in the Type field of the Case object, that you are actually editing the CaseType Standard Value Set and not the Case Custom Object.
Gearset detects all these differences, but it isn't obvious why Case.Type appears as unchanged in a Gearset comparison. It would be better if Gearset showed some help text in the Case.Type object definition that pointed me to some help docs or linked me to the exact…
2 votes -
Display "Metadata comparison (custom) filter" used on "Comparison in progress" -screen
Hi! I just started to evaluate Gearset. Looking good. When I was staring at "Comparison in progress"-screen this came to my mind:
Sometimes it takes a bit longer than expected and I start to think: "OMG - What custom filter I used? - Probably I'm comparing everything - That's why it takes so long - Maybe I should cancel this job?".
It would be more reassuring if the Metadata comparison (custom) filter being used was also shown on that "Comparison in progress" screen.
4 votes -
In comparison mode, remember whether I want to see the XML view or a friendlier view of the object I'm looking at.
I noticed that the non-XML option label changes depending on what type of object I'm looking at. Regardless, if I select the non-XML option in comparison mode, I'd like the site to remember that option during my session so I don't have to keep re-clicking the non-XML option for each line item.
1 vote -
Simple visualization showing Process Builder differences
Assuming the high-vote count Idea for matching on latest version Process Builder flow between source and target (and not by version #) is implemented; make the visual comparison between source/target PB not solely XML.
Process Builder in XML can't be deciphered by a human mind. Hence, a simple indented text-based visualization could be done to make it more readable
- Decision 1.1 Entry criteria 1.2 Immediate actions 1.2.1 action 1 details (XML here OK) 1.2.2 action 2 " " 1.3 Scheduled actions 1.3.1 scheduled action 1 (XML here OK) ...
- Next decision ...
There's an implicit tree layout in the PB…
3 votes -
Improve detection of custom fields on Managed Package objects coming from Git
If I have a managed package object in Git, Gearset does not recognize it as managed package code in its comparison to a Salesforce org. This is a problem since it may not recognize a change if a custom field has been added to the managed package object.
16 votes -
Be able to switch the direction of a comparison/deployment
Sometimes we need to reconcile changes on an object between two orgs, where some of the changes have been made in Org1 and some in Org2. Having set up metadata filters, compared and deployed required changes from Org1 to Org2, it would be nice to be able click a button to switch direction to then deploy required changes from Org2 back to Org1, without having to go through the whole process of setting up a new comparison.
5 votes -
Scheduled deployment freezes
Prevent deployments during certain periods of time for a team or for production environments
10 votes -
FogBugz integration for Gearset
We'd LOVE a FogBugz integration for Gearset similar to the new Jira Integration.
https://docs.gearset.com/feature-walkthroughs/integrating-with-jira
4 votes -
Avoid Analyzer suggesting to deploy a workflow's Sobject when such SObject and all referenced fields exists in the target
Use case:
1. Deploy from source to target a changed Workflow (from active to deactivated)
2. Target already has all of the workflow's referenced components (fields used in filter criteria, fields used in Field Update)Analyzer will tell you "Add the following to the deployment" and something that looks like:
Deploy All
- object.WfName
-- object and its subcomponents
-- object and its subcomponents
-- object and its subcomponentsSince the object is already in the target as are the subcomponents, this message is alarmingly misleading and could inadvertently lead to deploying an object not yet ready.
The above message…
1 vote -
Improve PermissionSet comparisons by providing an option to ignore fieldPermissions when their editable/readable are set to false
Current Metadata Behavior:
When a new object is added, objectPermissions are only added to a PermissionSet only if one of allowCreate, allowDelete, allowEdit, modifyAllRecords, viewAllRecords are set to true
When a new field is added, the new fieldPermission is added to all PermissionSets by default (with editable and readable set to false).
NB. PermissionSets are additive in behavior and can only open up access not revoke. Values of false have no meaning and are only noise.Current Gearset Comparison Behavior:
Comparing PermissionSets show these new fieldPermssions as New Items even when default values for editable, readable are set to false.…9 votes -
Show Workflow Activities As Dependency of Parent Workflow
When selecting a Workflow Rule, its dependent components (i.e., email alerts) are not shown in the dependency view. They should be.
2 votes -
Allow "Rollback" if you have a user within the same org
Rollback currently requires the user who did the deployment to enable "Deployment" user access. Instead, it would be helpful if I could use my own user, within the same org, to do the rollback.
This would be helpful if the individual who did the first deployment is unavailable.
4 votes -
Support for zipping and unzipping static resources in GIT repos.
Add support to automatically unzip zipped static resources when migrating to a GIT repo and re-zipping when migrating to SF. This would allow me to edit my static resource files without having to manually unzip them.
2 votes -
would be cool to be able to "ignore" certain differences
would be cool to be able to "ignore" certain differences... e.g. encryption. So if encryption is enabled in a Production Org but not in a Sandbox (not sure if Encryption is possible for SBs), you have a difference for every custom field <encrypted>true/false</encrypted> which is really irritating.
18 votes -
Deployment of pre-valided package doesn't include accurate test counts
We did a deployment last week and noticed that as part of the deployment report that went out that it stated the Tests Run was zero. We did a pre-validation the day before where we ran all tests with all passing.
Could this test section on the deployment report again include/include the pre-validation tests that were run for the deployment?
3 votes -
Allow teams to share custom git repositories
It would be nice to be able to share custom git repositories with the entire team. At this time, each team member that does deployments needs to configure each custom git repo in Gearset. Besides requiring them to set it up, it also means I need to give each person the credentials.
4 votes
- Don't see your idea?