Test jobs are only configured on time basis. When developer commit some changes and it will be deployed, but tests will be done on a time basis in 2 hours for example, so he should wait to know weather tests are passed or not. Or ask the release manager to run tests manually. So, this feature is must have improvement.

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

Not sure this is a bug or a limitation in the V40.0 SFDC Metadata API but it would appear that Custom Metadata Type (__mdt) listviews are not included in the Comparison (default 66). List Views on other Sobjects are included. Hence they can't be deployed

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.

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.

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.

Hey guys,

I am not sure if this is an actual issue or not but I will ask the question to see if I am missing something :)

When comparing email templates, the compare will return both email templates and folders. I have noticed that in my case, email templates that are part of a managed folder do not return. We can see the folder and sync the folder settings, but no templates. If we move the templates to a non-managed folder we can see the templates. Has anybody encountered anything similar?

Thanks!

Richard

Allowing customers to specify their own S3 buckets for storage could be beneficial for the product. This would give the customer enhanced security and control over their data.

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

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?

When I remove a page layout from my Git repository (the file and the package.xml entry) and then do a comparison to an org that it still exists in, Gearset fails to detect a deletion. It doesn't even show up in the All objects tab. It happened to me yesterday and then I just reproduced it now.

In the custom filters dialog, if you select a metadata type that is not supported by the API version, the compare and deploy currently just silently ignores that item, giving the impression that the compare has failed. e.g. selecting "Duplicate rule" with metadata version prior to 38.0.

It would be good for Gearset to provide a warning if a selected metadata type is not supported by the selected API version.

I find that I'm frequently copying to the clipboard the friendly name of the deployment into the notes of the next deployment or the friendly name of some other deployment. In addition to the pencil and delete buttons, add a copy to clipboard button

Note I still support other User Voice suggestions like auto-copying the deployment notes from Deployment X to cloned deployment Y or auto-defaulting the friendly name of the deployment from the deployment notes.

My use-case would somewhat be handled by separating code and xml differences, but I would like to be able to filter on difference count (or at least, easily see / sort by diff count).

For example: We are updating the API version on all of our classes and triggers (about 279 files this go around) and I want to make sure that the API update is the only diff when doing a deployment. Or to be worded differently: only deploy files where the only difference is the API version.

If you deploy permissions for, say Task.Type, Gearset deployment analyzer displays: "Exclude the following from the deployment - Field permissions for fields that are probably required fields on the target"

Field Task.Type (V39) is not a required field. If one ignores the suggested exclusion, permissions deploy just fine.

Elimination of spurious analyzer warnings increases utility of the remaining analyzer messages that are the raison d'etre of Gearset