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.
1138 results found
-
Global Search feature
It would be very useful to have a Global Search feature within Gearset. This would be used to search the contents of all metadata objects.
My use case is that sometimes a string has been hardcoded inside a function. The only way to find the function that contains the string is to manually trace through the code. The global search would indicate the function that contains this string.
Another benefit would be to track dependencies for metadata objects that don't support dependency tracking. For example Aura Components, we could search for the component name.
9 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 -
The Action Order in the XML should follow the sortOrder
Sometimes there is a difference between a object because the order of the platformActionListItems are different. Sometimes an item with order 0 comes first, but it is possible that an item with 9 comes first. This is probably an error in Salesforce API, but Gearset should order this list before the comparison so 0 will always be the first item.
2 votes -
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 -
Workflow failed to deploy without error, due to standard object dependency
In a CI job : Validation shown as success & Deployment shown as success. But actually no workflow deployed due to it being removed in the Problem Analyser.
The Problem Analyser triggered due to the (standard) object, that the workflow depends on, not being in the comparison results.
In a traditional deployments object is not needed to deploy WF, that too standard object. I feel it is a gap - problem analysers should never fire on object dependency.
1 vote -
Workflow failed to deploy without error, due to standard object dependency
CI job : Validation shown as success & Deployment shown as success.. but actually no WF deployed. Saying Opportunity object doesn't exist in target just because it was not selected in the components. in a traditional deployments object is not needed to deploy WF, that too standard object. I feel it is a gap.
1 vote -
Automatic retry for Unknown Error in scratch org creation
When creating a new scratch org from either the Gearset UX or via a CI job, one often gets the Unknown Error message
Gearset should attempt to retry this error as often, a simple retry works. This is especially important for CI jobs which should not have to be attended to manually.
Of course, the better solution is to not get this error at all
2 votes -
Make CI-created scratch orgs more usable by downstream webhooks
If a CI job creates a scratch org ; and you configure an outgoing webhook in the CI configuration, the subscribers to that webhook have no way of being able to connect/authenticate to that scratch org.
The typical use case would be to run automated UX testing (Provar, Selenium)
At present, even the CI job creator can't log into the CI-created scratch org let alone any CI webhook
In addition to supporting this, there should be doc on how a downstream webhook can access the scratch org to then do useful work.
2 votes -
Add Static Analysis Notifications
For org monitoring, we can get a notification on either every run, or when the org changes.
Could we also have the option to get notification when the number of static analysis problems increases?
2 votes -
Link Static Analysis results to the code
Could we link the file names in the static analysis results to the actual code from the comparison/monitoring job?
i.e. Where the results have a list of issues per Apex class, I'd like the class name to be a link to the code for that class
Having a quick peek at the code from within Gearset can help me to diagnose whether it's a genuine problem, or something where the static analysis rules need tweaking.
If it's just the rules that need tweaking, it would be nice to be able to complete that job entirely within Gearset.
1 vote -
Choose Delete action per Metadata Type for CI jobs
In the past we had troubles deploying reports via CI, they were not showing/deploying, the workaround was to enable the filter to include all reports. This works to solve that, but now I am looking at including more into the repo and start using delete actions in the CI jobs as well. The downside is that because we have to have all reports in the filter, the CI job will delete reports created by users in non-private folders. A freedom we want to give certain users in Production.
What would be an epic enhancement (and solve this challenge) is if…
27 votes -
Allow standard linux path in sfdx-project.json
if path contains "./force-app" a bug appears, if we write "force-app" it works. so first one should work to
Repro step :
{
"packageDirectories": [{
"path": "./force-app",
"default": true
}],
"namespace": "",
"sfdcLoginUrl": "https://test.salesforce.com",
"sourceApiVersion": "48.0"
}Result :
Comparision failedExpected Result:
Comparision Ok2 votes -
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 Additional Deployment Preferences for JIRA integration
Currently the Jira Ticket Deployment Preferences don't give you enough options to manage the expected behavior with our process. Right now there is too much noise on our tickets and we want the option to reduce that. For example, we do not need to comment on the ticket when attempting to validate deployment, just as we don't need it for failed deployments (which you already have as a feature). We simply want a comment with the deployment notes when a deployment is made since this would reflect the actual system changes that took place with this feature/issue.
3 votes -
Show test apex run in the deployment report
When we validate a deployment then schedule it for deployment. Once deployed we receive a report however the tests run do not show here and you have to back to the validated section to find them - please include the tests run on the final deployment report
2 votes -
Select a set of data deployment templates and run them in order
Ability to build sequence of data load (choose a list of data load templates and have to possibility to run them automatically in sequence). The sequence can be changed.
10 votes -
Be able to log into scratch org from Deployment Success page
It would be super convenient to log into the scratch org directly from the Deployment success page
- From Compare & Deploy sequence
- From CI success
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 -
Move the configured regex filters to the top of the scrollable pane (currently at bottom) of
Move the regexes to the top of the pane so one can see they exist and not have to guess that they exist at the bottom of the pane.
Note the example, selects all custom objects - this is useful for ISVs
example: For custom object, there are 100+ entries for standard and custom objects. If you add a regex, it appears at the bottom of the scrollable pane, after all the enumerated objectnames. Coming back into a custom filter, it is not obvious that you had even created a regex as you would have to know to scroll to…
1 vote -
Enable tracking / comparison of code not in the force-app/main/default folder
SFDX officially supports tracking of source within the same package in more than one folder. The "standard" folder may be used, but you are also able to create a folder hierarchy that's more akin to a "modularization"
It can for example look like this:
force-app (any names goes here)
-> main
--> default
----> aura / classes / pages
-> module1
--> aura/classes/pages
-> module2
--> aura/classes/pagesCurrently, only the metadata inside the force-app/main/default folder is seen. It would amazing if git integration could take other folders into account too. Both for Deployments from and to Git (for…
2 votes
- Don't see your idea?