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. Jira: Ability to pass a list of Jira ticket Ids vs. single entry

    Would really benefit from being able to paste a list of Jira Ids, e.g. comma-delimited (similar to specified tests) on final deployment. Hate giving up validation / deployment status writebacks to Jira, but often we have packages spanning dozens of Jira tickets and entry can be time-consuming, especially if there is a failure or refresh needed and Jira ticket associations get lost from the draft.

    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

  2. Ability to trigger different CI jobs or changing the targets based on the user who did the commit in source control

    Related to CI jobs can you set up multiple jobs to trigger based on which user did the commit to source control? The goal would be having the deployment / last modified dates in SF reflect which user did the commit in source control and triggered the CI job.

    I don't think that's possible as I don't see any kind of filter or way to manage which CI job should fire when source control is updated so the audit history in SF will only reflect one specific user doing the deployments and people would need to review the details in…

    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. Need a Integration of Gearset & Jira , once the user story is updated in Jira , My gearset job will get triggered

    Need a Integration of Gearset & Jira , once the user story is updated in Jira , My gearset job will get triggered and deploy the components related to that user story.
    and once the deployment is done , update the jira ticket status as deployment done.

    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

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

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

  6. Basic Authentication with Jira

    As our local hosted Jira instance doesn't allow unnamed connections it would be great to have a basic (username + password) authentication for Jira as well as Bitbucket.

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

  8. Repository Rebasing

    Allows the Git repository to be rebased from the latest and greatest metadata from a target organization. In just few clicks the gearset will download all the latest metadata from a target org and will check in it inside master branch

    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

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

  10. Add Validate pull requests for custom git

    We have self-Manged Gitlab as a git provider.
    It would be good to have the possibility to allow to run validations on pull requests for custom git repositories or

    support on-prem GitLab (submitted as https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/39728857-add-validate-pull-requests-for-on-prem-gitlab)

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

  12. Option to choose CI validation run behavior with Open Pull Requests and Branch updates

    Currently, if you have a CI job set up to validate based on events (push, pull request) on a specific branch the following occurs:

    You open a pull request against the specific branch noted in the job - CI validation runs
    You push a commit to the source branch of the same open PR - CI validation runs
    You push a commit to the target branch of the same open PR - no validation runs

    In the conversation with Dan on 8/13/2020, I was told this is by design on Gearset's end (to ignore that situation) to avoid long queued…

    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

  13. Only show JIRA tickets with specific statuses

    We would like to the ability to only display JIRA tickets with specific statuses (e.g. Approved, In Progress).

    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

  14. Include the static code analysis report in the deployment notes so it can be integrated with Azure DevOps

    We would like to have a link in the Pull Request or Azure DevOps work item to the static code analysis report so the tech leads can review the report.

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

    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. no difference report

    Currently the deployment report that is attached to the Jira ticket includes all "No Difference" components which I don't believe provides any real value. In my instance, this includes endless amount of pages, from what I can tell the changed values I'm actually looking for don't actually exist. I would suggest either excluding from report all together or providing a summarized statement that is just a grouped item for all items that were included in deployment but had no change. Also the report should bring the actual changed items to the top of the report like it is on the…

    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

  17. Github: Ability to select Reviewers for pull requests created in Gearset

    Currently, you can create a PR after a successful deployment in Gearset. You're able to provide a description and even select it as a draft.

    However, the only potentially necessary field that's missing is "reviewers". This means any CI/CD setup you have that requires an approval requires the user to go into Github just to add the reviewer.

    Since Gearset would have all the team members (and those with linked github accounts), it seems it might be an opportunity to select based on that list and pass the linked username on to github in the PR creation to keep end…

    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

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

    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

  19. Filter branches by tag name

    In order to remove the clutter when selecting a branch to deploy to or from, allow users to apply metadata filters that dictate which branches show up in Gearset. For example, being able to specify that I only want to see feature branches.

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

    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

  • Don't see your idea?

Feedback and Knowledge Base