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.
1228 results found
-
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 -
allow multiple slack webhooks per scheduled monitor or test run.
I have multiple slack teams, I'd like the ability to hook up a monitor org, or a test run to send to multiple slack webhook urls.
Not super important, and I suppose I could get around it by scheduling a duplicate, but that just felt wasteful of everyone's API's. :)
1 vote -
Exportable metadata reports for orgs
Being able to export a summary of an org's metadata state for reference, prior to a deployment or as part of our reporting, would be great.
1 vote -
Have access to multiple pull request templates
Currently we can only access one pull request template named pullrequesttemplate from Gearset.
I would like to be able to access a list of templates.
This would allow us to have precise template for each team using Gearset.0 votes -
Identify different backup job types (full vs. incremental)
Today, it is not possible to identify the backup job type, so we cannot really distinguish between a full and an incremental backup. This would be helpful to get better visibility when a full backup job is/was running.
0 votes -
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 -
Email Notification whenever deployment is successful
it would be good if we can send email notification to Users whenever we successfully deploy components to specific Org regardless of CI job.
0 votes
- Don't see your idea?