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

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  2. 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"
    }
    ]

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  7. Store formatted JSON in source control

    The SFDC metadata API returns some items types as JSON compressed to a single line. For example, this applies to Wave dashboards (.wdash files).

    Gearset neatly expands this to a more readable when visualizing and comparing.

    However, in source control Gearset stores them in their original one-line compressed format. As a result, when doing merging and conflict resolution at the source control layer, these items are impossible to handle, as any change (whether technically conflicting or not) results in a conflict from git's point of view.

    It would therefore be great if Gearset kept the expanded format for JSON data…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  8. When source is local files, Refresh Comparison button should be smarter

    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.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  9. Support for zipping and unzipping static resources in GIT repos.

    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.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  10. AWS CodeCommit ability to view Repos

    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.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  11. Create a VSTS Build Task for Gearset

    VSTS offers the ability to create build definitions to validate/deploy your code, but Gearset customers don't have much options natively in VSTS to trigger a Gearset deployment. We can scan a code repository for changes every 4 hours in order to do a CI deployment-- but that's about it.

    VSTS offers the ability for vendors to create "Build Tasks" for their applications, where you can initiate a VSTS build and get results. This is basically a controlled version of API access to the tool.

    More information:
    VSTS Marketplace - https://marketplace.visualstudio.com/vsts
    VSTS "Add a Build Task" - https://www.visualstudio.com/en-us/docs/integrate/extensions/develop/add-build-task

    It would be…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  12. I need TeamCity to kick off a deployment within GearSet when all my auditing constraints are met.

    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?

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  13. Failure to login to scratch org - needs better error message

    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

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  14. Gearset configuration as a Code (git or exportable)

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

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  15. Populate Pull Request Templates from BitBucket

    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.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  16. Allow upload of Scratch Org Definition file from VCS

    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

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  17. Gearset to be added to a connect app

    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

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  18. Additional options for updating Azure DevOps work items

    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.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  19. Add ability to disable all comments on JIRA tickets

    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.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  20. add the ability to filter Git repos on connection

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

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  • Don't see your idea?

Feedback and Knowledge Base