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.
1411 results found
-
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 -
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 -
Ability to carry out action after successful deployment or detect org changes (monitoring)
After every release, we have to do smoke testing. We do have automated testing using selenium and we wanted to trigger the automated testing every after release is detected. It would be nice if in the deployment we can call an api or webservice after successful deployment. Or in the monitoring we can call an api when there's a change happened in the org.
2 votes -
to add an option to not to run unit tests validation in CI job in case there are no changes detected
2 votes -
Account owner should be able to delete templates created by others
If a team member is removed from Gearset team, any template or previous activity can not be removed by anyone else. Leaving some clutter behind. It would be good to have the Owner of the Gearset account/team to have a super admin level access to all templates/data created by other team members so clean up could be managed....
2 votes -
Support multiple SFDX projects for a custom GIT repo
When comparing / deploying using a custom git repository, containing multiple SFDX projects, present the user with the ability to select which SFDX project to compare / deploy, either by package.xml or sfdx-project.json. Currently Gearset fails and reports multiple sfdx-project.json were found.
[
{
"UserReadableError": "This repository has 2 sfdx-project.json files: Gearset cannot determine which one to use",
"ErrorType": "ErrorFromSource"
}
]2 votes -
Distinguish between process builder and flow
If you do deployments of flows and processes from process builder, both of them are handeled as a flow. If you need to activate the flow or process manually in a production org, you need to guess if it was a flow that you have deployed or a process.
Please within the deployment report (and the comparism), distinguish between flows and processes.2 votes
- Don't see your idea?