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

339 results found

  1. Use Draft deployment name as the Friendly name...

    Would it be possible to have the draft deployment name, default to the friendly name under deployment history?

    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

    Completed  ·  1 comment  ·  Admin →
  2. Monitor Orgs feature -- Turn off monitoring for metadata types

    Monitoring orgs is great, except for orgs (in my case) that have Site.com Metadata. Each day that the monitoring runs it reports changes because of the MD5 checksum value is changed.

    So to see the changes from the monitoring screen I have to click into the org and the monitored job, click into history, then into comparison. When nothing on the org has really changed other than the checksum value it shows differences (which makes sense).

    What I would like is the ability to turn of monitoring for this metadata type. Or possibly more than just this type if there…

    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  ·  Admin →

    We have removed the Site.com metadata type from the default comparison set, so change monitoring jobs will no longer include this by default.

    In addition, when you create your monitoring job, you can specify which metadata filter you’d like to use. This will let you choose exactly which types of metadata to monitor for changes.

  3. Display deployment history in a list

    Currently viewing the deployment history requires opening a pdf. If going back in time the only way to find a specific item that was deployed is to open one pdf at a time and look for the change.

    It would be great if clicking on a past deploy would show items deployed in a list form on the page itself. This would make finding a past change easier.

    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

  4. Please don't try and deploy 'changed' Process builder processes.

    Process Builder Flow versions appear as separate elements for deployment. Unfortunately you can't re-deploy an existing Flow, it won't let you change it, so Gearset shouldn't suggest that as an option.

    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

    The latest release of Gearset includes additional dependency analyzers which should automatically find and resolve the issues around deploying flows. This includes detection of active flows, flow definitions, and deletions of flow definitions.

    My colleague Matt has emailed you with a more detailed summary of what’s changed.

    Jason.

  5. HTML email template - require Letterhead

    Currently when deploying an HTML email template I get an error. This is due to the Letterhead not being present at the target. If I select the letterhead in the source and deploy it along with the HTML email template the deployment succeeds.

    It would be nice if Gearset could see this dependency for the Letterhead and prompt to include it as part of the deploy

    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

    Completed  ·  2 comments  ·  Admin →
  6. Object level filters for Monitoring

    Object level filters for Monitoring

    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

  7. 7 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

  8. Support v37 API Metadata Items

    I'm unable to deploy metadata items that were introduced in v37 of the API.

    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  ·  Admin →
  9. Track deployment validation errors more easily

    When a deployment or validation fails, Gearset helpfully provides a list of the failure reasons. But when I go back to the comparison to make the changes, it's easy to lose track of what needs to be fixed. Adding the ability to export or save the warnings so I can easily work through then as a reference list.

    0 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  ·  Admin →

    You can now export deployment failures as a CSV file from the validation or deployment failure screens. The CSV show the objects and their associated errors.

    We may add additional functionality to this over the coming months to expand on how we track and display errors to make the process even easier.

  10. 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

    Completed  ·  3 comments  ·  Bug  ·  Admin →
  11. Email notification for failed deployments

    Getting an email when a deployment succeeds is nice, but it would be nice for failed deployments too. (Unless maybe I've missed an option for this?)

    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

    Failed deployments will now trigger an email notification, just like successful ones.

    The email contains a summary of the failure information, and a link to the failure report where you can begin to debug and fix the errors.

    Thanks for the suggestion! :)

  12. Desktop Comparison - "Referesion Comparison" does not clear modal background

    Using the Gearset Deploy desktop application (specifically for on-disk comparison):
    1) Compare environments
    2) Wait for loading until comparison view loads
    3) In comparison view click "Refresh Comparison"
    4) Click "Refresh" in modal

    Result:
    Grey background for the modal remains. No interface elements are clickable.
    Note: Tabbing to elements behind the window shade still works.

    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 →
  13. Configurable code coverage limts

    The test automation nicely tracks code coverage and allows me to see when I'm getting close to 75%.

    It would be good if Gearset could be configured to warn me when any of my orgs approach a limit that I control.

    For example, we mandate 85% code coverage for our production org and I'd like to be notified if we start to dip below that.

    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

    This feature has now been released.

    When creating a job, you will be able to set a test threshold percentage. When your code coverage falls below this threshold, Gearset will notify you using your chosen notification settings.

    Thanks for the suggestion. :)

  14. Show more info on source control on comparison screen

    Would be nice to see something like "SOURCE: reponame, branchname (username)" when comparing with a repository.

    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

    Completed  ·  0 comments  ·  Admin →
  15. Deployment summary screen

    On the Deployment summary screen, there's no indication on what are the source org and target org. Would be nice to be able to check before the actual deploy.

    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  ·  Admin →

    This has now been released.

    The pre-deployment summary screen now lists the source and target org so you can be totally sure what you’re about to deploy the changes to.

    Thanks for the suggestion.

    Jason.

  16. Display more information when a test method fails during deployment

    When a test method fails during a deployment in SF, we get the message and the stack trace. This can be really useful in tracking down the source of the problem.

    Gearset currently only gives the name of the method that failed, so extra info would be great. Ideally both the message and the stack trace.

    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

    This has now been released. If a deployment fails due to a test failure then you’ll get the full stack trace in addition to the failure message. Let me know if there’s anything else you need from that part of the app

  17. Add BitBucket Integration

    Would be awesome to have the equivalent of GitHub and GitLab for BitBucket!

    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 →
  18. Allow users to choose when change monitoring and unit testing jobs run

    The change & test automation is great, but we can't choose when these jobs run. The option to choose when to run jobs so they don't coincide with dev work would be a great addition.

    10 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

  19. Add support for GitLab

    Like the integration with GitHub, to compare and deploy from repos to our Salesforce orgs.

    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  ·  Admin →
  20. Option to run tests when deploying to dev or sandbox orgs

    You run tests when deploying to production orgs, which is great, but sometimes I want to force tests to be run when deploying to sandboxes or dev orgs. Can you add in an option to run tests for these orgs?

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

Feedback and Knowledge Base