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.
17 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 -
Add "View on GitHub" and "Create Pull Request" options when target is Custom Git Repository
I've enjoyed using the view on github or create pull request options when my target is a github repo. However, when I use the custom git repository option which still points to my same github repo but doesn't require me to wait for all of my repo's to populate in the list, I'm no longer able to use them after a successful deploy. Please add "View on GitHub" and "Create Pull Request" options when the target is Custom Git Repository.
4 votesI’m afraid this isn’t going to be possible with a generic repository.
-
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.
-
Implement a Deployment Fish
Salesforce Change Sets support a Deployment Fish to entertain the developer while waiting.
It would be nice if Gearset could provide the same behavior.
2 votes -
Allow for bulk export of data deltas
Allow for export of data deltas so the extract can be loaded into a database for analysis using sql. This will enable us to view more clearly changes that have taken place and filter data to be edited
1 voteAfter speaking to the user on a call on 16-09-2020, the user confirms that there isn’t a strong enough use case to go forwards with this suggestion. So we will don’t have plans to investigate this further.
-
Custom metadata retrieval failure
Looks like with the recent Winter 20 patch sandboxes deploys are failing if custom metadata is included in metadata filter. We had to remove the custom metadata from the filter to get CI jobs to run successfully.
The error was 'Salesforce reported an error (INVALID_TYPE: sObject type 'et4ae5MCOAuthClientDetailmdt' is not supported.)' which isn't even a metadata type in our org.
1 vote -
Be able set a max number of items for CI Job
It would be great to be able to set a max value on max number of changes that will be pushed. We have some CI jobs that push translations, however, if all of a sudden there are 100+ changes that are going to get pushed when the usual rate is 10ish, i wouldn't want it to go through.
1 vote -
Make the Combine Packages feature available on the Pro tier
Having the ability to Combine Packages is helpful. However, this ability is only available to Enterprise Licenses. Our Salesforce developers move from our DEV to our Full Sandbox, and not having the ability to combine deployed packages means they must clone and copy or edit existing packages. They move bits of features as they develop in order to work with Agile methodology.
1 voteHi Donna,
We’re always monitoring the distribution of features across both our tiers, with the Pro tier primarily designed for smaller teams and single consultants.
Combined packages is typically used on larger teams with more complex deployment scenarios, and they’ll hopefully benefit from having the wider set of features in the Enterprise tier.
Thanks,
Kevin
CEO, Gearset -
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
-
UI Enhancement: Drag modal windows to reveal background
UI Quality of Life recommendation: let me drag the modal windows so that I can see what classes are being deployed, which will let me quickly specify tests without having to go back to my code base to look.
1 vote -
Monitor orgs - false positives in Clean Rules
It would appear that in the default 64 comparison set when using Monitor Changes, that SFDC may be returning fieldmappings in non-deterministic order when custom cleanrules are in effect as when Day n-1 org is compared against Day n org, the same cleanrule's fieldmappings are displaced some number of lines away causing a false positive. The obvious workaround is to remove Cleanrules from the metadata to compare but this means one can't detect true variances anymore.
1 vote -
1 vote
-
Desktop Application does not save to history
Desktop Comparison and Deployment not visible in the web history.
Was using v1.0.2.2021. Compared Source: Local files, Destination: Sandbox.
1 vote -
1 vote
Closed this as no information provided on the idea.
-
Allow PRO Licenses to integrate with Jira
With Jira integration only currently available with the Enterprise Gearset license, we are limited.
Our Salesforce developers work daily in Agile and use Jira. Since we purchases PRO Licenses, we cannot take advantage of integrating Jira for the Salesforce Developers. Currently only the Enterprise license provides this, but we don't want to hand out Enterprise licenses to every developer for obvious reasons. Please consider providing Jira integrations as part of the PRO license.0 votesHi Donna,
We do review the mix of features on tiers, but Pro is primarily designed for smaller teams or those that don’t need to collaboration features.
Jira is typically used by larger Enterprise teams, and so is on the Enterprise tier of Gearset.
Thanks,
Kevin -
Clicking Deployments tab should intelligently select the relevant subtab
When one is on the Deployment Results page, especially on a successful deployment, if one clicks the Deployment tab, the smarter default would not be the leftmost subtab (Draft Deployments), but the Deployment History tab.
Why?
a) You should as best practice enter a Friendly Name
b) You might be cloning the deployment into org A for immediate use into org B (in lieu of waiting 4 hours for a CI/CD job)0 votes -
Tag orgs & deployments
Tag orgs and deployment entries, then allow you to filter results by tag. This would help filtering down results by specific org (e.g. prod) or by a client or team member.
0 votes
- Don't see your idea?