Creating a visualization of the DevOps process removes the need for separate Visio diagrams or visual aids to represent the process. Also by creating this feature, you could allow for a drag and drop type feeling to represent CI Jobs, Data Deployments, Comparisons, etc. Users who may be new to a DevOps environment would pick up the process quicker allowing them to quickly adapt to the tools and this type of deployment mentality.

When user clicks on test run details, Gearset defaults to the successes tab. But no one clicks on test Run details to see successes; they want to see failures. Default tab should be failures, especially if non-zero

Saves user a click and supports DWIM - "do what I mean" when clicking Test Run Details

I have so many connections and jobs, is it possible to have group them (in future release?)

It would be nice if you broke up the settings into smaller subcomponents. For example the Security settings would be more useful if you extract out the password policy changes so we can pick and choose what Security settings we need. I thought of this concept similar to how you break up profiles into sub component. This could get noisey in the list of changes so an alternative to that could be to bundle it under components like how CustomObjects work.

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 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 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.

When combining packages for a deployment to a new source, it would be helpful if I could add additional packages to a comparison. There are times when I realize a package or two may have been missed in the original combination, and when reviewing the missing components, I realize a missed another deployed package. Without the ability to add additional packages to the comparison, I must start the combination of packages all over again.

Ability to Export Validated Packages from Grid, like Deployment History.

This feature would allow Enterprise user with Role"Owner" to Delete Validated Deployment by Other Users. The reason for doing this is that there could be packages created in error and this would allow release managers who are typically owners to cleanup.

Once you create a regex filter in your your Metadata Filter, you can't select it and edit it. You have to delete and re-enter.

This is especially useful when working with CI job filters

When you stop licensing a feature, there could be all sorts of cruft in the VCS that is otherwise challenging to remove using normal Gearset tools.

Example: We stopped licensing LiveAgent but our VCS is full of references to LiveChatTranscript and other CustomObjects used by this feature. This is particularly apparent with sub-elements of Profile

It would be cool if Gearset repo cleaner could detect when standard objects no longer available in the source org of the compare would be considered as deleted and all refs to those standard objects would be repo-cleaned.