Help us improve Gearset

We love getting feedback from our users on how we can make Gearset even better. Post your ideas for improvements, new features, and bug fixes alike, and vote for others – let us know what’s important to you.

If you need any further support, please contact us at team@gearset.com.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Additional feature - GITHUB Pull Request validation in CI Job

    Checkbox - Pull requests: Validate pull requests targeting the source branch is only visible when Run Job is set to --> Run tests based on Apex changes in the package

    Request you to enable option even when this is set to Run Job: 1 / 2 /4 / 24 Hours

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Require Jira Updates for certain types of deployments.

    While requiring updates on Jira tickets is nice we don't require this for ALL deployments such as if going to a production environment it's required however sandbox to github or sandbox to sandbox does not require an update.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Populate Pull Request Templates from git providers

    When creating a pull request directly in Gearset, it would be ideal to pull in the existing templates defined in BitBucket or GitHub.

    A middle of the road solution (if GiHub or BitBucket's API doesn't support this) could be defining a pull request template in Gearset.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. add an option to sign commits with GPG key

    If a source control space has enforced GPG key signature for all commits, gearset is not able to push any commits.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Create GitHub App as alternative to GitHub OAuth

    Gearset currently uses OAuth to connect to GitHub, and the way that works is that the OAuth connections have permissions to all repositories that my user has access to, which from a security perspective is a problem, because if the github key were ever compromised, it would provide very broad access to customers GitHub organizations.

    Security teams would feel much better with the ability to limit the scope of access to just one repo instead of all the repos that my GitHub user has access to, which can be accomplished by creating a Github App which can be installed for…

    4 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. provide the ability to add tags to branches within Azure DevOps.

    Within Azure Devops you can group commits and changes into a release based on a tag. So for a user to be able to add that tag when they are associating a workitem to a commit would mean they didn't have to go into Azure Devops later to add the tag.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Connection List Search Feature

    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.

    3 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. SFDX projects and source format and CLI useage

    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.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. add static code analysis results to pull request

    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?

    3 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. OAuth support for outgoing webhooks

    Currently outgoing webhooks support only basic authentication. It'd be useful to have oAuth support for outgoing webhooks for enhanced security.

    5 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Add the ability to restrict the Jira Projects Gearset can access

    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.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Ability to merge the pull request from inside gearset. It gives me option to stay in one tool and carry out all my opertions.

    In Gearset we have option to raise the pull request but we cant approve merge them inside gearset. There should be a checkbox which if checked should go and merge that pull request. That will allow the user to stay in one screen/one tool i.e. gearset. If someone wants to keep its approval processes in bitbucket then checkbox will allow them to only raise pull request and not auto merge/approve.

    4 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Show associated JIRA ticket in Validated Packages & Deployment History and Export

    We would like to view the associated JIRA in both the Validated Packages and Deployed History pages. In addition, we would like to export the associated JIRA tickets in the Export History Excel report, found in the Deployment History page.

    We link our Jira stories to our Production deployments and we would need a way to report on which ticket is linked to which deployment. Currently this is only available if users are diligent enough to also write the story number in the Friendly Name or Notes.

    This would be an extremely useful feature especially for companies undergoing SOX Compliance…

    3 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base