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

1354 results found

  1. Cloning deployments: add namespace option

    If you are using Gearset to develop for a 1GP managed package:

    Your deploys between VCS and dev orgs/scratch orgs DON'T use namespace in the metadata filter

    Your deploy from VCS to Packaging org MUST USE namespace in the metadata filter - otherwise, everything in the difference viewer appears as NEW rather than CHANGED (if truly just edited during dev cycle)

    So, when cloning a deployment, one should have the option to add the namespace to the clone dialog.

    Without this, one has to repeat the Compare step thus losing the benefit of what you had enumerated in a prior…

    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)
  2. Spurious difference CustomObject excludedstandardbuttons ordering

    SFDC has a tendency from release-to-release of reordering the excludedStandardButtons for a CustomObject. If you are using source control populated under Vx and SFDC changes the ordering in Vx+1, your custom objects all show up as Changed in the differences viewer.

    Because these are "excluded" buttons, their ordering in the XML file doesn;t matter to the end deployment and the variance should be suppressed in the difference viewer.

    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)
  3. Use exact filters of Automated Job

    Currently automated CI job filters are unique to that job and not available as a filter for manual jobs.
    Ability to use the exact current job filter as a filter outside of the CI job.
    Ability to to clone the CI Job filter into a new named filter.

    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. no difference report

    Currently the deployment report that is attached to the Jira ticket includes all "No Difference" components which I don't believe provides any real value. In my instance, this includes endless amount of pages, from what I can tell the changed values I'm actually looking for don't actually exist. I would suggest either excluding from report all together or providing a summarized statement that is just a grouped item for all items that were included in deployment but had no change. Also the report should bring the actual changed items to the top of the report like it is on the…

    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. 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  ·  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. 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  ·  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. Workflow failed to deploy without error, due to standard object dependency

    In a CI job : Validation shown as success & Deployment shown as success. But actually no workflow deployed due to it being removed in the Problem Analyser.

    The Problem Analyser triggered due to the (standard) object, that the workflow depends on, not being in the comparison results.

    In a traditional deployments object is not needed to deploy WF, that too standard object. I feel it is a gap - problem analysers should never fire on object dependency.

    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)
  8. Workflow failed to deploy without error, due to standard object dependency

    CI job : Validation shown as success & Deployment shown as success.. but actually no WF deployed. Saying Opportunity object doesn't exist in target just because it was not selected in the components. in a traditional deployments object is not needed to deploy WF, that too standard object. I feel it is a gap.

    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)
  9. Link Static Analysis results to the code

    Could we link the file names in the static analysis results to the actual code from the comparison/monitoring job?

    i.e. Where the results have a list of issues per Apex class, I'd like the class name to be a link to the code for that class

    Having a quick peek at the code from within Gearset can help me to diagnose whether it's a genuine problem, or something where the static analysis rules need tweaking.

    If it's just the rules that need tweaking, it would be nice to be able to complete that job entirely within Gearset.

    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)
  10. 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  ·  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. 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  ·  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. Move the configured regex filters to the top of the scrollable pane (currently at bottom) of

    Move the regexes to the top of the pane so one can see they exist and not have to guess that they exist at the bottom of the pane.

    Note the example, selects all custom objects - this is useful for ISVs

    example: For custom object, there are 100+ entries for standard and custom objects. If you add a regex, it appears at the bottom of the scrollable pane, after all the enumerated objectnames. Coming back into a custom filter, it is not obvious that you had even created a regex as you would have to know to scroll to…

    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)
  13. Export Object level and OWD (sharing settings) in permissions reports (in addition to the field-level)

    Currently, the permission reporting feature only provides field-level permissions export to CSV for all Profiles and Permission Sets. This is a very small part of the overall security and sharing permissions model. Here are a couple of items that I recommend adding to the permission reporting as a starting point:

    1. Object-level permissions (read/create/edit/delete/view all/modify all) for Profiles and Permission Sets
    2. Sharing Settings (organization wide defaults) for all objects

    In the future, it would be nice to have additional permissions from Profiles and Permission Sets available to export such as:
    1. App assignments
    2. Tab visibility
    3. Apex classes
    4. Visualforce…

    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)
  14. "Next" button on comparison page sometimes does not work

    Sometimes, the "Next" button on the comparison page does not work. In the Developer Console I can see a 403 response from "POST https://app.gearset.com/api/static-code-analysis", traced to "raygun.js:2016".

    In this case, I have to reload the comparison page.

    This happens quite often (I estimate 1 in 5 times).

    I don't think that it's a timeout issue (CSRF token or sth.), because just right now I only marked one file in the comparison list and wanted to proceed, and the button didn't work.

    On other occasions, I spend a lot more minutes on the comparison page, and the button works perfectly.

    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  ·  Bug  ·  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. 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  ·  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. Yearly report of all previously migrated items.

    It would be great to get an end of year report or report of how many migrations were completed and a high-level list of components.

    Example:
    Custom metadata, lightning components, page layouts, fields, apex, etc.

    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)
  17. Show Read Only Source control Settings to Members

    Would be good to see the current settings of Source control for Members in read only mode.
    Currently what greats us is just a text message:
    "Only team owners can change these settings."

    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)
  18. Include the local file name on all the results screens

    When you choose a local file to use as compare, on every subsequent screen the only title you see is: "On-disk repository". It would be helpful to include the name of the file.

    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. Include the local file name on all the results screens

    When you choose a local file to use as compare, on every subsequent screen the only title you see is: "On-disk repository". It would be helpful to include the name of the file.

    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)
  20. Create Scratch Org dialog should echo DevHub name

    When you Create a Scratch Org, the dialog that appears doesn't echo the DevHub name used to associate the scratch org. Since one's Gearset user account could be authorized to multiple DevHubs, one loses the thread (breadcrumb) to which DevHub is being used for the new scratch 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)
  • Don't see your idea?

Feedback and Knowledge Base