Skip to content

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

158 results found

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Add Salesforce Data Cloud sandboxes as an option for deployments

    Salesforce Data Cloud sandboxes are now generally available but to promote changes from sandbox to production, the only options are through Data Kit and change sets, CLI, or DevOps Center. Having the option to use GearSet would be helpful so all deployments were managed the same.

    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)
  3. enable using a Repository Access Token instead of a Service Account

    I would like to be able to use a repository access token instead of a service account to connect to VC (Bitbucket in my case). https://support.atlassian.com/bitbucket-cloud/docs/repository-access-tokens/

    The main benefit for me would be the ability to conveniently authenticate while maintaining a high level of security, even in situations where corporate change management policies and SSO requirements can be cumbersome.

    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)
  4. Allow configurable default settings for Jira integration

    Allow us to customize the default behavior for the Gearset<>Jira integration. Currently, Gearset posts a comment on the linked Jira ticket every time a commit is started and completed. This creates a lot of noise on the ticket.

    Currently the only way to customize the messages posted to Jira are on a ticket-by-ticket basis. Allowing an option to customize this at the org/pipeline level (e.g. only post a comment when a deployment succeeds) would be very helpful.

    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)
  5. Improve audit API to extract list of users and their entitlements. Additionally, allowing us to provision & deprovision user access via API

    We use 3rd party tools to audit all of our user access at our company. Automating this via API instead of exporting CSV and loading that into another tool would be very beneficial. Additionally, we use that tool for provisioning and deprovisioning so if an API for that existed too, we could automate Gearset users.

    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)
  6. Trigger Gitlab Pipeline Faster

    When opening a MR in Gitlab, the Gearset pipeline queues the Validation very quickly. However, in Gitlab, there is no pending Pipeline until Salesforce starts the validation. Sometimes this can be a lengthy period of time with no visibility inside of Gitlab.

    Would be nice to trigger that immediately so approvers can see that it is queued, not just no pipeline job has been executed yet.

    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)
  7. Integrate with Linear

    Linear is quickly becoming the new Jira for today's technology and engineering teams. It should be considered an important integration.

    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)
  8. Allow CI jobs to use the running users GitHub connection

    At the moment CI jobs within the Pipeline use the CI owner's GitHub account for new branches and pull requests etc which is stopping the code reviewers process within GitHub from working currently.

    Can we allow the integration within Pipelines to run on the promoting user's connection (i.e. so requests are shown with the running user and not CI Owner within GitHub) or allow a generic user to be set up instead to untie deployments from the CI owner GitHub connection within Gearset.

    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)
  9. Let the user post Jira comments as internal or customer-facing from deploys

    When deploying from sandbox to sandbox, we'd like the comments to post on the tagged jira issues, but would like to keep those comments internal instead of updating our clients. It would be good to have a security selection option when posting comments from gearset to jira.

    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)
  10. Notify GitHub that checks are running sooner

    When a PR in GitHub is being validated, Gearset doesn't let GitHub know that the check is happening until after it has run the comparison between GitHub and the target org. Then the check is pending while the validation runs in Salesforce.

    This means that there is a delay between when you create a PR and Gearset's check appearing as pending in the PR. At that moment, it looks like there are no more checks to run in GitHub so you can go ahead and merge. But, you really should wait until Gearset has compared and validated the changes.

    It…

    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. Delete GitHub webhook when the CI job is deleted

    When we create a CI job where the source is GitHub, Gearset can automatically create a webhook for us in GitHub.

    Would it be possible to delete that webhook in GitHub when we delete the CI job from Gearset? I've got some GitHub repos with failing webhooks due to CI jobs I once created. Obviously, I can tidy up manually from GitHub, but it would be nice to have the option of Gearset doing it for me. The URL seems to be unique to the CI job, so I can't see it having any negative consequences.

    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)
  12. Enforce each deployment to have a Jira issue in a specific status in order to be able to deploy.

    As a gate-keep; to be able to deploy anything to production (or any other named environment), the associated Jira ticket must be in a pre-select status.

    For example, the Jira ticket's status must be in "Ready for Deployment" to allow an end-user to deploy.

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

    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)
  14. Ability to mark certain branches as your favorite branch so you can pick them quickly

    When selecting a branch from source control, it would be great if Gearset had an ability to mark certain branches as favorites so they appear the top of branch selection dropdown.

    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.

    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)
  16. 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)
  17. Select source control based on actual setup/connections when starting comparison

    When starting a comparison and selecting source/target environments for Source Control - it shows all connection types including those that I haven't connected.

    With browser cache, it seems to remember the one you selected last. However, for new users (or when you clear cache) it'd be ideal if Gearset would default your source control on this screen to whatever the user has connected. Once a user has connected a source, there's no sense in having the user choose it again at this step.

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

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

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