When selecting a branch from source control, it would be great if Gearset had an ability to mark certain branches as favorites so they appear the top of branch selection dropdown.

When creating a pull request directly in Gearset, it would be ideal to pull in the existing templates defined in BitBucket. A middle of the road solution (if BitBucket's API doesn't support this) could be defining a pull request template in Gearset.

On the "Create a new scratch org" page -- since SFDC recommends that Scratch Org definition files go in VCS (see https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_scratch_orgs_def_file.htm)

then the Upload dialog should offer an option to browse repo/branch/folder for the desired Scratch Org Definition file (default path would be main/config)

and, once selected, the other portions of the page that are overridden by the Scratch Org definition file should be both populated and disabled so the user gets a confirmatory echoing of choosing the right scratch org definition file

The ability to use Salesforce as an Identity Provider and have gearset be added as a connected app so the user would be forced to sign in with SSO and select when they sign in from salesforce

For example, we do not want to see messages posted for validation started, validation completed, deployment started, deployment completed. We only want to see messages posted on successful deployment. And one more thing is to update the State once the deployment completes successfully.

Currently, when adding a ticket number in JIRA connector on a deployment, there is no possibility to disable comments sending on JIRA.

This can be a problem, as JIRA tickets can also be seen by our final users, and this "XXX has deployed the ticket" kind of comments can question them.

Gearset CI only supports SFDX source that follows the SFDX project template structure (e.g. force-app/main/default/classes and so on). However, SFX CLI doesn't mandate that structure.
SFDX allows you to group metadata by function or logical group (so you can combine metadata in any way that makes sense to you) . We have many projects like this that gearset cannot deploy.

It would be useful to be able to select only applicable Git repos from source control that will interact with Gearset. A user may have many repos that they need on their account, but of those there may only be 1 which would be used via GearSet. It would be great if we could select which repos should be available when setting up the connection to our source control (specifically I am requesting GitHub but I think this would be useful for all source control integrations).

A Jira account may be linked to many projects which will never be interacted with through Gearset. However those projects might still be legitimate for the user, so they can change their project access on the Jira side. It would be great if we could select projects in the connection that we want to choose from when associating to a Jira item.

Add a Search feature to Connections Page. I have 59 connections at the moment and the only differentiation between them is a suffix at the end of the login. It would be nice to be able to quickly search the list of Connections like a CTRL + F would do.

I often have to scroll the list and compare login usernames.

If I clone a deployment, it copies all the associated Jira tickets, but if I merge two deployments, the list of associated Jira tickets is empty. Is that how it is supposed to work? I would expect a union of the lists of all the merged deployments.

The same would apply to comparison refreshes.

Would really benefit from being able to paste a list of Jira Ids, e.g. comma-delimited (similar to specified tests) on final deployment. Hate giving up validation / deployment status writebacks to Jira, but often we have packages spanning dozens of Jira tickets and entry can be time-consuming, especially if there is a failure or refresh needed and Jira ticket associations get lost from the draft.

Remember the last used repository and branch in all places.

Can you add the ability to add the static code analysis results to a pull request? Or link back to the deployment summary screen with the results displayed there?

Need a Integration of Gearset & Jira , once the user story is updated in Jira , My gearset job will get triggered and deploy the components related to that user story.
and once the deployment is done , update the jira ticket status as deployment done.

As our local hosted Jira instance doesn't allow unnamed connections it would be great to have a basic (username + password) authentication for Jira as well as Bitbucket.

Allows the Git repository to be rebased from the latest and greatest metadata from a target organization. In just few clicks the gearset will download all the latest metadata from a target org and will check in it inside master branch

It would be great to have some ability to customize the notifications, specifically:
- change sender/title. right now it just shows up as my name.
- add a link to the monitoring history to allow wasy one-click into monitoring reports to see what specifically has changed.