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

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.

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.

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.

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.

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.

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.

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.

On the deployment history page, the column widths are fixed. If you have a value in the "friendly name" column that's over a certain character count, it gets truncated automatically. there is a tool tip to see the full value by hovering, but if you use consistent naming standards for naming deployment packages, this can result in having to hover over many package (i.e. rows) to find the one you want.

if making the column width customizable isn't possible, then making the "friendly name" column character limit longer would be a good start!

When you delete a managed package from VCS by deleting its <InstalledPackage>, Gearset should look for all traces of that managed package in VCS and delete those files/update the metadata

The <InstalledPackage> file identifies the namespace - eg. SomePkg, and Gearset should be able to remove files that start SomePkg__ as well as delete/edit metadatablocks within other files that reference SomePkg__c.

It is extremely tedious to remove managed package metadata from VCS otherwise; especially if the customer opted to put a lot of managed package metadata in VCS (perhaps by accident)

Lets say multiple vendors are working on different environments and done the deployment across all the lower environments using their own Gearset. But coming to the production org. internal team will be performing the deployments using internal Gearset. So Instead of recreating the deployment draft again, it would be very useful internal team can reuse the draft created by vendor in different Gearset environment.