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
  1. Make it available to commit custom labels that are part of a managed package

    Custom Labels of managed packages do not show up in the comparison because they cannot be changed and therefore are not deployable. However, the (override) translations of these Custom Labels do show up and are deployable. It is possible to deploy & commit the translations but this poses an issue if you commit to git since gearset suggests to leave them out of the commit because they are missing a dependency. If you ignore the suggestion and commit them anyway, they'll be removed the next time the repo cleaner runs. This way, it cannot reliably be kept in git.

    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

    0 comments  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Retrieve Metadata into local environment (e.g. using VSCode pluging)

    This would make the integration of Version Control and Gearset nicer. Where now user has to go to Gearset deploy to a feature branch, afterwards, go to VSCode pull from the feature 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

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Rolling back deployment made by CI JOB

    Currently it is possible to roll back a deployment made by CI Job, though that rollback will only be performed to the specified Org. Hence, other Orgs have to be rolled back individually.

    Use case: I have propagated changed from my Sandbox to Staging. An issue was identified that requires a substantial amount of work where that feature cannot be included in the next deployment to production, hence it needs to be removed from Staging. Though, other sandboxes back propagated that feature because they assumed it should work.

    It would be amazing if the rollback used Github commits, so 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

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Associated Work Items through Commit message

    As a Developer, I want to use a unique ID from the work item I am working on
    when I make a GearSet commit
    So the work item I am working with (like Jira) can have a comment stating it was deployed
    and I don't have to manually go to a separate process to update the ticket.

    Say my work items are in jira and I am working user story 100.
    There is a Jira ID that is unique to that work item.

    When I specify a commit
    instead of going through the separate process to find the work item…

    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. Write Deployment Results back to the user's Salesforce org

    When setting up a deployment, it would be helpful to capture Deployment Results in a custom object in the running user's Salesforce org. Users would be able to specify a unique reference at the point of deployment, which would track through to the Salesforce org.

    Information about the deployment would be captured in a Master record, with data about individual components existing in Detail records.

    Org admins would then be free to leverage automation features to map the created records as they see fit.

    As a consultancy that tracks our customer requirements in Salesforce, our use case would be that…

    13 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

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Clone Problem Analyzer Templates

    With CI jobs, you may need to refine over time your Problem Analyzer templates

    However, there is no clone button and you have to carefully set up the new template (as edit-in-place is not supported when the template is already assigned to a CI job - at least that is what the in-app guidance tells you)

    So --

    a) Allow Clone from page app.gearset.com/problem-analyzer-templates
    b) Allow an easy way to assign the new template to all CI jobs without having to do each 1 x 1

    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

    0 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Spurious analyzer; Required fields on target when deploying Custom Field Permission to a Permission Set

    If you deploy Custom Field Permissions for fields such as Task.ActivityDate or Task.WhatId to a Permission Set, the Gearset Analyzer auto-checks Do Not Deploy and shows this message: "Some field permissions in the deployment are for fields that Gearset thinks are required fields on the target side. Field permissions cannot be set for required fields."

    While this is a useful message when deploying Custom Field Permissions to a Profile, it is not a useful message when deploying to a Permission Set as that Permission Set might be used in conjunction with Profile "Minimum Access - Salesforce". If you are using…

    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

    0 comments  ·  Problem analysis and deployment failures  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Remove/Deactivate new feature for batch comparison

    A few weeks ago, Gearset added a new feature to officially make the comparison faster, by showing already results of first batch and add the rest later on.

    This feature makes it much more difficult to do comparisons. First of all, I don't see any benefit. I still need to wait for the whole comparison to finish, because I still need to now, what has changed. Why should I look into the first things, when I need to look into it again, after the rest is compared. So before I can select anything, I need to wait the whole time…

    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

    0 comments  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Add More Granular Control over Email Notifications

    Allow users to enable/disable categories of email notifications at the user level. E.g. success emails for monitoring jobs, deploy succeeded/failed emails, etc.

    Alternatively, or possibly in addition, allow users to "mass-edit" job notification settings, so we don't have to edit each one individually.

    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

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. UI Change: On any pop-up page using Source Control, auto-expand to show Create Branch button

    On a monitor job (and probably elsewhere), clicking "Deploy To" and then selecting Version Control target, you get a default branch, typically master. If you click the link to Create a new Branch from Master - you input the name of your new branch, but the Create Branch button is hidden below the display and you need to scroll down to show it. The Start Comparison button is where the Create Branch button should be, so you end up starting your comparison instead of creating the branch first. Suggesting to change the pop-out window to expand to show both buttons…

    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

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Show Formula Comparisons line by line

    When comparing formulas (in validations, formula fields, workflow criteria...) the comparison should be done line by line.

    Considering the whole formula a block and only showing that "something" has changed in the formula is not useful when looking for conflicts between environments.

    When pushing changes between environments, admins are checking to make sure they are not overwriting other changes with their update. They most probably know the formula has changed (that was their job) but they need to ensure no unwanted changes are added/deleted from the target environment.

    In long formulas with many lines (potentially >100) it's not easy to…

    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

    0 comments  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Revert with one click all changes from this PR

    Please allow reverting PR from lower environments. In mine example, we had a feature that went through develop and uat and was waiting in the pipeline to be added to release but the business changed its mind and canceled this whole feature.

    Please add an option that with one click we can revert PR and changes from lower environments.

    Image:
    https://www.dropbox.com/s/ohvymcs16p9n5ge/2022-06-30_14h10_44.png?dl=0

    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

    0 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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…

    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. Create a pop-up warning when on the Selected Items tab before you can deselect all items

    Without the Undo feature, there is the odd time (nightmare situation) where you haven't saved your compare and are on the Selected Items tab and accidentally deselect all items. It would be great to get warned that all work will be lost unless it's saved or the deselect action is canceled.

    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

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Unify the message when you authenticate an org with a username that has been shared. It uses the term "delegated" instead of "shared"

    Unify the message when you authenticate an org with a username that has been shared. It uses the term "delegated" instead of "shared". This could be confusing.

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

    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)
  17. Saved Comparisons should be visible to team members

    I have a team that has access to Gearset but unfortunately they cannot view the Saved Comparisons I've created. To reduce unnecessary time spent on creating and maintaining Saved Comparisons, it would be greatly appreciated if the Saved Comparisons could be shared with the team and possibly allow the owner to delegate access to the Saved Comparisons.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Run Flow tests during test monitoring jobs

    With the new flow tests, it would be nice if we could also have these run within test monitoring jobs.

    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

    0 comments  ·  Testing  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. to let us configure the default metadata filter by deployment pipeline configuration

    Can we please have a possibility to configure the "standard" metadata filter by each deployment pipeline project?

    I think it is currently preselected by the last used metadata filter from the standard comparison.

    As we usually have a specific metadata filter configured by deployment pipeline project, it would be great that we can configure each project with a default one..

    Thank you!

    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

    1 comment  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Test salesforce connections in mass to highlight which need to be re-authorized

    Having a way to monitor/test all salesforce connections in mass to then highlight which need to be re-authorized would be helpful instead of catching them when preparing to do a comparison.

    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

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →

    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