API to provision users, assign users to connected organisations

It would be hugely benificial to us (60+ connected organisations, 25 employees working in teams for multiple clients at a time) if we could programatically provision/deprovision users and provide access to connected organisations via an api.

At the moment this is error prone manual work that has to be done by someone with high level access (and as such is usually already short on time).

I really love using Gearset. It would be great if we have a plugin in there to integrate Gearset and SonarQube to display Static Code Analysis and Test Coverage in Sonar. I had tried this through CircleCI and it requires lot of configuration and we need write code to create and maintain the connection.
Whenever there is an update to the GIT Master it has to Initialize the Sonar Scanner and it'll run some tests and display results in SonarQube.
Thanks!

I would like to see a change to the metadata filtering in general.
Filter management has become a important part of our devops process as we seek to lower our comparison timing.
Instead of having it at the bottom corner of the compare screen, move that section to the middle of the compare screen.
In addition, add a side bar specifically for filters that allows you to edit or delete them as well as change the sharing between personal and team. I have example screenshots for suggested layout changes here: https://faef.box.com/s/frse8jnvqsxbl8ue05x641j3wlga1quy

After a deployment to a git branch, gearset allows to create the pull request from Gearset. It would be nice to:
1. Have an option to add the pull request URL to the deployment notes
2. Have the capability of add reviewers (users from the git repo) into the Pull Request

It would be helpful if in the "Changed On" dropdwn filter if it grouped it into days, rather than the exact time the change was made. Also, if there were preset groupings like "Today","Yesterday","Last 7 Days", etc.

When looking at a comparison it shows changed by as a column, would be helpful for consultants to Show Created By and Created Date as well

When deploying code, it would be nice to have an option of having an exclusion list of test classes to not run.

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.

For example, deployments to a production environment should only come from the master branch of our git repository

It would be useful to be able to import data with Gearset from a .csv, so that I wouldn't have to use tools like Data Loader (newest versions are extremely buggy on macOS), Workbench or pay for a separate tool like dataloader.io.

We have clients in Canada that require data residency for data backups/deployments and even metadata deployments/processing.

Please add the option for a Canadian hosted Gearset account.

Currently successful deployment notifications send every success to the specified addresses. Having the ability to specify the source would eliminate the unnecessary notifications to those addresses. We have a use case in which we only wish to send notifications for successful deployments to our production source.

There is no support for Wave Recipes currently and we are not able to deploy dashboards via Gearset and Continuous Integration.

The idea is to validate feature branches in repo. For doing this it's necessary to allow specifying source branch by pattern (like feature/*) in "Add CI validation job" menu. The validation should check whether the code breaks the scratch org creation or not. This is valuable due to fragility of scratch org creation process (sfdx force:source:push).

Rather than splitting jobs into Validate and Deploy and ordering alphabetically, allow custom ordering (drag and drop, or custom grouping) in order to maintain logical job sequences including a mix of deploy and validate jobs.

The comparison screen is great to help admins and declarative users see the changes they made. However, it still requires them to know which metadata to pull based on changes they made.

Source tracking in Sandboxes is in beta and would alleviate this concern.

https://help.salesforce.com/articleView?id=sfdx_setup_enable_source_tracking_sandboxes.htm&type=5

If Gearset could leverage this functionality (potentially leveraging SourceMember object or storing .jsons to track last modified times as local projects store) it would make the complete process easy to use for all alike (pull metadata, select diff, deploy).

Hi Team,

Please add checkbox for validated package as same as deployed ones. that way I can combine package even for validated one's and deploy.

an additional layer of security and convenience would be to enable Gearset login (that is, login to Gearset) to be done from an enterprise's SSO solution. We use Duo but Okta and others should be supported.

Just like we can login to Salesforce from our enterprise's SSO , we should be able to login to related apps in our suite of enterprise tools via SSO