Right now, the only way to edit a group's membership is via the API (users or groups only) or the UI (additionally allows roles, roles and internal subordinates, etc.). Please allow the editing of group membership of public groups.

Currently, if I want to suppress errors from static analysis, the suppression seems to be all-or-none at the class level.

I would prefer to suppress only the specific errors when they happen.
(e.g. in the method or in the line.)

Currently the moment you deselect a single specific date, all blank dates are also filtered out.

I would expect only the items with the given date be removed from the list.

This has become apparent now that the sort order of dates in the pulldown bug has been fixed.

It would be useful to select all objects in the data deploy screen to make it faster to select a large number of objects (even better would be the ability to group objects and select whole groups at once)

We use PMD locally in our IDEs to analyse during development, and the whole team shares a rule file in xml. It excludes the ones we don't like and configures other rules.

We can configure Gearset to do the same through the UI, but I'd rather be able to just upload the file, then I will know they are the same set of rules.

When doing a bulk clone, each metadata should show what previous deployment it was a part of as to allow us to verify that the bulk clone worked. Another use case is that it would allow us to find a deployment we know has changed and be able to remove or change the metadata quickly.

We just came across an issue in which we were deploying an HTML email template that had been moved from one folder to another in the source environment.

When deploying, only the delete happened on the first deploy. I needed to do a second deploy to handle the addition.

While probably not a common case, it's certainly important as the initial deployment reports that the addition was successful.

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

We use Clone from Deployment History quite often. A typical use case would be:

Deploy from feat org F to branch
Do PR & merge to /master
.. CI runs
Upon successful CI
Clone deployment with source = master and target = QA org
Upon successful UAT
Clone deployment with source = master and target = PROD org

Rather than having to re-enter on the Clone dialog the source and targets, since they are always the same, it would be nice to "favorite" sources and targets (assigning a favorite name) and then reusing those favorite names on the Clone dialog

A nice-to-have UX feature would be to echo the metadata API version used in the CI Job on the Validation Errors report (or any CI report). This can be used to aid in troubleshooting

The ability to use this product for CI/CD and various other use cases in the US federal space would be a huge win for many agencies. I know the FedRAMP process is quite arduous, but the contractual potential here is pretty massive.

When you open a Draft Deployment it would be great to see its name on the deployment page as well as its refresh date. I understand that when you open a draft deployment you're seeing a snapshot from when it was created or refreshed.

Gearset's ability to send notifications to Slack is great. I'd like a similar ability to send notifications to Atlassian's Slack alternative - Stride.

Macros deserve to be added to source control yet there is no way to do this with Gearset:

1) Data feature (paid add-on) doesn't deploy to/from source
2) PRO/Enterprise can't source/target deploy Macros because it is not available with the Metadata API.

Since macros represent some debugged logic, managing in source control makes sense. Curiously, SFDC has chosen to make Documents available via Metadata API but not Macros

An integration with Zapier will allow more customizations options for how we can integrate with other tools, such as Manuscript (fka FogBugz).

we have a custom field we use that ties to a release number. It would be great if as an additional option to selecting tickets, access this field, set the value (in this case our release number) and have gearset pull all related requests in.