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.
1286 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 -
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 -
Link to salesforce source records
When reviewing a Comparison with Salesforce as a source or target, include a link to the Setup/Configuration page that is being compared. For example, a link to a Page Layout that the user could click to jump right to the Layout in the appropriate Salesforce environment. There are times when we review Comparisions and need to see the source outside of Gearset and this gets the user there much faster.
The link would appear in the header of the Comparison window, near where "SOURCE" and "TARGET" are listed.
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 -
Monthly sandbox refresh from production
I would like the ability to refresh a sandbox from production on a scheduled recurring basis on a monthly cycle (ex: from prod to a full sandbox) so as not to overwrite current development items that are in process or testing.
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 -
Improve CI validations jobs - allow incremental comparisons with Github Pull Request/Push Validations
Currently, the only way to validate a branch, push, or pull request is to essentially have gearset pull all metadata from the repository and the org.
This can result in a long wait time for validation. It'd be great if we could have quicker turnaround for users to get feedback after a push/pull request.
Since github/provider of choice would have the exact metadata that changed in the push/pull request, it'd be helpful to only have gearset pull the metadata that actually changed to limit how much time is spent simply pulling all metadata to make the comparison.
2 votes -
Include Apex classes imported into LWC
Ensure that Apex Classes imported in LWC javascript files are included in dependencies.
2 votes -
Ability to Compare metadata filters
When we have too many metadata filters, it is getting hard to keep track of them and figure out the similarities between them. It would be great to have an option to compare custom metadata filters.
2 votes -
Add 'run selected tests' in nightly scheduled Unit Tests Jobs.
We can select which tests run in Validation. It would be great if we could do the same in a nightly monitoring job.
2 votes -
facilitate selection at the UI of related permissions for selected items during deployment
Our typical use case surrounding related permissions for selected components (application visibilities, class accesses, field permissions, layout assignments, object permissions, page accesses, record type visibilities, tab visibilities) is to need to ensure that if a component is selected, its related permission is always selected also, with respect to a target set of profiles. We suggest you provide an affordance at the UI that selects related permissions en masse rather than requiring individual mouse clicks for each permission selection as at present.
2 votes -
Export test run history
Exporting the Test run history to Excel/CSV will allow keeping trends.
The ultimate goal is to include this in a dashboards. If an embedable web page could be generated with solely the trends, that would be perfect.
2 votes -
Distinguish between code changes and just API metadata changes for Apex in Comparison Window
For large code comparisons, it'd be great to have the ability to see when it's just a change in API vs. actual differences. Right now, you'd have to click on every row to see what the actual change was.
2 votes -
Webhook trigger when Pull Request is Completed in Azure DevOps
Continuous Integration job to trigger when a Pull Request is Completed in Azure DevOps
2 votes
- Don't see your idea?