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

102 results found

  1. Flexible Org Monitoring Notification Scheduling

    I'd love to schedule a weekly or bi-monthly digest email rather than receiving emails for each run or each change. There are developers who need to know when changes are made, but they do not need to monitor changes frequently. In those scenarios, it would be nice to schedule out a weekly review of all changes.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Add Time Column to the CI Deployment page

    Due to recent latency issues regarding SF performance issues, I would like to quickly see how long each CI job takes without having to download an individual report for each job. This can either be solved by either:

    1. Adding a field to the CI Deployment page so that I can compare each CI job

    2. Allow me to extract a complete report of all of the CI jobs and open it in excel with the time column so that I can compare the values. I can currently do this from the Deployment history page, however this does not include the CI…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. change monitoring for scratch orgs

    The Change Monitoring feature only supports normal orgs (sandbox, developer, prod). It does not support scratch orgs

    For use cases where developers inadvertently let their scratch org expire with pending, uncommitted work, it would be nice to recover the work before and after the scratch org expires

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Add tool to send emails after deploying to specific targets

    A project manager on my team expressed desire to receive reports when someone deploys to our production org. I would appreciate a tool that sends these emails only upon successful deployment to that specific org so that recipient's inbox is not flooded with every successful and failed deployment to every org.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Add a filter in monitoring job to exclude changes done by Gearset

    To help identify changes done manually to the org it would be nice to have a filter which excludes all the changes done by Gearset deployment.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Add Salesforce ID to Export History button

    Can you add the Salesforce ID to the Export History button for reconciliation purpose.
    We currently have to manually match the Salesforce ID in Gearset with the Salesforce ID on the Salesforce Deployment Status page to get the reference between the source ticket in Jira and the deployed change for compliance purpose which is a time consuming process.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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!

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Be able to start immediately a JOB (CI/Unit Tests/Monitoring)

    Add a button to start it immediately. Currently only solution is to change the executing time!

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. test Monitoring overview - show "is running" + stats

    On the Test Monitoring Overview page; you should be able to see at a glance whether the test is running and how many methods have run vs total

    Reason this comes up is if you establish a Unit Test run for your developer sandbox org, then you can't run (some) tests from your IDE against the same org "ALREADYINPROCESS Test already enqueued"

    A quick glance at the Test Monitoring Overview would tell you if you need to wait 1 minute vs 20 - and guide your activities accordingly

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Have the option to attach test details to test notification email

    When you set up notification options for test monitoring, there should be a checkbox for attaching the detailed test result csv file to the email

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. User Account Specific Validation Errors

    When deploying objects such as reports to a Target ORG, sometimes the reports are shared with a user in the source ORG. If the user does not exist in the Target ORG, the validation throws an error. Would it be feasible to add objects, such as reports, to the Warnings / Fixes screen so we can easily select how to handle user specific dependencies? Maybe we can chose to enter a new username or simply remove the shared with permission on the object?

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. View Locations Not Covered from test results

    In the Salesforce's deployment result metadata there is details -> runTestResult -> failures -> code coverage -> Apex Class Name -> locationsNotCovered.
    It would be very useful to be able to see the locations not covered of any apex class in the test results section of the UI.

    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. Add regex or other means to "exclude" strings in monitoring job

    The Wave dashboards have a key field that changes every day and causes false positives in the Monitoring jobs. I would like the ability to exclude that string pattern from the results so I don't have a bunch of changes that don't matter showing up every day. Regex seems like the most robust way of defining it.

    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. To provide the deployment history of all deployments, not only the ones from compare and deploy.

    It is useful to be able to filter and download all promotion history in a similar way we can do for deployment history.

    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. Unsubscribe from commit emails

    Choose to unsubscribe / subscribe from commit emails (success and or failures) in gearset setup in order to avoid generating unwanted emails (and their PDFs) for each deployment (and save a little CO2 along the way).

    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)
  18. Help to have a change log, including the name and email of the person who changed the test level in CI jobs?

    The test class level change in the job is crucial for us; if someone changes the test level to no test in place of a specific test run, components will go without a test run.
    So, if we monitor things on a regular basis, we can ensure that everything is in place.
    If we have a tab to get all these kinds of information, such as reports

    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)
  19. audit report missing PR message

    The audit reports don't include much context of the deployment, which means they are pretty useless to us and do not serve our auditors' needs. Specifically, they do not include the PR message for deployments through our pipeline, which means we can't link each deployment to the specific ticket responsible for that deployment. The PR message is where we put our ticket. This information is needed for our SOX audit process. Additionally, we can not see a link back to the deployment, which would allow us to quickly reference the specific metadata files/components that were deployed.

    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. Expand Notifications Capabilities

    Currently 'Notifications' found under 'Settings' in 'My Account' allow for send outs for your owned connections. It would be helpful to have the ability to make notifications for connections that have been delegated to you as well.

    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