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.
1140 results found
-
Display more workflow subcomponents under Workflow for Metadata filter
Currently, two sub-components display under Workflow when selecting metadata types within a filter.
- WorkflowAlert
- WorkflowRule
There's more sub-components than those two and I'd argue that there's two that are frequently used that should be included for visibility
- WorkflowFieldUpdate
- WorkflowOutboundMessage
There's 2 more, but these may be used less frequently and not needed for visibility
- WorkflowKnowledgePublish
- WorkflowTask
2 votes -
Github: Ability to select Reviewers for pull requests created in Gearset
Currently, you can create a PR after a successful deployment in Gearset. You're able to provide a description and even select it as a draft.
However, the only potentially necessary field that's missing is "reviewers". This means any CI/CD setup you have that requires an approval requires the user to go into Github just to add the reviewer.
Since Gearset would have all the team members (and those with linked github accounts), it seems it might be an opportunity to select based on that list and pass the linked username on to github in the PR creation to keep end…
2 votes -
Show/Flag what unlocked package elements are getting updated on Monitoring Jobs
When you look at the details of a monitoring job there is a field called "Packages Afftected" that shows green when is 0 and orange when >0.
There is a description that says...
Unlocked packages have been modified. View the comparison to see details.
However, when you look at the details there is nothing there to see what unlocked package element was modified. So the warning it is not very helpful at all.
Can this be implemented so that the warning is actionable.
2 votes -
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 -
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 -
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 -
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 -
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 -
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 -
Allow users to hide or collapse the middle bar of the comparison screen
I have a small laptop monitor, so screen space is pretty valuable to me when working from home. It can be difficult to do code reviews from a laptop monitor because of the middle bar, which takes up a significant amount of real estate.
I rarely use any of the controls or information in that box. It would be great to be able to collapse or hide it to allow more space for the top panel (list of metadata components) and the bottom panel (selected metadata contents)
2 votes -
Include the static code analysis report in the deployment notes so it can be integrated with Azure DevOps
We would like to have a link in the Pull Request or Azure DevOps work item to the static code analysis report so the tech leads can review the report.
2 votes -
Filter branches by tag name
In order to remove the clutter when selecting a branch to deploy to or from, allow users to apply metadata filters that dictate which branches show up in Gearset. For example, being able to specify that I only want to see feature branches.
2 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 -
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 -
Allow setting the default testing method for deployments
I want to enforce that any deployment into a UAT sandbox runs all the tests. The standard Default option runs no tests since it's a sandbox. I have to manually choose the "Run Only my Tests" Option every time I deploy to that sandbox. I would like to be able to have that option selected by default
2 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 -
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 -
Save draft deployment notes
Save draft deployment notes so when you combine drafts you can see all the notes from each single draft
2 votes
- Don't see your idea?