As Gearset is run through a web browser, if the browser happens to freeze while a package is being built, you don't have the opportunity to save it as a Draft Deployment. An auto-save feature would allow someone to pick up where they left off, or when the last auto-save was done, without having to start from scratch.

Such as Selenium and/or Cypress.io

If the only difference in the field is that History Tracking is turned on, it would be nice to filter these results out.

Running checks on our app with multiple customers, who all set history tracking differently, can create a lot of noise to filter through to find actual differences.

Today the ability is not there to allow for viewing multiple repositories within AWS Code Commit. One can view a singular repo and the branches that it contains.

In our instance we have different repos for our various instances. We would like to be able to have the ability to go on level deeper and be able to first choose the repo, then choose the branch.

Hit me up with any questions please.

In the Deployments > Comparison History view, there is currently the action to "View Comparison" but it would also be nice to have a "Refresh Comparison" button next to it.

Currently, you can select a VCS repo and branch to use for comparison. It'd be great if you could select a specific commit from that branch, so that you're only looking at an atomic set of changes. This would allow for fine-grained comparison and deployment of changes.

Build a Jenkins Plugin to integrate with Gearset that would allow triggering CI jobs and/or deployments.

Please provide an API for querying deployment info such as friendly names, components, deployment notes, etc...

Support the ability to group org credentials on the Manage Orgs page by a new Group Name attribute. In managing multiple clients with dozens of PRD and Sandbox orgs it would be extremely helpful to be able to group and filter related credentials by client. However, to expand this feature to support multiple use cases, providing a new Group Name attribute (text) which could contain any value would be fantastic!

Thanks for your consideration,
Mike

Support automated webhooks into Jira Cloud for:
- Creating a new ticket when automated tests fail
- Updating existing tickets with deployments using the standard Atlassian smart comment format "[TicketID,...] some comment"

When a dev team work on a shared deployment, it would be nice to work on the same deployment draft, at the same time. At a bare minimum, it would be good to be warned that someone is updating the draft at the same time as you.

It would be great to be able to copy Territory models from one org to another, as per this request in the SFDC Community...
https://success.salesforce.com/ideaView?id=08730000000DgemAAC

Often times I find myself updating 1 or two files since a prior comparison. Rather than refreshing the entire thing which can take a while, it would be nice if I could specify which ones to refresh.

I'm aware that I can set which metadata types to compare, but even in large orgs, the 4 or 5 common ones can still take quite awhile from a full refresh.

Thanks!

When deploying, there's a pain point when we want to specify tests to run. It would be nice to have an option to only run test classes that are included in the deployment. Automatically identifying which test classes are in the deployment package should be fairly straight forward:
`grep -ri @IsTest ./src/classes`

Download the zip package at an earlier stage before the analysis has taken place.
In big Orgs with multiple teams working the analysis page takes sometimes to load so it would be a great addition if we can download the zip package file and modify it.

Sometimes a user may forget to add in a commit message before deploying, so the history in our source control is "no commit message" which is not editable. Can we add a feature to be able to turn on marking commit messages as a requirement for deploy?

When a CI job fails, the bad code remains in the GitHub repo. I'd like to see a way to revert the commit/PR that caused that failure so that any CI jobs for new, unrelated, commits/PRs won't fail while the developer is working to resolve the issue.

I would like the ability to print the current comparison for selected objects before deploying to use for documentation purposes.