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. Add option to provide exact time in case automatic deployment

    We need to set exact time for automatic deployment. We need this option for example for night releases for specific client. This is important for international clients that works in different time zones

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  2. Make metadata filters easier to use when you want to "include all except X,Y"

    For CI jobs, it is not uncommon that you want to include all elements of a given custom metadata type except specific elements

    Today, you need to have two entries - an include all (".*") expression and an exclude expression. For users who are not regex savvy, this is too complicated.

    We should have "All", "Named", and "All except Named" at the top level so simple check boxes can be used.

    This is particularly useful for CI jobs (whose purpose is to sync VCS w/ org) - you want to sync most everything except a few items - like Sites…

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  3. Ability to differentiate between scheduled metadata deployments from validated packages and non validated packages

    Under Deployment History

    1. All scheduled packages should appear. This is not the case today, validated packages that have been scheduled appear under validated packages with a Scheduled Date but not under Deployment History

    2. Scheduled packages should have a link to the appropriate Validated package if any.

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add an option to disable Problem Analysis for CI

    When running CI jobs, we can create a problem analysis template to control what potential problems can block a deployment.

    For deployments from SF orgs to Git, many of the problems being analysed are just irrelevant (e.g. users don't exist in the target, because the target is not Salesforce).

    Although some options can be switched off via templates, the list is not comprehensive. So, it would be great to have an option to switch off everything, or a built-in template of "no analysis".

    When production is the source of truth, we just want all the metadata to get copied into…

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add the ability to order/chain overnight jobs

    Gearset offers various automated jobs that run overnight e.g. Org Monitoring Snapshots, CI Jobs, Unit Test Runs.

    it would be great to be able to set an ordering on how those run for any particular org. For example, a natural order for the night jobs may be:

    1. Monitoring Snapshot
    2. CI run
    3. Unit testing

    This means we have a backup before making any potential CI changes and the unit tests show the results after CI. It would also allow us to make sure that the jobs don't clash.

    Ideally, we'd be able to do this without just specifying exact times 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

    0 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  6. For failed CI job runs, develop a way update to the job status

    When for whatever reason, jobs can get job stuck in status "Deploying".

    The real deployment task is already successfully finished in the org, so I would expect that the status of the CI job would be "Succeeded".

    I was assured that in 24hrs the status of the job will automatically reset, but can we have also a way to force an update to the CI job manually?

    Note: The "Cancel running CI job" button is visible and clickable, but doesn't do anything with this stuck CI job.

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  7. Run all tests only when have apex classes in the package

    Hello,
    I want suggest an option to avoid run unit tests when no have apex class in the package.
    And run all tests when have any apex class in the package.

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  8. Run only apex test thats related to the Pull request for Validate pull requests targeting the source branch

    When we check Validate pull requests targeting the source branch for the Pull request , it runs all the test class irrespective of the package content that being pushed.
    It should not run any test class if pushed metadata is only configuration.
    It should run only test class if pushed metadata ha class.

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  9. Automatically identify and run unit tests for deployed classes

    When deploying, we have standard options for running tests. It would be great, if we have an option for "auto-specified tests" where Gearset would automatically find test classes for classed being deployed.
    It can be done that in Setup, the team will define what type of extension the test classes has and then Gearset would use that key to find matching test classes.
    E.g. we have the class "AccountServices" and we have developed a standard set that the test class has extension "Test", so "AccountServicesTest". In the Gearset setup we would set the variable for tests to "Test".

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  10. Empty cache during meta deployment process

    Before you deploy but after you start the process it should be possible to refresh / empty cache to make sure that any updates to the meta data in either source or target are updated.

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  11. Gearset should control the order of deployment for Report Types, Reports and Dashboards

    Dashboards require Reports, and Reports require Report Types. Yet when I attempt to deploy a group of components that comprises all of the necessary components, I'm hit with errors that the required components don't exist <yet>. That shouldn't happen. This is going to <artificially> require me to do multiple 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

    0 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  12. Allow Source to choose multiple Branch for CICD Validate/Deploy

    when choosing source as GitHub it allows user to choose feature/*** which allows every commit on branch name starts feature will trigger the CICD

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  13. Deploy on pull request creation

    Currently is supported only validation on pull request creation. It would be great if we can also do deployment on pull request creation, not only on merge.

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  14. Don't auto-select all tests when choosing "Select which tests to run"

    When selecting "Select which tests to run" Gearset shows the tests included in the comparison first, but the moment all other tests are loaded, everything is selected.

    When choosing this option, the tests included in the comparison should stay on top and selected, and the rest of the test should be added alphabetically but UNSELECTED.

    If I'm choosing this option, I probably only want to run some tests. I think it would be much easier this way. Usually you need to run the tests included in the comparison and maybe one or two more.

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  15. Change Data Capture

    When installing a Integration Platform you have to enable the Change Data Capture in order for the platform to receive notifications on changes. At the moment updates under Setup/Integrations/Change Data Capture can not be deployed by 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

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

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

    0 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  18. Load Balancer for CI validation

    would be nice to have possibility to configure 1 source (git branch), but multiple targets (sandbox), so gearset would have some "load balancer", which would distribute the validations into sandboxes, which are not busy. Its taking too much time from developers to wait for their validations to finish.

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  19. Move Package Contents to Left Column on Deployment Screen

    On the "Summary of Items to deploy" page, the items in the deployment show in the 3rd column. So when you go to choose tests, you can't see what's in your package. Makes it very easy to miss a test.

    Illustration: https://imgur.com/a/wbZOeiZ

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  20. Allow setting the default testing method for deployments

    I want to enforce that any deployment into a UAT sandbox runs all the tests. The standard Default option runs no tests since it's a sandbox. I have to manually choose the "Run Only my Tests" Option every time I deploy to that sandbox. I would like to be able to have that option selected by default

    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  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base