I need the option to configure an outgoing webhook when deploying via 'Compare and Deploy' feature. Currently webhooks are only available with the CI jobs.

When comparing / deploying using a custom git repository, containing multiple SFDX projects, present the user with the ability to select which SFDX project to compare / deploy, either by package.xml or sfdx-project.json. Currently Gearset fails and reports multiple sfdx-project.json were found.

[
{
"UserReadableError": "This repository has 2 sfdx-project.json files: Gearset cannot determine which one to use",
"ErrorType": "ErrorFromSource"
}
]

When a CI job is configured to post to slack, and a job fails, it is very useful to see the message posted with information about what failed (error message, number of components that failed).

However, when a CI job succeeds, it only shows the counts of changed/new/deleted objects.

It would be very useful to have the option to list out what was deployed - this would make it easier for devs/qa users who monitor these slack notifications to understand which deployments are relevant to them at a glance.

For example after Jira status "Deploy" is captured doing a comparison and deploying the changes will work.

When creating a scratch org, allow us to select/configure a sfdx-project.json. This will allow for more complicated sfdx project to be deployed, i.e. multiple project folders, namespaces, ... etc.

If your source is Local files, and you do a Compare to some target, and then realize the source needs to be amended before re-comparing, your "training" is to clock "Refresh Comparison" button.

This executes but does not ask you to upload new source files so essentially nothing happens.

User should be given option to upload new folder/zip.

Add support to automatically unzip zipped static resources when migrating to a GIT repo and re-zipping when migrating to SF. This would allow me to edit my static resource files without having to manually unzip them.

Today the ability is not there to allow for viewing multiple repositories within AWS Code Commit. One can view a singular repo and the branches that it contains.

In our instance we have different repos for our various instances. We would like to be able to have the ability to go on level deeper and be able to first choose the repo, then choose the branch.

Hit me up with any questions please.

We currently have a deployment pipeline for our .net and Rails environments that utilize VersionOne, GitHub, TeamCity and Ansible to deploy changes into AWS.
Due to auditing constraints we would like to use VesrionOne, GitHub and TeamCity to deploy our SF changes.
Does Gearset interact with these tools or must it stand on it's own?

If you created a scratch org from the Gearset Orgs page and subsequently, that user is deactivated in the scratch org then ...

a) A Compare fails when scratch is either source or target with an ugly error suggesting you reauthorize the org - but you can't reauthorize scratch orgs from within Gearset

b) A login to that Scratch Org from the Orgs page fails with an HTTP 500 error and makes you think the Gearset server is down/broken

Basically, when login target is scratch org and login fails, suggest a more context-aware diagnosis & remedy

Gearset configuration as a Code (git or exportable) so that there is a way to store it i.e. in Git and see how various jobs, cicd pipelines, monitoring and schedulers are configured which is an enterprise way to implement solutions nowadays (PaaS, IaaS etc..)

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.

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).