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.

I suggest you ...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Migrate audit fields

    When deploying data records, it would be helpful if audit fields values could be migrated

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data  ·  Flag idea as inappropriate…  ·  Admin →
  2. Show Created By and Created Date when doing comparisons

    When looking at a comparison it shows changed by as a column, would be helpful for consultants to Show Created By and Created Date as well

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add the option to purge on delete

    The metadata API has a boolean option to "purge on delete", i.e. permanently erase deleted items rather than just moving them to the recycle bin. This option is not exposed in Gearset currently, but rather hardcoded to "false". For CI scenarios in particular, it would be extremely helpful to be able to specify that this option should be set to "true" for deployments.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  4. Be able to exclude single items from comparison

    E.g. If I generally want to include all Custom fields for all Objects in the comparison, but there’s one specific field that I don’t ever want to send across to the target org, it’ll keep popping up and I’ll have to uncheck it each time.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  5. Track Items Added to Draft Packages

    It would be nice to be able to see which items within a comparison are part of Draft Packages. We have a need to build multiple packages from a single Comparison of Instances. This can be done by creating many Drafts, but it is sometimes difficult to know if items have been added to a draft package already. If we could visually see this, it would allow us to generate and confirm our packages much faster.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  6. Ability to set a friendly name to the package

    Should it be possible to set an equivalent of "friendly name" in Gearset but one that can also be spread to Saleforfce.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  7. add the ability to run static code analysis against an org or source control, simply click refresh button to re-run it and see results

    This will give you a "run code analysis -> see results -> fix issues -> push to source control (or an org) -> repeat" workflow.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  8. test class not captured in deployment history

    It would be nice to capture whatever test classes ran for code coverage deployment of classes/triggers in the deployment summary in the Test Results section. You already have a section for this test results so why not add the class names used in the report. We have come across many classes deployed without their appropriate test classes and it is hard tracking/documenting which test classes were used to deploy these as there are no documentations in the class.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  9. Allow for custom metadata permissions to be included with a single click when custom fields are being deployed

    For example; when adding new custom fields, you generally have to add the permissions as an additional line item to the deployment. Having a checkbox or something that will have gearset automatically add the permissions associated with the metadata currently in the deployment list would speed up the process. Users should also be allowed to deselect lines that were automatically added.

    10 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add default compare filter - Code changed by me today, changed by me last 7

    A super common comparison done by a developer is to see only the Apex changes done by that developer today , or in the last x days

    Since the last changed dates on Apex (VF, triggers, components) is super reliable whereas it is useless on Custom Field/Workflow), the suggestion applies only to Apex or code-type changes

    Gearset would fetch only those code items changed in the last x days, then present in the difference viewer the changes pre-sorted in descending date order

    This feature would eliminate multiple clicks just to deploy a handful of recently-made code changes in the comparison…

    2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  11. Support parallel testing during CI job

    CI jobs use metadata API to deploy and run tests. The tests run serially. As such, CI jobs can take many minutes to execute

    As an optional configuration for a CI job, and only if the CI is run against a non-PROD org...

    1. Deploy metadata using Metadata API
    2. Run tests using Tooling API (parallel testing)
    3. If tests fail, use MetaData API to rollback the deployment

    Ideally, this can shave off 50% of the CI job time

    2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  12. give the ability to ignore certain changes between Sandbox and Production enviornments

    After deploying from a Sandbox to a Production environment, you will always see a 'change' for Custom Objects and Custom Fields because there is no Encryption Scheme (for example)

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  13. Jira: ability to associate tickets during comparison

    Would like the ability to associate Jira tickets during the comparison process so that it can be saved to draft deployments and can continue to add as needed. Currently it appears you can only add Jira tickets after you have finalized all items for deployment.

    3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  14. Allow Monitoring Jobs on Source Code Repositories

    Currently, Enterprise users can create monitoring jobs on sandboxes, so that they may be notified when a sandbox's metadata changes. It'd be great to be able to perform the same monitoring action against source code repositories (GitHub!).

    An example use case would be detecting when undesired metadata types enter into the repository. This is important because CI jobs will fail on certain metadata types, so we want to ensure that they never make it into source to begin with. Additionally, our business has decided that some metadata types should never be captured into source.

    9 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  15. Ability to add custom trigger points to trigger CI from source control

    At the moment the tool allows you to only kick off CI jobs when a branch is updated.
    This is actually limiting the capability of the tool in itself,
    because services like Bitbucket allows you customize trigger points, as to when they should ping the webhook;
    such as the creation of pull request, merging a pull request.

    The two trigger points mentioned above are specifically very important because you would want to run validation CI jobs on the creation of pull request or when the merge completes so that you can actually ascertain if your branch compiles.

    Based on an…

    6 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  16. When pushing Workflow rules and associated actions, gearset mistakenly says target objects do not exist

    When pushing work flow rules and associated actions, if you do a compare with only workflow, then gearset prompts an error indicating that the target objects do not exist in the destination and that the rules should be removed from the package for the deployment to be successful. In this case, it told me Account, Event and Opportunity do not exist in the target. Including other metadata from the referenced fields resolves the issue.

    5 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  17. Skip CI Jobs to source control when there are no changes.

    After setting up a CI job from a Salesforce sandbox to a Bitbucket repo, it looks like the CI job always runs a commit, even if there are no actual changes. It would be great to not have this happen to avoid having many commits where there are no actual changes.

    9 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  18. Provide options to delete records from Target Org. This will help clean up of test data and reload from Source.

    Provide options to delete records from Target Org. This will help clean up of test data and reload from Source.

    2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data  ·  Flag idea as inappropriate…  ·  Admin →
  19. Notify Slack when deployment is successful

    I would like to inform Slack on when a manual deployment is successful or failed. It will tell me what the source environment and what was the destination environment. It will also tell me if what the success/fail ratio of the tests that were run.

    6 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  20. Improve detection of custom fields on Managed Package objects coming from Git

    If I have a managed package object in Git, Gearset does not recognize it as managed package code in its comparison to a Salesforce org. This is a problem since it may not recognize a change if a custom field has been added to the managed package object.

    8 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  • Don't see your idea?

Feedback and Knowledge Base