It's great that we can set filter visibility now to Only Me or to share with Team. It would be nice, especially for larger teams, to have another way to organize them either with tags, folders, sub teams or groups.

Example: 1 Scrum Team may have 10-15 filters they maintain and use, and another group of users on a team also have 5 or so they use. Both can see all 20, and this adds up fast.

Feels like being able to group users together could also have other benefits like mass assigning access to orgs (for deployment, validation, comparison) vs doing it per each user individually

When compare source and target, sometimes u do an educated decision to NOT select something, and then selecting the rest of the items. Then if the compare results saved as a Draft Deployment, u may return back to it, and do a refresh for the comparison. In this case Gearset would kindly save all of the selected items. But for items that were not selected by the user, not they are mixed up with the new differences. So user have to remember, that this particular item he did not select intentinally, but this item that is not selected is a new difference.

It would be nice to have an additional capability to mark "not selected" items to "not deploy". So if I refresh the comparison, i would be able to identify "not deploy" items from new difference.

In the past we had troubles deploying reports via CI, they were not showing/deploying, the workaround was to enable the filter to include all reports. This works to solve that, but now I am looking at including more into the repo and start using delete actions in the CI jobs as well. The downside is that because we have to have all reports in the filter, the CI job will delete reports created by users in non-private folders. A freedom we want to give certain users in Production.

What would be an epic enhancement (and solve this challenge) is if you could decide to do delete actions per metadata type. Then I'd configure delete actions for everything except Reports and List Views for example.

On the “My Connections” page, I'd love to see an option to add a folder (and sub-folders).

Currently, there are options for "Developer orgs", "Sandbox orgs", "Production orgs", and "Scratch orgs".

If you are running more than one entity, having the sandboxes related to a single entity inside of a folder would be more user-friendly than having multiple dev/sandbox orgs inside the same folder.

For example, if I'm managing deployments for "ABC Company", "XYZ Company", and "LMNOP Company", and each has multiple sandboxes, it would be really convenient to be able to separate out their various sandboxes more effectively, into their own company folders, rather than all grouped inside of the same "Sandbox orgs" folder.

Custom user folders:

-  External Clients

    -  ABC Company

        -  Sandboxes

        -  Production org

    -  XYZ Company

        -  Sandboxes

        -  Training org

        -  Production org

Hello Gearset,
We are exploring using the "Monitoring" functionality to audit our Salesforce production metadata changes for our IT Controls. It looked promising until we found out that anyone on the team can edit any monitor job setting, which creates a loophole in the controls that we can't monitor the monitor.
So I'm curious to learn from Gearset whether any of the following can be done/requested:
* Can we limit the Monitor jobs to only be editable by the person who created it?
* Can we show either an audit history or LastModifedBy/LastModifiedTime of the Monitor job?
* If the Monitor job audit log cannot be surfaced to the UI, can we reach out to Gearset to request the history of a particular Monitor job?
Thank you!