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. Allow searching Monitoring of a system by a specific record of metadata to see all the dates that the record changed

    If I need to find when a specific thing was changed in our system, my only option is either to use the last edited date or to manually check every daily comparison from Monitoring to see if it changed. Since many metadata types do not reliably update the last edited date, it makes it much harder to find those changes. If I could choose a specific metadata record and use that to search the Monitoring to see when it changed, it would be much easier to find it.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow custom endpoints for webhooks from Unit Testing and Monitoring Jobs

    You can post to Slack, Teams, and Chatter when an org monitoring job runs. But, as a consultancy, we'd like to post to our own SF org in a more general way. We have records for each of our customers, and it would be good to be able to report on summary data about the Gearset's monitoring for those customers.

    If there were a configurable endpoint we could target that at a custom REST endpoint on our Salesforce and then join things up.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  3. Send different deployment notifications based on the target org type

    Successful deployment notification is for all sandboxes. It would be nice if we can have a separate notification for production and sandboxes as certain people only care what goes to production. Thank you!

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  7. Show number of changes or new components in validation only Continuous Integration Job History

    When you click on "View History" for your Continuous Integration job, it shows every run and for each run has the following columns:

    Attempted Changes
    Changed
    New
    Deleted
    Problems Fixed

    For validation only CI jobs, all the columns show "0". It makes sense that "Attempted Changes" should be 0 (as nothing is deploying), but it'd be helpful to still see the appropriate # of changed, new, and deleted to get a sense of scope for the validation.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add a Description field in the General Settings for Automation like Continuous Integration.

    We LOVE Gearset. I just took over when an employee on my team moved to a different team. I was looking over the existing Monitoring jobs and had to ask why some of them were setup. They were similar with the exception of when they run, for example. It would be helpful to have a Description field in the General settings section so when someone creates these jobs, they can give a brief description of their intent and purpose. Thanks.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  9. More custom monitoring delays

    It would be brilliant to be able to choose the days of a week your monitor script runs on so I don't have to deploy changes every single morning and could instead do once a week

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  10. Filter deployment and comparison reporting by user in the account page

    Right now Gearset is showing Total Deployment Team wise . My suggestion is to Publish User Wise Count of Deployments with all Successful , Failed Deployments .

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  11. Download metadata from monitoring job in SFDX format

    Please add the opportunity to download the metadata from the monitoring and backup job in SFDX format.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add Failure Information to CI Job's Email Notifications

    Currently, Unit Test jobs provide a nice email notification of what tests failed right in the email body.

    CI jobs, however, provides the same generic message for failures for validations as below:

    "The validation only CI job, Release Validation, has failed. Find and fix the validation issues on the error summary page in your CI job history"

    and for CI deployments

    "A continuous integration job, Prod to Dev3, has failed. No changes were deployed to the target org.

    Find and fix the deployment issues on the error summary page in your CI job history. "

    It'd be great to get…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  13. Distinguish between process builder and flow

    If you do deployments of flows and processes from process builder, both of them are handeled as a flow. If you need to activate the flow or process manually in a production org, you need to guess if it was a flow that you have deployed or a process.
    Please within the deployment report (and the comparism), distinguish between flows and processes.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  14. Provide more detail in Monitoring notifications

    Right now, the Monitoring job notifications (Slack especially) provide very little detail as to what actually changed.

    Ideally, I'd be able to see right in the message (or in a threaded reply), the first X number of metadata changes made. If there are more than that, then providing a direct link to the detail page in Gearset would be great.

    As of now, it simply just says "there were changes", with no detail or way to easily see the changes in Gearset...which is not terribly useful.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  15. Export test run history

    Exporting the Test run history to Excel/CSV will allow keeping trends.

    The ultimate goal is to include this in a dashboards. If an embedable web page could be generated with solely the trends, that would be perfect.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  16. Email notification selection: none, success, failed deployemnts

    In account settings allow me to choose what kind of notifications I want to receive to my email.
    [ ] Send me success deployments notifications
    [ ] Send me failed deployments notification

    No selection means do not send any notifications.

    Why? With many deployments my email is bombarded with notifications. Last two weeks 65 emails which I do not read as I see status on screen. Therefore I want to turn off those notifications.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  17. On 'deployment' and 'draft deployment' pages provide a way to see the filter information without having to open the full comparison screen.

    On 'deployment' and 'draft deployment' pages provide a way to see the filter information without having to open the full comparison screen. We need a quick way to make sure that item level filtering is being used on each metadata type

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  18. Attach pdf items details in the email notif "Your organization has changed"

    When you receive a notification concerning a change into an organization you need to know quickly which items are changed.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  19. Mass delete option for deployment history

    You can select multiple deployment history rows to "combine packages", but it'd be nice to be able to "delete all selected".

    This is useful if you'd like to clean up a cluttered history to only see successes and what actually went in to an org.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  20. Allow searching for Org IDs in deployment history

    Enable the search results in Deployment History to include Org Ids.

    USE CASE: I want to see a history of all deployments into, or out of, a specific org, regardless of the usernames used to deploy.

    BONUS POINTS: allow me to specify whether it's the ID of the target org or the source org when searching. ex -
    targetorgid:00D1U000000sfXD
    sourceorgid:00D1U000000sfXD

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base