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

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

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

Currently only the creator (owner) of Schedule Test, Monitor Orgs and Manage Orgs can edit these activities. It would be helpful if we could designate more than 1 Owner for these activities. Similar to granting access to the various orgs (Comparison, Validation& Deployment) it makes sense to also include an Owner access as well.

If this is not possible, having a transfer ownership button would be helpful for each activity.

Thanks!

We sell a managed package and will never include standard objects in a comparison, and absolutely not in source control. When I'm running a compare against source control to check for changes, it will show all of the standard objects as "custom objects" which is not correct. I should have a way to filter out standard objects from the comparison.

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!

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.

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.

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.

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"

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

Filter on Custom Objects prior to running a comparison similar to Salesforce Change Set, select the required object and fields to compare

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,
Mike

We have a push topic that we use but there is currently no easy way to deploy changes between orgs. Would it be possible to do this via Gearset?

Use-case is where we have validated a package, but not been able to deploy it before expiry. Eventually, we are able to deploy it...

At this point, I'd like to be able to go from my validation package in the history straight to a comparison with the same objects selected. Then, I'll be able to make sure everything still looks good and validate/deploy again.