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

1130 results found

  1. Add ability to customize CI Dashboard

    We have a number of different teams using Gearset with a number of different CI jobs. I don't care to see their jobs in my dashboard and they don't care to see my jobs on their dashboard. It would be great to be able to customize my dashboard so that I only see the jobs I'm interested in. Maybe it's some sort of flag on job to be able to add/remove from dashboard or maybe its a separate tab called 'My CI Jobs Dashboard' that we could default to when opening CI Jobs. Thanks for your consideration.

    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  ·  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. Allow Username/Password authentication option when selecting target/source orgs during cloning a deployment package

    Currently, when cloning a deployment package or re-deploying a package to a new target, it only works with OAuth authenticated orgs. It would be nice to have more of my available saved orgs to be a target/source when cloning a deployment. I am not able to authenticate a target or source using a My Domain or Username/Password with this method.

    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  ·  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. Allow download of the zip package for failed CI jobs

    Download the Gearset constructed package from CI job history when the CI job failed

    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)
  4. Provide controls around who can create/manage Salesforce Connections

    I have a team of multiple admins that use GearSet and I want to fully control who can deploy where. I can set this up with security today in GearSet by what kind of access I grant. However a user can create their own connection using their credentials and get around the shared connections I have established. I would like the ability to disable a users ability to create new connections which would then only allow them to use pre-existing connections that I have established appropriate security for.

    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. Warning On Missing Custom Metadata Field

    I had a deployment fail today due to a difference between a custom metadata type's definition in the source org vs the destination. The source had two extra fields that the destination did not have. This cause the metadata record deployment to fail, because two extra values were included in the deployment which did not have corresponding fields in the destination. Because the fields were for a custom metadata package, I was unable to (easily) add the fields into the destination org.

    I'd like to see a way to suppress custom metadata values. This may be solvable through the inline…

    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. Add an option to not run the comparision part in CI job (sfdx like)

    When you are pushing a project with sfdx, there is no compare, sfdx just push the whole package.

    It will save a lot of times.

    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. Ability to carry out action after successful deployment or detect org changes (monitoring)

    After every release, we have to do smoke testing. We do have automated testing using selenium and we wanted to trigger the automated testing every after release is detected. It would be nice if in the deployment we can call an api or webservice after successful deployment. Or in the monitoring we can call an api when there's a change happened in the org.

    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)
  8. Warn about Email Deliverability setting

    Warn users when they are about to deploy (data OR metadata) to remind them when "Email Deliverability" is turned on.

    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  ·  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. Allow deployment of Email header/footer changes

    Examine changes to Email Footers and allow deployment of changes.

    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  ·  Data deployment  ·  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. Ability to chose SFDX source format (force-app) compare or old style (src)

    Add a checkbox to chose wheter we want a sfdx compare or an old one (in order to not let gearset chose for us)

    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

    1 comment  ·  New feature  ·  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. Jira Integration: Include the option to add a comment in JIRA with the URL of the pull request created from Gearset + Assign reviewers

    After a deployment to a git branch, gearset allows to create the pull request from Gearset. It would be nice to:
    1. Have an option to add the pull request URL to the deployment notes
    2. Have the capability of add reviewers (users from the git repo) into the Pull Request

    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

    0 comments  ·  New feature  ·  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. Associate pull requests to work items in Azure DevOps

    When you create a pull request from gearset, the pull request isn't associated with the Azure DevOps work item.

    6 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

    3 comments  ·  New feature  ·  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. 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. 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)
  15. Manage multiple Gearset teams from a single Gearset account

    I want to be able to manage multiple Gearset teams from a single Gearset account, and not have to log out and log in again.

    17 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. Add a tab for Items that the Items I Selected Depend On

    It would be so cool if there could be a tab that shows all the items that my selected items depend on. It would be much easier to review / select them then the way I do it now, which is expanding each item in the Selected Items tab to check for things I need to add.

    Thanks!

    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)
  17. Metadata filter - ability to select Report/Dashboard folders by parent folder name

    When setting up a metadata filter for a new comparison, when it comes to Reports and Dashboards, it would save sooooo much time if they could be selected according to the top-level/parent folder that they reside in. That would enable the ability select all reports within a single parent folder at once, rather than having to select reports separately which reside in a nested/child folder.

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Separate the Custom Settings <object> Permissions and Metadata Type permissions from the Profile or Permission set

    When promoting Custom Objects and their security, we have to look at Custom Object Permissions (after loading the respective Profiles and Permission Sets in addition to the Custom Objects). We should follow a similar model for Custom Settings and Custom Metadata Types. The reason is that, if they remain part of the Profile or Permission Set, then I have to make sure that the Profile or Permission set exactly matches what I want in the target environment - I can't have any extra Custom Settings or Metadata Types that don't exist in the target environment yet or the promotion will…

    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. Link to salesforce source records

    When reviewing a Comparison with Salesforce as a source or target, include a link to the Setup/Configuration page that is being compared. For example, a link to a Page Layout that the user could click to jump right to the Layout in the appropriate Salesforce environment. There are times when we review Comparisions and need to see the source outside of Gearset and this gets the user there much faster.

    The link would appear in the header of the Comparison window, near where "SOURCE" and "TARGET" are listed.

    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  ·  New feature  ·  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. Account owner should be able to delete templates created by others

    If a team member is removed from Gearset team, any template or previous activity can not be removed by anyone else. Leaving some clutter behind. It would be good to have the Owner of the Gearset account/team to have a super admin level access to all templates/data created by other team members so clean up could be managed....

    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)
  • Don't see your idea?

Feedback and Knowledge Base