Help us improve Gearset

Welcome to the Gearset feedback forum. We love getting feedback from our users on how we can make Gearset even better.

Post your ideas and vote for others – let us know what’s important to you. We’re keen to hear about product improvements, new features, and bug fixes alike. We check this forum regularly and will keep ideas updated with their current status. If you need any further support, please contact us at team@gearset.com.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Ability for team members to manually run the CI

    Currently, only the owner of the CI job can manually run the CI. If the owner is out or unavailable, this creates a problem for team members because they have to deactivate the current job, clone and setup the new CI OR transfer ownership. Transferring ownership doesn't work if a team member is out unexpectedly, ill or doesn't have access to perform the transfer.

    It would be helpful if you could grant access to a group of team members who have access to manually run the CI. This would save a lot of time and prevent having to keep multiple…

    12 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  2. Enable tracking / comparison of code not in the force-app/main/default folder

    SFDX officially supports tracking of source within the same package in more than one folder. The "standard" folder may be used, but you are also able to create a folder hierarchy that's more akin to a "modularization"

    It can for example look like this:

    force-app (any names goes here)
    -> main
    --> default
    ----> aura / classes / pages
    -> module1
    --> aura/classes/pages
    -> module
    2
    --> aura/classes/pages

    Currently, only the metadata inside the force-app/main/default folder is seen. It would amazing if git integration could take other folders into account too. Both for Deployments from and to Git (for…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  3. Add Validate pull requests for custom git

    We have self-Manged Gitlab as a git provider.
    It would be good to have the possibility to allow to run validations on pull requests for custom git repositories or

    support on-prem GitLab (submitted as https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/39728857-add-validate-pull-requests-for-on-prem-gitlab)

    6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  4. Include the static code analysis report in the deployment notes so it can be integrated with Azure DevOps

    We would like to have a link in the Pull Request or Azure DevOps work item to the static code analysis report so the tech leads can review the report.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  5. Enable Dependency Cleaner only jobs on Git repos

    Similar to Unit Test jobs for connected Salesforce orgs, it would be great to have independent Dependency Cleaner jobs for our source repos to help identify problems separate from any particular commit.

    In our flow, not every commit goes through Gearset, so it's possible that our repo could become "undeployable" as a result of these non-Gearset commits. If this occurs, it then comes confusing on the next Gearset commit since the Dependency Cleaner will add all the deletions it deems required which don't relate at all to the PR being reviewed.

    A the end of the day, we'd like our…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  6. Allow outgoing webhook option to be configured for Compare and Deploy

    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.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  7. Filter branches by tag name

    In order to remove the clutter when selecting a branch to deploy to or from, allow users to apply metadata filters that dictate which branches show up in Gearset. For example, being able to specify that I only want to see feature branches.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  8. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  9. Integration with Rocket Chat

    Hello, I need rocket chat integration, in order to receive notifications in deployment group chat about deployment status.

    Thank you.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  10. Support integration with OKTA

    Salesforce orgs that have OKTA as a SSO Identify Provider cannot seem to be connected to Gearset using SF Authentication. Therefore is makes it impossible to do Monitoring and Tests.

    Please look into supporting OKTA SSO

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  11. Provide integration with WebexTeams

    We moved from Slack to WebexTeams and have lost the ability to post deployment notifications from Gearset. Here's an article about Webex Bots: https://developer.webex.com/docs/bots.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  12. Support multiple SFDX projects for a custom GIT repo

    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"
    }

    ]

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  13. Allow merging functionality when two branches are compared

    right now, when compare/deploying two branches, Gearset only fetches the new changes and creates a whole new separate commit to be pushed to the targeted branch. This causes the targeted branch to lose track of all previous commits from the source branch and when compared in git, it thinks that the targeted branch is still behind. It would be very useful, especially for admins, to be able to use merge compatibility if and only there is no conflict between the two branches.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  14. Add the option to note successfully deployed components in CI notifications

    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.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  15. Allow reauthorization of git/Bitbucket tokens used by CI jobs

    Currently, if the OAuth tokens used for a Bitbucket integration are refreshed, any existing CI job will not adopt the newly authorized token. In fact, there is no way to even edit the job to use the new credentials; the job must be completely deleted and created anew.

    However, in the case of Salesforce OAuth tokens, Gearset already has a Reauthorize button, along with facilities for re-associating the new credentials with saved orgs and saved CI jobs. Please enable similar reauthorization mecahnics and credential saving for other Oauth integrations, especially Bitbucket Server, so that CI jobs will not need to…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  16. Add support for incoming webhooks

    There's already a way to set up an outgoing webhook after a successful CI job run.

    It'd be nice to have a way for a CI job to have an incoming webhook from another service, such as ElectricFlow (a build platform).

    One use case would be for CI deployments to be dependent on external validation services.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  17. If we move Jira ticket to status "Deploy" -> get the code from the repo ->deploy to destination ORG

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

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  18. Link to test runs in Slack messages (or Slack messsage customisaton/templating)

    I have automated test jobs post about failed tests to our Slack. I want the posted Slack message to include a direct (though maybe shortened) link to the "Test run details" so that when we see Gearset telling us about some tests starting to fail I would be one click away from seeing a view of failed tests the message is talking about.

    Next/bigger step would be a way to shape the Slack messages ourselves. The most basic templating setup where I could write my own Slack message with some placeholders like {{instancename}} or {{failedtests_link}}..

    6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  19. Eliminate unnecessary XML reformatting in git

    Currently, when gearset deploys XML to git, it seems to run it through a reformatter, which creates superfluous changes in git. These changes cause extremely large deltas, which are hard to read, increase the difficulty of merges and the likelihood of conflicts, and make working with any other metadata tooling (like SFDX) difficult.

    For example, here is part of a delta gearset commited for a profile.xml:
    diff --git a/force-app/main/default/profiles/Commissions.profile-meta.xml b/force-app/main/default/profiles/Commissions.profile-meta.xml
    index 8b11e6b7..3d640a50 100644
    --- a/force-app/main/default/profiles/Commissions.profile-meta.xml
    +++ b/force-app/main/default/profiles/Commissions.profile-meta.xml
    @@ -1,10 +1,27 @@
    -<?xml version="1.0" encoding="UTF-8"?>
    -<Profile xmlns="http://soap.sforce.com/2006/04/metadata">
    +<?xml version="1.0" encoding="utf-8"?><Profile xmlns="http://soap.sforce.com/2006/04/metadata">
    + <custom>true</custom>
    + <profileActionOverrides>
    + <actionName>Tab</actionName>

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  20. Allow sfdx project files for scratch org creation

    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.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base