Idea is to have the Delta CI for Validation only Job, so the as well, so the validation process will become faster .

The option of validating a PR in the deployment job does the same task, but is comparing too many items of metadata and it is taking too long.

It would be nice if we have the select all option in the deployment history to select multiple packages to combine in one go and deploy as one package into target.

We have clients in Canada that require data residency for data backups/deployments and even metadata deployments/processing.

Please add the option for a Canadian hosted Gearset account.

Gearset does not support PR validation for AWS code commit. We are cloud-native and use AWS extensively, thus missing out on most important feature of gearset. If you can support it it will be amazing and lifesaver for us.

https://gearset.com/blog/set-up-automatic-validations-of-pull-requests/

Sometimes, you carefully craft a comparison between source org and VCS only to discover that you have targeted the wrong branch!

It would be nice to go to the Comparison History tab, select your completed comparison and click Clone so you can change the source/target but preserve your selected metadata filters and selections

Current Environment Variable feature uses search/replace logic across the entire metadata file. This is a bit "scary". Add optional 3rd argument for the specific XML tab within the file that you want to limit the scope of the search/replace to

I'd like to be able to exclude certain custom fields from my comparison.

For example we have fields that have environmental differences between orgs that we don't want to deploy. There are also random fields on standard objects that show up as "different" even though they aren't and it would be nice to filter them out.

Ost to pst recovery software to recover all the ost file data in to pst file. stella ost to pst converter software support all the version 32bit and 64bit ost file data in to pst file. stella ost to pst recovery software recover damage ost file data in to office 365 account. Stella ost to pst recovery software recover all unmounted ost file data in to pst file. for more info visit this link https://www.stelladatarecovery.com/ost-to-pst-recovery.html

I would like to see a change to the metadata filtering in general.
Filter management has become a important part of our devops process as we seek to lower our comparison timing.
Instead of having it at the bottom corner of the compare screen, move that section to the middle of the compare screen.
In addition, add a side bar specifically for filters that allows you to edit or delete them as well as change the sharing between personal and team. I have example screenshots for suggested layout changes here: https://faef.box.com/s/frse8jnvqsxbl8ue05x641j3wlga1quy

When setting up the filters, I would like the ability to do a Select All on just the filtered items so that I don't have to manually select each one of them. This would be a huge time saver.

At this time, there does not appear to filter deployment history by specific orgs AND other criteria in the general "filter" text box. I would like to find specific packages deployed to a specific org and also that have a standard friendly name. I am only able to enter text to filter by the friendly name and the additional filters allow for source / destination type, but it does not allow for specific source / destination.

I want to be able to share 'delegate org access' with other team member(s) so they can visually see our security / deployment structure for reporting.

In this example the fact that "user A owns the connections and has delegated the permission to user B" is not visible to user C. Ideally user C would be able to see that delegation information for auditing purposes.

APEX Class Changes Reporting

It would be really cool if, through the monitoring side, if a summary Excel could be created. Excel could have multiple tabs: 1 tab per class change with four columns:

col1 :original line #
col2: original line value
col3: new line #
col4: new line value

Header could include change DateTime, source/target orgs, Gearset ID, who, etc

Thanks
Ron

It would be immensely helpful for our team, that works across dozens of production orgs and sandboxes, to be able to create deployment history filters (or list views like in Salesforce) that support filtering based on an org's mydomain, the username's domain, or the Gearset user that facilitated the deployment.

We'd like the ability to view the number of changes that were deployed from the Deployment History table view so that we can quickly scan the list of recent deployments and identify certain deployments using that additional information.

We do receive an email notification when CI job is deployed. Is it possible to know which PR is deployed with that CI Job? Now, the email notification only has the info with branch name, source, target and deployment summary. it'll be great if we can know the PR name that is associated with this CI job, some users, like QA team, will receive emails and know the PR with card info is deployed so they are ready to test. thanks

I have a markup screenshot for the above feedback but I don't find a way to add attachment here.