In the new UI for Validation to view failed test classes error messages you must click into each failed class to view the details.
--
The previous UI showed "part" of the error message within the table. This was extremely useful in identifying all of the "unique" errors that are occurring.
--
IE: If 58 test classes fail from "4" unique issues -- then in order to determine that you may need to click into all 58 test classes or fix one at a time --> refresh --> validate.
--
This is just a time save feature.

It would be great to add the open PR feature (Github) to work with BitBucket after a successful commit.

Super helpful for the admin team to close off their feature branches and move onto the next job at hand without having to interact with BitBucket.

When I do a deployment it would be useful to download the success and error logs as a csv or excel document

All apostrophes are un-encoded within Gearset and show up as delta at merge.

At commit to branch, Gearset reorders large chunks of the XML file. This causes additional deltas (seen in the hundreds of lines) and merge conflicts.

Please add the ability to use the "Compare and Deploy" for Attachments and Files. The ability to migrate PDFs, image files, word docs, and excel spreadsheets would be GREATLY appreciated! Thanks!

If the search term ends in '__c', drop that when conducting the search.

Like how it used to be, when I could see all the Validation Failures on one screen. I'd just Snipping Tool them, head Back to Results and fix them, quick and easy. Now the Failures are scattered within the Successes with no way to filter or sort them.

Enable deployment of unmanaged packages and Lightning Bolt Solutions from one Salesforce Sandbox to Another.

Currently, a validated package is created by the owner of the draft deployment package, even if someone else was the one to actually press the 'Validate' button. I would like to have the username of the person who actually pressed validation to be noted somewhere in the validated package for auditing purposes.

This would help us be compliant with processes where we need a record of separation of responsibilites bewteen users.

Include the name/id in the deployment detail page within Salesforce in the Gearset deployment report so we can trace and match those details to a deployment run in Gearset.

When you clone a deployment package you have to select your Source details, but the selections do not default to the the last used settings or to a recently/commonly used settings. This is a minor annoyance but in other parts of GS you have the last selected options already selected based on user history, so hoping you can extend this to the Clone page

The current data deployment functionality works fine for one-off deployments, but if you are trying to keep specific data in sync across multiple orgs, the ability to schedule data deployments for a given time in the future would let you deploy on a recurring basis automatically. Becomes especially helpful when combined with the current data filtering options.

I'd like to be able to export a snapshot of all the metadata from my production org (include all components) to my git repository by clicking a single button.

After every release, it's worth taking whole metadata export from the org to git for the next/on-going releases.

For now, we have to create a couple of metadata projects to export the metadata to git, which is a tedious job and takes a lot of time.

"[TicketID,...] some comment"

When a deployment fails, deployment notes are sometimes wiped, and it is laborious to retype them - sometimes, I'll copy and paste to Notepad before deploying because I know I'm going to have to type them again. Notes should persist, or at least be configurable, from one comparison run through successful deployment.