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

250 results found

  1. Ability it use SOQL to provide complex filters on Vlocity and Salesforce Metadata types to create custom Compare & Deploy Filters

    I would like to have the ability to enter SOQL queries to filter Metadata types and data. Currently you can only use Object or Regex when you try to filter the data to fine tune the comparison. We are looking to do this for Vlocity and Salesforce metadata types and objects

    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

    2 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. 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)
  3. Remove files from a PR

    I want the ability in Gearset to selectively remove files from a branch or PR without running another comparison.

    I have an admin that frequently "over commits" too many things.

    Often its bad enough that its just easiest for them to delete the branch in github then start over in gearset.

    The problem then is that starting over from scratch, a day or two since they worked on it, and they will make a different mistake.

    I'm aware of a few features, like

    1. Delete the branch in Github and start over in gearset

      • Seems to be the easiest to me
    11 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)
  4. allow automatic publishing of an experience site after deployment

    Just like you can automatically activate Flows in Gearset upon deployment; it would be nice to automatically publish deployments of Experience Bundles. This is especailly true for deploying Experience Bundles to staging/qa orgs but applies also to PROD.

    There's an API to do this: /connect/communities/communityId/publish documented https://developer.salesforce.com/docs/atlas.en-us.chatterapi.meta/chatterapi/connect_resources_communities_publish.htm

    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  ·  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. Visibility to Log Files for Connections and Compare & Deploy Events

    When you either make connections to 3rd party applications or run a Compare & Deploy, there is no visibility to the log files, I feel these should be accessible to the user so that we can understand the reason why something is failing and not have to have someone provide this information. Additionally it should have options to change the level of logging to provide detailed information when needed

    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)
  6. Implement a Ticketing Feature

    Salesforce DevOps Center has a useful feature that allows users to create different Projects that have their own pipelines. Within each Project, you can create Work Items (similar to Issues in Jira). The user can then perform their work in a Salesforce environment and then run a comparison to associate certain changes to respective Work Items.

    From there, each Work Item can be promoted through the various environments in the Project pipeline.

    This is really helpful when working on numerous tickets/features for a given project, knowing exactly which environment each Work Item is in and the various metadata elements that…

    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

    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)
  7. Set up notification according to the target connection we're deploying to.

    Set up notification according to the target connection we're deploying to. This way, the scheduled and manual deploys will notify us with what we set up.

    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)
  8. Allow open PRs to queue up.

    Allow open PRs to promote via selection and to queue up against the target keeping blocking behaviour to just merges and the deploy activity

    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. Display auto-merged files during Conflict Resolution

    The Conflict Resolution only displays files that require manual resolution. Sometimes I want to see the files that were automatically merged without human intervention.

    The only way to see this is to submit a resolution as is, then read through the file changes again to look for files that were auto merged/resolved from target instead of source.

    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)
  10. Pre-fill Pull Request Description with comments from last commits

    In order to save time, when a Pull Request is created from the Pipeline, the Description field could be pre-filled with the comments from the last commits in the feature branch, instead of forcing the User to type something.

    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)
  11. Save sort order of grids

    It would be nice to be able to sort by column names and save that sort order for the next time the page loads or save a default sort order. We sort often by jobname and would like to not have to resort everytime we need to touch a ci job to sort the column.

    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)
  12. Is it possible to get an additional field in the compact view of the jira ticket ?

    Is it possible to get an additional field in the compact view of the Jira ticket ? We would like to add Fix Version as well as what already exists.

    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)
  13. User Data & Logs

    For audit reason we have been asked to provide a comprehensive user list with the following data:

    User Status (Active/Inactive)
    User Creation/Removal Date
    Created/Removed/Updated by
    Updated Value (if you change the role of a user from member to owner or opposite)
    User Last Login Date

    These data are part of the user audit control (create/update/remove users) and are very important to prove you have control who gets access, and there is no risk for unauthorized access but also to prove that segregation of duties is in place.

    Thank you!

    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)
  14. 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)
  15. Get Notified if Pull Requests or Validation Fails

    Our Org has Gearset Officers who handle promotions. It happens at times that I create a pull request and have it start validating (which can take a while). I'll navigate away from the screen and totally forget about it, assuming it'll get pushed to the next environment.

    But sometimes there are merge conflicts, or validation fails. I'd love to get a notification, either in email, or as an integration to an attached jira ticket that it failed. That way ill be notified by slack or whatever.

    Just an addendum here. We use 3 environments. Admin, UAT, and finally Production. When…

    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

    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)
  16. Show PR Flow changes in Flow Navigator View

    New new Flow Navigator view is really good.
    It is such a shame that I am only able to view flow in flow navigator in comparison view (when creating pull request).
    I would love to be able to open flow in flow navigator directly from teammates open pull requests. That would really speed up reviewing flow changes cuz reading metadata on VCS is not the clearest thing to do.

    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)
  17. Ability to Customize Export Items in Comparison

    Currently we are able to Export All of our comparisons. It would be a nice addition to have the ability to customize the export. For instance, as the GearSet user, I would like to be able to export specific items. I would also like to be able to include either the "depends on" or the "used by" items in my export as well as the specific items that are used or depended on.

    IE:
    In my export, I have selected Object A, Object B, Object C, Report 1, Report 2, Report 3, Flow X, Flow Y, Flow Z. In total…

    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)
  18. Adding Identity Settings to Metadata Deployment

    Would be nice, if the Identity Settings can be deployed. Currently, every change on any Identity Settings page has to be done manually in each org.

    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)
  19. Allow us to update the Associated Azure DevOps work item on a successful deployment

    Currently within the successful deployment page, you can edit the 'Deployment friendly name' and 'Deployment Notes' which is a very handy feature.

    However sometimes we would need to also update the associated work item as the wrong one can be mistakenly associated, this would be a very useful feature for us as a way of correcting such mistakes (that are in fairness rare).

    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)
  20. Bulk resolve merge conflicts

    We occasionally run into a situation where there are quite a few files with conflicts to resolve. We almost always are just wanting to accept all changes from the feature (not the environment). This takes an excessive amount of time through the Gearset UI to accept changes in every file. Would it be possible to add a button accepting all changes from feature across the entire PR?

    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  ·  Admin →
    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 12 13
  • Don't see your idea?

Feedback and Knowledge Base