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

  2. Implement public key authentication for source control

    Implement public key authentication for source control.

    Allow Gearset to generate a public/private key pair, and expose the public key for use in authentication to source control.

    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

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

  4. Zapier Integration

    An integration with Zapier will allow more customizations options for how we can integrate with other tools, such as Manuscript (fka FogBugz).

    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

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

  6. integrate with Atlassian Stride for notifications

    Gearset's ability to send notifications to Slack is great. I'd like a similar ability to send notifications to Atlassian's Slack alternative - Stride.

    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

  7. 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. 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. Access to Jira custom fields

    we have a custom field we use that ties to a release number. It would be great if as an additional option to selecting tickets, access this field, set the value (in this case our release number) and have gearset pull all related requests in.

    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

  10. Skip CI Jobs to source control when there are no changes.

    After setting up a CI job from a Salesforce sandbox to a Bitbucket repo, it looks like the CI job always runs a commit, even if there are no actual changes. It would be great to not have this happen to avoid having many commits where there are no actual changes.

    14 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. Gearset API to externally trigger Gearset actions

    It would be incredibly helpful to trigger Gearset comparisons, validations, deployments, etc. from an external source using an API. Our team uses GitHub for our VCS, which provides the perfect opportunity to:
    1. design webhooks to validate changes in order to approve a Pull Request
    2. design webhooks to automatically deploy changes to an org once the PR is approved.

    Additionally, CI tools such as Jenkins, TravisCI, TeamCity, etc could use such an API to design complex builds that still employ Gearset, but use the external tool for additional actions outside of what Gearset provides for their CI features.

    105 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. Improve detection of custom fields on Managed Package objects coming from Git

    If I have a managed package object in Git, Gearset does not recognize it as managed package code in its comparison to a Salesforce org. This is a problem since it may not recognize a change if a custom field has been added to the managed package object.

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

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

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

  16. Allow for selecting which repositories to display for github in org settings.

    It would be helpful to be able to select repositories to display in the selection under Manage Orgs. Some of our repos in Github aren't related to Salesforce deployments, and filtering those out so they don't even show in the list would be really helpful in getting to selections faster.

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

  18. Allow comparisons of a single commit from a VCS

    Currently, you can select a VCS repo and branch to use for comparison. It'd be great if you could select a specific commit from that branch, so that you're only looking at an atomic set of changes. This would allow for fine-grained comparison and deployment of changes.

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

  20. Integrate with Jenkins

    Build a Jenkins Plugin to integrate with Gearset that would allow triggering CI jobs and/or deployments.

    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

  • Don't see your idea?

Feedback and Knowledge Base