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.
241 results found
-
Schedule multiple gearset deployments
Have the ability to schedule metadata deployments along with data deployments. As of now, you must deploy all metadata then move into data deployments. It would be great to schedule these items in some sort of task flow.
2 votes -
One stop shopping for scratch org creation
Too many steps to get a scratch org usable for use - especially when compared to a CLI script.
If the model is VCS -> Scratch Org, then the following should be doable in one step:
1 - Create scratch org
2 - Populate scratch org with metadata in VCS
3 - Populate scratch org with SObject tree data from VCS (optional)By definition, the scratch org is empty so with a properly configured filter, the VCS metadata is implicitly all NEW and can be preselected checked
If the VCS contains multiple packages, then the pipeline config could identify which…
2 votes -
Ability to specify test suites when deploying apex classes. It would be easier when there are a large # of test classes involved.
Ability to specify test suites when deploying/validating apex classes. It would be easier when there are a large # of test classes involved with a deployment
11 votes -
Add filters & search to the Salesforce orgs page
Add Filter/Search to the Salesforce Orgs page. On Deployment History you have a filter that is very handy when sorting through the list to find a specific deployment. I am currently trying to add multiple new dev Orgs for a client and it is hard to sort through them all. Can you add the Filter/Search option on the Orgs page?
2 votes -
Jira Integration: Include the option to add a comment in JIRA with the URL of the pull request created from Gearset + Assign reviewers
After a deployment to a git branch, gearset allows to create the pull request from Gearset. It would be nice to:
1. Have an option to add the pull request URL to the deployment notes
2. Have the capability of add reviewers (users from the git repo) into the Pull Request5 votes -
API to provision users, assign users to connected organisations
API to provision users, assign users to connected organisations
It would be hugely benificial to us (60+ connected organisations, 25 employees working in teams for multiple clients at a time) if we could programatically provision/deprovision users and provide access to connected organisations via an api.
At the moment this is error prone manual work that has to be done by someone with high level access (and as such is usually already short on time).
6 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 -
Searching for work item should allow for searching by ticket #
When searching for work items to associate to a deployment, user should be able to enter ticket IDs rather then key words from the Azure DevOps ticket title. This will make it easier to search larger backlogs.
2 votes -
Support JWT authorization to DevHubs
If Gearset could authorize the DevHub using a JWT (requires DevHub to have a Connected App and Gearset to be given the clientId + server.key + username) ...
Then:
* Scratch orgs created by Gearset could be accessible to any other machine provided that machine is using the sfdx force:auth:jwt:grant command (same clientId, server.key, test.salesforce.com, and username of scratchOrg)
* This is a prerequisite to any outgoing webhook that wants to auth against the CI scratch org
* This is a convenience feature to IDE users who want to auth against a Gearset-created scratch org without having to get a…1 vote -
Migration/Deployment Path
In cases where you have multiple environments, provide an option to define a migration/deployment path; ability to define what environment is the source and what is the target. This will be useful in cases where we have requirement to deploy changes to say production from a specific environment (UAT).
1 vote -
Suppress the <deprecated> tag in CustomObject, CustomField
When retrieving metadata from 1GP packaging orgs, the <deprecated> tag appears in the source and, if you deploy to VCS, is preserved. But if you subsequently deploy to a scratch org, and back to VCS, the deprecated tag no longer appears in the scratch org and thus shows up as a diff in the Difference Viewer - confusing the user.
Doc says this tag is reserved for future use and until such time as it is used, suppress
1 vote -
Add ability to customize CI Dashboard
We have a number of different teams using Gearset with a number of different CI jobs. I don't care to see their jobs in my dashboard and they don't care to see my jobs on their dashboard. It would be great to be able to customize my dashboard so that I only see the jobs I'm interested in. Maybe it's some sort of flag on job to be able to add/remove from dashboard or maybe its a separate tab called 'My CI Jobs Dashboard' that we could default to when opening CI Jobs. Thanks for your consideration.
3 votes -
Tie scratch org URL to enumerated list of scratch orgs on My Connections
UX suggestion (tie list of scratch orgs to URL)
If you use Gearset to create a scratch org, the list of scratch orgs on the My Connections page does not tie to the visible URL of the scratch org you log into
This gets to be a real issue for the multi-tasker who might have several scratch org tabs open at once but has no way of knowing which one is which vis-a-vis the Gearset enumeration of how the scratch org was logged into the first place. Drilling into the user's name is too clunky
1 vote -
ability to filter on components
i would like to see the ability to filter deployments based on the components, just like the "Metadata comparison filter:" under Compare and Deploy option
2 votes -
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 -
Deploy permissions for Lightning Record Pages
provide a means of deploying the profile/recordtype/app permissions for lightning record pages without having to deploy the whole app.
4 votes -
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 -
Include support to name space filter to include option to include unlocked packages with no namespace
Currently there is no way to retrieve and compare components belong in an unlocked package with no name space without using the 'include managed package' namespace filter 'all' option.
this might include too many items that I am not interested in.
4 votes
- Don't see your idea?