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

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

    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

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

    Note that it lowercased…

    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

  4. Extend Jira Cloud Integration to Releases and Bitbucket

    We do the majority of our management via Jira and have it linked to Bitbucket and our test system so that we can manage everything via Jira. It would be great to extend the current integrations to more intelligently link the package to Jira tickets and the corresponding Bitbucket code and then push back to Jira the deployments in a more Jira friendly manner e.g. potentially creating/updating a Jira release for the deployment.

    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

  5. FogBugz integration for Gearset

    We'd LOVE a FogBugz integration for Gearset similar to the new Jira Integration.

    https://docs.gearset.com/feature-walkthroughs/integrating-with-jira

    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

  6. Allow teams to share custom git repositories

    It would be nice to be able to share custom git repositories with the entire team. At this time, each team member that does deployments needs to configure each custom git repo in Gearset. Besides requiring them to set it up, it also means I need to give each person the credentials.

    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

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

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

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

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

    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

  11. Show the latest commit(s) in the slack notification

    It would be extremely useful for the development team to see the last set of commits which were deployed via an automated job, so that if it breaks it is easier to tell what broke the build or if it is successful what the org has been updated with.

    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

  12. Integrate Gearset with Bamboo

    Would be important to be able to integrate Gearset with an existing CI Tool like Bamboo, Jankins. (e.g an Bamboo Action or a generic Rest API which can be used by Bamboo or other 3rd party apps)

    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

  13. Jira: ability to associate tickets during comparison

    Would like the ability to associate Jira tickets during the comparison process so that it can be saved to draft deployments and can continue to add as needed. Currently it appears you can only add Jira tickets after you have finalized all items for deployment.

    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

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

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

  16. Show associated JIRA ticket in Validated Packages & Deployment History/Export Deployment History

    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.

    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

  17. Require Jira Ticket Before Validation or Deployment

    We would like the ability to make the "Jira updates" section required (i.e. ticket selected) prior to validation or deployment.

    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

  18. Show In-Progress Validation jobs when clicking 'Details' in GitHub PR

    When viewing a GitHub PR and you have a status check that's in progress, clicking 'Details' should take you to the validation only job page and show all validations (including those in progress).

    Currently this page only shows you completed validations which makes it confusing to use at first and you have to navigate to 'Continuous Integration' and find the validation job there.

    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

  19. Ability to create Pull Requests for AWS CodeCommit

    Gearset can create Pull Requests for many of the source control systems that it integrates with, but not AWS CodeCommit.

    As AWS users, it would be very useful to use to have this ability so that we didn't need to switch systems to create Pull Requests.

    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

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

    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