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.
239 results found
-
Only see deployment history for Orgs you have access to
We would like to only see Deployment History for the Orgs we have access to. Our clients brought this up as a concern during our deployment meetings.
1 vote -
Create Scratch Org dialog should echo DevHub name
When you Create a Scratch Org, the dialog that appears doesn't echo the DevHub name used to associate the scratch org. Since one's Gearset user account could be authorized to multiple DevHubs, one loses the thread (breadcrumb) to which DevHub is being used for the new scratch org
1 vote -
Add NotificationTypeConfig metadata type
There is a new metadata type in API 48.0 NotificationTypeConfig. It would be great if you can add it.
https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_notificationtypeconfig.htm1 vote -
inform users they're logged in somewhere else when failing concurrent logins
When a user might attempt to log into their account from a second computer (or VM), its appropriate to fail their login on the second computer. Right now, there is no indication that this has occurred because they're already logged in elsewhere. The error talks about adding Gearset IPs to Salesforce, but the issue is being logged in already.
I suggest telling us we're already logged in. It's easy to forget!
Thanks!
1 vote -
Ability to clone deployments and include non-different (same) metadata items.
I would like to be able to Clone a deployment and include all of the metadata from the cloned package, even if there are no changes in the target org. This way I can incrementally build up a master package that includes all my metadata regardless of where I chose to deploy it.
1 vote -
Allow Username/Password authentication option when selecting target/source orgs during cloning a deployment package
Currently, when cloning a deployment package or re-deploying a package to a new target, it only works with OAuth authenticated orgs. It would be nice to have more of my available saved orgs to be a target/source when cloning a deployment. I am not able to authenticate a target or source using a My Domain or Username/Password with this method.
1 vote -
Warn about Email Deliverability setting
Warn users when they are about to deploy (data OR metadata) to remind them when "Email Deliverability" is turned on.
1 vote -
Ability to chose SFDX source format (force-app) compare or old style (src)
Add a checkbox to chose wheter we want a sfdx compare or an old one (in order to not let gearset chose for us)
1 vote -
1 vote
-
`Deployment history' User Interface update.
In `Deployment history' it would be great if when you choose a target and it opens in a new window. Deploying 48 packages and it is painful.
1 vote -
Support VS Code extension: ForceCode
Can you please support VS Code extension (ForceCode) source format so that we can use the extension to commit and include in CI jobs.
1 vote -
Email2Case Deployment for Selected Email2Case Setting
When deploying email2Case i am unable to choose particular email2Case that i need to deploy and end up choose all the email to case settings. Needed feature to deploy this selectively.
1 vote -
Plain text list export of metadata
There are times when I'm in an email thread with other developers and I want to share a list of metadata that I'm trying to deploy via Gearset. It would be nice to have a button after a validation or deployment (failure or success) that copies in plain text a list of everything in the deployment. The list not only has the name of each metadata, but also the type of metadata it is.
1 vote -
Reporting
have a way to dump a csv of the description of objects. i need to find a way to see what fields are encrypted.
1 vote -
Meta Data Searches
Ability to do a meta data search like you can in eclipse or visual studio in gearset.
For example search a custom field and where it is used within your org.
1 vote -
Provide the ability to run static code analysis on all commits to the repo
We'd like the ability to run static code analysis on all commits to a repo, regardless of the branch name. This would allow us to catch code quality issues early and up front, regardless of the branching model we use.
Example: https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow (development is done in feature-* branches, so there's no one branch we can configure a CI job on)
1 vote -
Gearset to do Sanbox Refresh by copying metadata and data from production
Quite often an Environment needs to be refreshed, but every time it happens all the integration breaks as OrgId changes. Gearset can move metadata and data, which when made together can be a solution for sandbox refresh. Full copy sandbox sometimes takes days, GS will be able to it quite quickly.
1 vote -
Create an rss or atom feed as you add new features
When working inside of Gearset, it often alerts you to changes that have been recently made. It would be nice to have these as a separate, consumable, feed. We have a slack channel that we would like to pipe those changes to, for instance.
1 vote -
enumerate unsupported metadata in Manage Custom Filters
In Manage Custom Filters dialog, Gearset should link to
a) https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_unsupported_types.htm
b) a Gearset list of Metadata API-supported but not yet GS-supported metadata typessaves devops person wondering why certain metadata can't be deployed
1 vote -
Add functionality to select the changes in the component for the deployment.
I think it will be very helpful to have a possibility to deploy only some selected changes in the modified component.
1 vote
- Don't see your idea?