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.
4 results found
-
Compare active versions of flows (processes)
When comparing flows (processes) between environments, Gearset appears to try to match on flow version number, even though different environments are likely to have different numbers. It seems like it would probably be more helpful if the comparisons were between just the active versions.
12 votesThis is no longer applicable now that v44 of the API is released:
https://docs.gearset.com/en/articles/2439855-changes-to-flows-in-v44-of-the-metadata-api -
Only show connected source types when starting comparison
When selecting the source or target environments the list currently shows me all connection types including those that I haven't connected. For example, I connected Salesforce orgs and a bitbucket account. When
I start a comparison or create a CI job, I can still select in the source/target type GitHub, AWS etc...This is super annoying when setting this up for admins that are already confused by the change of process.
1 voteHi Jannis,
On balance we believe that removing all other connections to the Git providers we support will harm discoverability for a larger number of people using Gearset so have decided not to change the current approach at this time.
Regards,
Stephen
-
Detect global picklist dependency
When I deploy a custom field that uses a Global Picklist which does not exist in the target, Gearset does not currently detect that I need to include the Global Picklist in my deployment.
It would definitely save some time if it could tell me that.
4 votesGearset supports dependency analysis on Global Value Sets, which have replaced Global Picklists.
As Salesforce is recommending everybody move to the newer metadata types, we won’t be adding support for this legacy component type.
-
1 vote
- Don't see your idea?