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

241 results found

  1. Ability to use Sandbox Source Tracking features as opposed to a comparison filter

    The comparison screen is great to help admins and declarative users see the changes they made. However, it still requires them to know which metadata to pull based on changes they made.

    Source tracking in Sandboxes is in beta and would alleviate this concern.

    https://help.salesforce.com/articleView?id=sfdx_setup_enable_source_tracking_sandboxes.htm&type=5

    If Gearset could leverage this functionality (potentially leveraging SourceMember object or storing .jsons to track last modified times as local projects store) it would make the complete process easy to use for all alike (pull metadata, select diff, deploy).

    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)
  2. 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)
  3. Modify the "Changed On" drop down filter groupings to round to the nearest day, rather than the exact time the change was made.

    It would be helpful if in the "Changed On" dropdwn filter if it grouped it into days, rather than the exact time the change was made. Also, if there were preset groupings like "Today","Yesterday","Last 7 Days", etc.

    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)
  4. Provide an option to run Aura and/or LWC testing before deployment

    I don't think that very many people are actually creating Aura/LWC tests yet, but they really should be.

    Since SF doesn't require them like it does for Apex, if we decide that those tests ought to be run before deployment, it would be great to have Gearset run them. This will help us to make sure they are run before every deployment instead of relying on developers remembering to do it manually.

    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

    Started  ·  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)
  5. Add default compare filter - Code changed by me today, changed by me last 7

    A super common comparison done by a developer is to see only the Apex changes done by that developer today , or in the last x days

    Since the last changed dates on Apex (VF, triggers, components) is super reliable whereas it is useless on Custom Field/Workflow), the suggestion applies only to Apex or code-type changes

    Gearset would fetch only those code items changed in the last x days, then present in the difference viewer the changes pre-sorted in descending date order

    This feature would eliminate multiple clicks just to deploy a handful of recently-made code changes in the comparison…

    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)
  6. Allow option to select certain test classes to NOT run. Include an exclusion list of tests not to run

    When deploying code, it would be nice to have an option of having an exclusion list of test classes to not run.

    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)
  7. Please, please, please get US FedRAMP approval.

    The ability to use this product for CI/CD and various other use cases in the US federal space would be a huge win for many agencies. I know the FedRAMP process is quite arduous, but the contractual potential here is pretty massive.

    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

    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)
  8. Deployment pipeline view personalization

    Currently, the view in continuous integration (deployment pipeline) is sorted by ABC, which is not user friendly when there are many team members. In this case I appear last and I need to find myself in this screen.
    I suggest you to either:
    1. allow creating personal views per user, so I can see only my dev sandbox, full sandbox and production.
    2. change the scroll into a "regular" scroll, and not the current drag scroll

    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

    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)
  9. Make Pipelines a Top-Level Menu Item

    This is a less-good, but arguably easier to implement, version of my request for customizable landing pages. It takes a few clicks to get to pipelines and, since it's the place I live most often inside of Gearset these days, I'd love it if it was a menu option that is parallel to "Continuous Integration" so I could get there in fewer clicks.

    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

    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)
  10. Add a Tab to manage Metadata Comparison Filter

    Add a menu item or tab where we can
    1. Share, delete, edit names of the custom Metadata Comparison Filters.
    2. See the comparison history, who used the filter and when in team etc.

    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

    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. Approval process for metadata deployment

    It would be great to have a approval process for the deployment.

    For example, once we have completed the comparison and validation, we can click a button "e.g.: Submit for Approval" and an email will be sent to a list of email.
    In the email, receiver can review the summary of the deployment (e.g.: source org, target org, number of changed/new/deleted components, ...) and click on a link to approve or reject the deployment.
    We can deploy only when the job is approved.

    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

    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. New Feature: Filter Custom Fields (and other sub-components) in Comparison Filters

    I'd like to be able to exclude certain custom fields from my comparison.

    For example we have fields that have environmental differences between orgs that we don't want to deploy. There are also random fields on standard objects that show up as "different" even though they aren't and it would be nice to filter them out.

    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

    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)
  13. Support for WaveRecipe metadata is missing

    There is no support for Wave Recipes currently and we are not able to deploy dashboards via Gearset and Continuous Integration.

    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

    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)
  14. Include support to name space filter to include option to include unlocked packages with no namespace

    Currently there is no way to retrieve and compare components belong in an unlocked package with no name space without using the 'include managed package' namespace filter 'all' option.

    this might include too many items that I am not interested in.

    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

    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)
  15. Deploy permissions for Lightning Record Pages

    provide a means of deploying the profile/recordtype/app permissions for lightning record pages without having to deploy the whole app.

    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

    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)
  16. Separate Filters for CI Jobs to reflect filter edits

    Currently, if you have a saved filter being used in CI jobs, any edits/changes to that filter are not reflected in the CI jobs that use said filter.

    It'd be great if we could isolate filters for CI jobs so that we could edit CI job filters that would then affect every CI job they're being used with instead of having to edit every job and re-select the filter whenever a change is needed.

    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

    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)
  17. Selectively filter managed package metadata without excluding unpackaged components

    Add the ability to filter in/out managed package elements from a comparison set at metadata type level. e.g. allow for the comparison of managed package objects and fields but exclude other managed package metadata types whilst allowing those types to be available for non-packaged constituents. More specifically for instance, exclude manage package page layouts and include managed package custom fields whilst including both unpackaged page layouts and custom fields in the comparison set.

    The reason for this is to minimise the comparison set which can reach limits due to size whilst including all mandatory metadata elements for a deploy.

    Using…

    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

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

    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)
  19. Add deployment support for Macros

    Macros deserve to be added to source control yet there is no way to do this with Gearset:

    1) Data feature (paid add-on) doesn't deploy to/from source
    2) PRO/Enterprise can't source/target deploy Macros because it is not available with the Metadata API.

    Since macros represent some debugged logic, managing in source control makes sense. Curiously, SFDC has chosen to make Documents available via Metadata API but not Macros

    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

    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)
  20. Restrict source orgs

    For example, deployments to a production environment should only come from the master branch of our git repository

    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

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

Feedback and Knowledge Base