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. Do selective restoration instead of a full restoration.

    We want to restore certain fields instead of all data into Salesforce

    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 →
  2. Add Component's Label and API Name to Export CSV results

    Please include columns for the components Label and API Name along with the Item Type and Display Name when exporting to CSV.

    Use Case - We use the Export results as a formal Deployment Log that we sharing with a Client's project team. In that log, we include the component's Label, API Name, and metadata Type. Most recipients of this Deployment Log are unfamiliar with the API Name which may not even closely match what the Label is. Having both in this Log would greatly enhance this understanding.

    Thanks in advance!

    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 →
  3. 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).

    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 →
  4. Monitoring enhancement: compare permissions across users

    It would be cool if the Gearset Permissions Explorer would help you in determining how to collapse Profiles into fewer numbers. The model would be https://perm-comparator.herokuapp.com/

    A typical org has proliferated Profiles over the years, many only slightly different from one another. As SFDC wants us to move to Permission Sets, job one is to collapse the profiles into as few as possible - this requires comparing user permissions against each other (you can't just compare profiles, you need to know what additional permissions some users have vs others too)

    Since SFDC is finally making dynamic Lightning pages GA (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

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  5. Combine validated packages

    Hi Team,

    Please add checkbox for validated package as same as deployed ones. that way I can combine package even for validated one's and deploy.

    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

    2 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  6. mark destructive only changes as a separate difference

    due to deployment limitations with salesforce destructive changes destructive changes dont necessarily reflect branch to org so these deltas are being marked as differences even though there is no way to fix other than manually in the org. these should be marked as a separate difference type for easier filtering.

    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 →
  7. Enable Gearset login from corporate SSO solution

    an additional layer of security and convenience would be to enable Gearset login (that is, login to Gearset) to be done from an enterprise's SSO solution. We use Duo but Okta and others should be supported.

    Just like we can login to Salesforce from our enterprise's SSO , we should be able to login to related apps in our suite of enterprise tools via SSO

    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 →
  8. Global Search feature

    It would be very useful to have a Global Search feature within Gearset. This would be used to search the contents of all metadata objects.

    My use case is that sometimes a string has been hardcoded inside a function. The only way to find the function that contains the string is to manually trace through the code. The global search would indicate the function that contains this string.

    Another benefit would be to track dependencies for metadata objects that don't support dependency tracking. For example Aura Components, we could search for the component name.

    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

    1 comment  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  9. Support JWT authorization to DevHubs

    If Gearset could authorize the DevHub using a JWT (requires DevHub to have a Connected App and Gearset to be given the clientId + server.key + username) ...

    Then:
    * Scratch orgs created by Gearset could be accessible to any other machine provided that machine is using the sfdx force:auth:jwt:grant command (same clientId, server.key, test.salesforce.com, and username of scratchOrg)
    * This is a prerequisite to any outgoing webhook that wants to auth against the CI scratch org
    * This is a convenience feature to IDE users who want to auth against a Gearset-created scratch org without having to get a…

    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 →
  10. Migration/Deployment Path

    In cases where you have multiple environments, provide an option to define a migration/deployment path; ability to define what environment is the source and what is the target. This will be useful in cases where we have requirement to deploy changes to say production from a specific environment (UAT).

    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 →
  11. Make CI-created scratch orgs more usable by downstream webhooks

    If a CI job creates a scratch org ; and you configure an outgoing webhook in the CI configuration, the subscribers to that webhook have no way of being able to connect/authenticate to that scratch org.

    The typical use case would be to run automated UX testing (Provar, Selenium)

    At present, even the CI job creator can't log into the CI-created scratch org let alone any CI webhook

    In addition to supporting this, there should be doc on how a downstream webhook can access the scratch org to then do useful work.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add Static Analysis Notifications

    For org monitoring, we can get a notification on either every run, or when the org changes.

    Could we also have the option to get notification when the number of static analysis problems increases?

    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 →
  13. Suppress the <deprecated> tag in CustomObject, CustomField

    When retrieving metadata from 1GP packaging orgs, the <deprecated> tag appears in the source and, if you deploy to VCS, is preserved. But if you subsequently deploy to a scratch org, and back to VCS, the deprecated tag no longer appears in the scratch org and thus shows up as a diff in the Difference Viewer - confusing the user.

    Doc says this tag is reserved for future use and until such time as it is used, suppress

    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 →
  14. Add Additional Deployment Preferences for JIRA integration

    Currently the Jira Ticket Deployment Preferences don't give you enough options to manage the expected behavior with our process. Right now there is too much noise on our tickets and we want the option to reduce that. For example, we do not need to comment on the ticket when attempting to validate deployment, just as we don't need it for failed deployments (which you already have as a feature). We simply want a comment with the deployment notes when a deployment is made since this would reflect the actual system changes that took place with this feature/issue.

    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 →
  15. Show test apex run in the deployment report

    When we validate a deployment then schedule it for deployment. Once deployed we receive a report however the tests run do not show here and you have to back to the validated section to find them - please include the tests run on the final deployment report

    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 →
  16. Be able to log into scratch org from Deployment Success page

    It would be super convenient to log into the scratch org directly from the Deployment success page

    • From Compare & Deploy sequence
    • From CI success
    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 →
  17. Tie scratch org URL to enumerated list of scratch orgs on My Connections

    UX suggestion (tie list of scratch orgs to URL)

    If you use Gearset to create a scratch org, the list of scratch orgs on the My Connections page does not tie to the visible URL of the scratch org you log into

    This gets to be a real issue for the multi-tasker who might have several scratch org tabs open at once but has no way of knowing which one is which vis-a-vis the Gearset enumeration of how the scratch org was logged into the first place. Drilling into the user's name is too clunky

    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 →
  18. One stop shopping for scratch org creation

    Too many steps to get a scratch org usable for use - especially when compared to a CLI script.

    If the model is VCS -> Scratch Org, then the following should be doable in one step:

    1 - Create scratch org
    2 - Populate scratch org with metadata in VCS
    3 - Populate scratch org with SObject tree data from VCS (optional)

    By definition, the scratch org is empty so with a properly configured filter, the VCS metadata is implicitly all NEW and can be preselected checked

    If the VCS contains multiple packages, then the pipeline config could identify which…

    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 →
  19. Allow users to hide or collapse the middle bar of the comparison screen

    I have a small laptop monitor, so screen space is pretty valuable to me when working from home. It can be difficult to do code reviews from a laptop monitor because of the middle bar, which takes up a significant amount of real estate.

    I rarely use any of the controls or information in that box. It would be great to be able to collapse or hide it to allow more space for the top panel (list of metadata components) and the bottom panel (selected metadata contents)

    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  ·  Flag idea as inappropriate…  ·  Admin →
  20. Only see deployment history for Orgs you have access to

    We would like to only see Deployment History for the Orgs we have access to. Our clients brought this up as a concern during our deployment meetings.

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

Feedback and Knowledge Base