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. Refresh specific item in comparison through context menu

    It would be great to refresh a specific item within a comparison that I know has changed since the last comparison.

    21 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  2. Inline Editing of metadata

    Inline Editing of metadata
    In order to make our deployment successful we had to download the package, modify the version numbers on the flow definitions, and then compare the local package to the target org. It would be very helpful if we can edit the metadata XML in the UI so we can fix the version numbers.

    24 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  3. API to provision users, assign users to connected organisations

    API to provision users, assign users to connected organisations

    It would be hugely benificial to us (60+ connected organisations, 25 employees working in teams for multiple clients at a time) if we could programatically provision/deprovision users and provide access to connected organisations via an api.

    At the moment this is error prone manual work that has to be done by someone with high level access (and as such is usually already short on time).

    6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allow users with owner role to modify and start backups

    Allow designated users the ability to modify and start backups without being the owner of the connected org or the person who created the backup.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  5. User Last loggged in and User Usage

    It would be great to see when a team member last logged in on the user account management page. It would also be great to see like a report or extension on the user page where we can see user usage information. Like number of compares, deployments, etc.. may when last compare was done.

    11 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  6. Treat "New" FLS entries that don't grant any access as "Not Different" in Profiles and Permission Sets

    Due to a recent change in the SF API, Permission sets now display every field in the org as a "New" FLS item, with Readable and Editable both set to False. This is leading to two distinctly negative results.

    1) For every "Permissions for FieldNameXXX" item, every permission set in the org is modified. If two projects on two different sandboxes each add a field, they will both modify modify all the same files, and require manual XML merge. for our org thats almost 70 files that need manual merge with every new field.

    2) When you dig into a…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  7. Explicitly set object-level permissions, even if these are omitted from XML provided by Salesforce API

    Valerio recommended that I post this suggestion following a discussion on 29 August 2019.

    Issue reference:
    https://docs.gearset.com/en/articles/3226459-a-note-on-deploying-custom-object-permissions-on-new-profiles

    Issue:
    1. Remove all object-level access for "Lead" from a custom profile in a source org
    2. Deploy this profile to a target org
    3. The profile in the target org will have access to the "Lead" object ENABLED, because this access is included in the Standard User profile (see document link above)

    The workaround (deploying and then deploying again) is cumbersome and not always practical, e.g. if making automated, one-step deployments outside of Gearset. Failing to make a second deployment means that…

    17 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  8. Use triggering branch as source branch in git-sourced CI jobs

    Currently:
    We have to define a single fixed source branch in a CI job, when it has a Git-Source.

    Desired:
    Option to say "use triggering branch". It should use the branch, where current commit-hook-call comes from.

    It should allow Pipelines to test also all development branches e.g. with "Validation only" CI-job.

    9 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  9. Ability to specify test suites when deploying apex classes. It would be easier when there are a large # of test classes involved.

    Ability to specify test suites when deploying/validating apex classes. It would be easier when there are a large # of test classes involved with a deployment

    8 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  10. Resolve "Data Owner" User metadata from difference comparisons (always exclude or compare, then exclude)

    Salesforce has begun adding User metadata to fields. One good example right now is the "Data Owner" field that appears on all custom fields now (in XML this field is labelled as "BusinessOwnerUser"). The field does not link via a Salesforce ID; it instead displays the Salesforce Username of the user.

    Naturally, this field in 99.9% of Salesforce environment comparisons is going to be different. "user@domain.com.sandbox" won't ever match to "user@domain.com" in production-- and it definitely won't ever match to any other Sandbox, either.

    This leads to a nightmare scenario where if this field has been…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  12. create an option to have chained deployments

    create an option to have chained deployments so complex deployments can be broken down and sequentially deployed or slaves can be ran

    allowing for multi staged deployments under one CI job

    21 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  13. Support package.xml filtering when using Git comparison with a SFDX folder structure

    When using a git repo with a SFDX folder structure + package/xml (in the /manifest folder) gearset dos not take into account elements in the package.xml when checking the option (filter with package.xml)

    24 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  14. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  15. Provide ordering for metadata elements when committing to version control

    When metadata is retrieved from Salesforce the order of child nodes is not guaranteed and results in false-positive changes when committing to version control. Usually this will be something simple like workflow actions/criteria appearing out-of-order which can be compared manually. However, recently we've noticed entire profiles being committed with every permissions element out-of-order, resulting in a change set with ~20k lines where the actual change is impossible to visualize.

    Gearset should provide a feature to 'order' child XML elements alphabetically by name in order to provide consistent commits to version control and eliminate false-positives.

    7 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  16. like in autorabbit ability to chose incremental build in CI

    Ability to only deploy the difference between the last 2 commits (incremental build) will dramatically reduce the time to run a CI job

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  18. Allow selection of Metadata types to be deleted in CI jobs

    As of now, if you have deletions enabled in a CI job, everything is deleted. It would be great to be able to specify which metadata types you want to include in the deletions since normally you won't need to delete all differences. This would be specially helpful to remove Apex classes and its permissions from profiles.

    17 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 25 26
  • Don't see your idea?

Feedback and Knowledge Base