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

137 results found

  1. Add "View Validation in Salesforce" to your Github and Teams/Slack Channel messages.

    Our pipeline is utilized by some implementation partners that we do not give access to Gearset. They manage their changes that flow through the pipeline with GitHub and receive pipeline updates in a Teams channel. Both of these options have a message to view validation errors in Gearset but the partner teams cannot see Gearset. If these messages included the same "View Validation in Salesforce" option that lives in Gearset, they could be redirected to the Salesforce error page to help their troubleshooting faster.

    10 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. 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)
  3. Delete feature branches in Github in a way that they can be restored

    I closed a PR to master, and Gearset deleted the feature branch. However, it wasn't merged, so I wanted to restore it to continue work. I was completely gone from Github. I believe Gearset should do a normal delete that allows restoration instead of completely obliterating feature branches or allow an option to do so.

    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)
  4. Expand integration for our Pipelines to allow us to enable tools like SonarQube and Veracode to run as part of our DevOps process.

    We use tools like SonarQube and Veracode within our company to improve our security and code quality. It would be extremely helpful to have integrations with these tools or an open integration we could configure to work with them. Especially if that could be triggered as part of our pipeline process so this interaction is automated.

    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. Improve Github Authentication and Access Control

    While authenticating with Github, GearSet asks for too many access request including read/write access to all public & private repos which doesn't make sense.

    Alternate Custom Git Auth does not allow teams to create team wide CI jobs.
    And with User - specific CI Jobs, It does not allow us to setup "Validate open PR" jobs.

    Please provide better resolutions on authentication and job setup processes.

    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)
  6. Enable us to customize the Slack notifications from Gearset

    Enable us to customize the Slack notifications from Gearset (e.g. add deployment Friendly name to Slack deployment notifications). Thanks

    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. CI job merger conflicts

    When resolving CI job merge conflicts, a user has two windows to accept changes from one side of the window. Can we have an option to accept specific components changes from one side and certain changes from the other side.

    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)
  8. Microsoft Teams CI Deployment Job Notifications - Add Source Commit

    There should be parity with the content included with a Teams web hook notification. With Slack, the Source Commit attribute is included.

    With Teams, it's omitted. Please add so this data point is available with Teams. Current output illustration.

    Slack


    Gearset Continuous Integration
    A continuous integration run succeeded for SIT Deployment / Validation job for PR #97. The job was a validation. No changes were detected for deployment.
    Source commit
    5ccc5b72

    Teams


    A continuous integration run succeeded for SIT Deployment / Validation job for PR #97. The job was a validation. No changes were detected for deployment.

    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 automatic tagging of release commits

    I've found it very useful to be able to quickly identify release merge commits from our VCS. Being able to search for a tag in our VCS would allow us to easily compare one version to another without having to use something like git bisect. I'd like the option to automatically tag a commit (you could probably use the release name) would be helpful.

    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. Enforce Promotion Approval Rules

    The current UI shows a green checkbox and allows you to attempt to promote changes between environments even if the merge request is unable to be approved. Looks like it in Gitlab there is an 'approved' attribute that may be able to be used.

    Alternatively, can have some basic rules but would like it called out its not ready to Promote in the Gearset UI.

    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)
  11. Pipeline PR User interface Details

    Currently we can see Jira ticket status when we look at PRs in the pipeline UI it would be phenomenal if we could include additional Jira fields to be seen from Pipeline UI such as Summary or fixversion

    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)
  12. Improve Deployment Information in Notifications

    I've tried both Email and Teams integrations and the actual information in the message (or attached PDF for Email) is lacking, with only great piece being the branch name.

    An option to get advanced details that could provide some of the below (but not limited to):
    - Actual Links - Atleast with Gitlab Self-Managed, we just get a text-based message referencing a merge request.
    - Commits / Original MR - For those deployed via a Pipeline, getting the original MR (our pipeline is dev org > QA > UAT > Staging > Production, with the Dev Org > QA being…

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

    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. Show all Github requirements to merge in the Gearset pull request view.

    We have required approvals enabled on PRs in Github. Currently when viewing a Pull Request in the Gearset Pipelines view, it does not show that a PR is blocked from being merged because at least one code review approval is needed in Github. This leads to accidentally attempting to "promote" in Gearset and then the Pull Request merge fails. We would like to see these (and any other Github requirements) showing up in Gearset so we are informed which PRs are approved and ready to promote.

    10 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. Integrate with Agile Accelerator instead of just Jira

    Integrate with Agile Accelerator instead of just Jira.
    It would be great if Gearset (and ideally the Pipelines-feature) could integrate with Agile Accelerator.

    Since we're a Salesforce-partner we want to use as many Salesforce-native solutions. That's why we've been happily using Agile Accelerator for many years.

    It would be great if Gearset can also integrate with Agile Accelerator instead of just Jira.
    Right now the Gearset Pipelines feature isn't useful to us, because of this sole reason.

    Thanks for considering this!

    27 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. Support Gitlab Application Tokens for CI Jobs

    Gearset uses User-level Application Tokens which is great for all user-initiated requests. However, things like automated commits, new branches, etc would be ideal if we could tie to Gearset. Gitlab supports granting out tokens at the Group or Repo-level where we could provide a better and more auditable tracking of Gearset automations

    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)
  17. Automated Commit Message Identifiers

    It would be great if automated commits/PRs/etc had a note that called out they were automated for audit purposes.

    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. Allow different source control users per CI job

    At the moment, my GitHub user is defined at an account level. So that user is the one for all CI jobs.

    I may want to have a different GitHub user for each of the projects that I run through Gearset. For example, if we are a consultancy that generally use our own stack, but have to use a GitHub user belonging to a customer on some occasions.

    Or (as I do now) I may want to switch my GitHub user from one to another. Today, switching that user will disable ALL OF THE CI JOBS. And I will have…

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

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

    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)
  20. When merging a Pull Request that is linked to an Azure DevOps work item, indicate the user who performed the merge

    Currently, when a PR is merged into an Org (and the PR is linked to an Azure DevOps item), a discussion comment is added to the DevOps item documenting the merge. However, there is no indication in the comment to document the user who performed the merge. The Author of the comment appears to be the owner of the pipeline, not the user who performed the merge. My suggestion is to either make the author of the comment the person who performed the merge, OR in the content of the comments, add a line to indicate "Merged By: [Name of…

    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)
← Previous 1 3 4 5 6 7
  • Don't see your idea?

Feedback and Knowledge Base