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.
165 results found
-
Avoid going to Setup | Deployment status on "validate deployment don't run any tests"
If you are deploying to PROD and
a) You have Apex classes in your deployment
b) You choose Validate Deployment - Don't run any testsThe Validation will fail and Gearset will tell you to check the target org Setup | Deployment Status where as suggested, the most likely cause is test coverage failures.
This is in fact true but it seems that Gearset could warn you before acting on a PROD deployment with non-test apex classes and 'don't run any tests' that this will be guaranteed to occur and give you a chance to reconsider your choice before wasting…
1 vote -
Access to Critical Updates
We use Gearset as our primary utility for managing various client orgs include Production and Sandboxes for Testing and Release Management. It would be great if there was also a way to access, review and potentially enable/disable any Critical Updates in any org from Gearset.
However, I do understand that Critical Updates may not currently be accessible from the metadata API.
Just a thought,
Mike1 vote -
Filtering by user across the app
Filter deployment history & automated jobs to only show a specific team member's activity (e.g. mine). With large teams, the history pages can get too busy and makes it difficult to find the results I'm interested in.
1 vote -
Specified Test Level Suggestion
Hello,
It would be very nice to be able to have a test classes suggestion when doing a deployment with "specified test level". The suggestion will ensure the package elements will be covered at least by 75% and so speed up the deployment.
1 vote -
Filters
Edit "Existing Saved Filters" on an "Existing CI Job"
If using a saved filter on CI job, there is no easy to update an existing saved filter from the CI job directly.
Here is my current workflow:
Start a new compare and edit / save the filter from there, then going back to the CI job, refreshing filters and reselected the saved filtered.
If multiple CI jobs are setup it's easy to miss some jobs which are dependent on updated filter.
Alternative solution - Provide toggle to update all related CI jobs which use the filter.
0 votes
- Don't see your idea?