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

1285 results found

  1. Don't Delete Managed Package's object permissions from Permission Sets in CI jobs

    In a CI job, using source control as the source and including deleted items, you can run into an issue where objects from managed packages show as "deleted" in terms of custom object permissions from permission sets that have access to them. This can occur for permission sets designed to give access to managed package features or if you have a permission set with "View all data" or a system permission that gives them access to all objects in some capacity (read, write).

    Ideally, we wouldn't have to include managed package object permissions into Source Control (likewise, Gearset suggests only…

    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. Avoid spurious differences in LeadConvert

    SFDC seems to retrieve the lead convert settings in non-deterministic order between orgs . Display only true changes/adds/deletes rather than differences in ordering of the mappings as they make no difference to the runtime execution of Lead Conversion

    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. it would be great if deployments could be done automatically based on a event trigger

    To facilitate Automated Testing, it would be great if a deployment could be triggered by an event (such as a commit by a dev), so that an org is created to allow functional automated tests (not unit tests) to be run automatically without requiring any manual process

    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  ·  Testing  ·  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 the option to skip code coverage when running tests on a schedule

    skipping code coverage on apex test execution, helps tests finish faster.

    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  ·  Testing  ·  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. Avoid manual selection of component while compare and deploy

    Good to have options in Gearset to auto select changed metadata files(changed as a part of pull request) while doing Compare and deploy.
    Imagine one pull request number 5377 (which is changing 200 metadata files moved from 1 branch to another branch).
    Now while doing compare and deploy It is good to have options which auto select this 200 metadata for comparison. This can help me from this manual selection of 200 metadata files which is very time consuming.

    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)
  6. allow users to customize Slack notifications

    It would be great to have some ability to customize the notifications, specifically:
    - change sender/title. right now it just shows up as my name.
    - add a link to the monitoring history to allow wasy one-click into monitoring reports to see what specifically has changed.

    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)
  7. Keep the same record owner between source and destination orgs.

    Alternatively, allow the change of record owner before importing data to destination 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  ·  Data deployment  ·  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. add files to a gitignore during Suggested Fixes

    When I make a comparison, Gearset will helpfully check the deployment and offer suggestioned fixes, such as... exclude object components belong to managed packages. now, i can agree to that solution and exclude those files, the problem is they persist every time i make a comparison, they always show up as changes. Would it make sense to be able to add them to a list of ignored changes?

    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. Exclude the subcomponents of the parent Workflow metadata and also exclude list views from custom objects

    I want to exclude outbound messages from workflows as we will have different urls in different sandboxes. Same with list views we want to exclude them from custom objects so that we can use CI using gearset for deployments

    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. Option to choose CI validation run behavior with Open Pull Requests and Branch updates

    Currently, if you have a CI job set up to validate based on events (push, pull request) on a specific branch the following occurs:

    You open a pull request against the specific branch noted in the job - CI validation runs
    You push a commit to the source branch of the same open PR - CI validation runs
    You push a commit to the target branch of the same open PR - no validation runs

    In the conversation with Dan on 8/13/2020, I was told this is by design on Gearset's end (to ignore that situation) to avoid long queued…

    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)
  11. Only show JIRA tickets with specific statuses

    We would like to the ability to only display JIRA tickets with specific statuses (e.g. Approved, In Progress).

    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)
  12. Deploy Einstein Datasets from one org to the other

    Copying of Salesforce objects with relations is a great feature. But this does not support Einstein datasets to be copied from one org to the other. It is critical for teams to have Einstein dataset in the lower orgs for development and testing

    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. 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)
  14. 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)
  15. 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)
  16. 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)
  17. 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)
  18. 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)
  19. 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)
  20. 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)
  • Don't see your idea?

Feedback and Knowledge Base