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. Include Test Run Details in Deployment Report for Validated packages

    In the Validation deployment flow, there currently isn't a way to view test execution results if they aren't manually exported during the process. Having the ability to view the Validation Deployment report and details in this deployment flow is actually more valuable than the actual deployment report that is generated.
    If we can't have that, it would be nice to be able to continue to export those test run results after deployment as part of the deployment details.

    7 votes
    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 →
  2. include the Name/ID of the Deployment from Salesforce into the Deployment Report generated by Gearset

    Include the name/id in the deployment detail page within Salesforce in the Gearset deployment report so we can trace and match those details to a deployment run in Gearset.

    3 votes
    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 →
  3. Allow notification for long running jobs

    Allow a for a notification to be sent when a Continuous Integration job runs longer than N minutes. Most of our jobs tend to complete in under one minute, so if a job runs longer than 30 minutes, being notified would be helpful.

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

    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 →
  5. Allow transfer of org ownership between users

    I need to set up monitoring against an org that is owned by a user who is no longer active or licensed in the system. It would be incredibly helpful to be allowed to transfer ownership of these orgs between users, rather than requiring someone to delete the org and recreate it under the different owner.

    5 votes
    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 →
  6. Cruise control feed for Deployment Steps

    We are planning to let our team notify and keep informed about the deployment steps status just that they can stay informed about it. These are non-Gearset users.

    Can we have a monitoring feed for Deployment steps that take place from Compare and deploy Screen 1 which contains basic deployment details (Source and Target). So as an When we progress with the deployment steps, it will keep it updated. Similar what you have for Unit Test monitoring feed. (Test monitoring Cruise Control feed)

    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 →
  7. Stamp a validated package with the username of the person who clicked 'Validate'

    Currently, a validated package is created by the owner of the draft deployment package, even if someone else was the one to actually press the 'Validate' button. I would like to have the username of the person who actually pressed validation to be noted somewhere in the validated package for auditing purposes.

    This would help us be compliant with processes where we need a record of separation of responsibilites bewteen users.

    2 votes
    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 →
  8. Provide reporting capabilities for Deployment History

    Our executive sponsor for Gearset has asked me to provide him with some metrics around our Gearset usage. Specifically, we would like to be able to have access to some of the data that already exists in the Deployment History section, but in a format where we could report on it. Ideally, we'd be able to show how many deployments to production, how many components deployed in those packages, frequency of production deployments in a given timeframe, etc.
    This would be a very valuable feature for us so that we can ensure our executive leadership team is briefed on the…

    4 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 →
  9. 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 →
  10. 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 →
  11. 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 →
  12. Allow scheduled jobs to be assigned a different authentication user

    We would like the ability to change over scheduled monitoring/testing jobs to a different authentication user. Currently if we need to switch an authentication we lose the history.

    Consider:
    I leave my employer and I need to switch the monitoring over to another developer or admin. I have to delete all the current scheduled jobs and re-create them using the other users authorization. Which causes the history to be lost.

    7 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 →
  13. For CI Jobs initiated by Github, dynamically send CI failure / success email to the user who committed to the repo.

    Currently, we can only specify a list of users to email, a Slack channel to update, or a Chatter group to post to when a CI job is successful or fails. If there are multiple notifications to a number of people, it's likely they will filter out these messages, so being able to notify the person who the CI Job is most relevant to would be a good improvement.

    7 votes
    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 →
  14. Ability to search Deployment History for specific metadata

    On the "Deployment History" tab, the filter dialog filters on the visible friendly name and items like that. What I would like to do is enter a specific metadata name and have the list filter down to deployments where that specific metadata name was a part of the deployment. This would be useful when getting the question, "when was xyz last deployed?"

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

    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 →
  16. 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 "ALREADY_IN_PROCESS 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

    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 →
  17. Org Management/Oversight Dashboard

    I would really benefit from a dashboard option. A single place where I could see my CI Job history, Unit Testing Jobs and Monitoring/Backup history for all/a subset of my orgs.

    I am using Gearset more and more to manage the state of my org's metadata, so it would be nice to be able to see it all in one place.

    3 votes
    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 →
  18. CI Validation Job report should show version of metadata API used for CI

    A nice-to-have UX feature would be to echo the metadata API version used in the CI Job on the Validation Errors report (or any CI report). This can be used to aid in troubleshooting

    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 →
  19. Trust Site

    Right now, Gearset is down and we cannot use it. It would be good to have a trust.gearset.com site that shows what is going on and what the team does to fix the issue...

    3 votes
    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 →
  20. Ability to have automated process to maintain field list in Production environment

    With GDPR, companies are required to provide justifications for all data that they collect. In Salesforce this means being able to identify why all fields in the system exists, categorize fields as PI, and provide business justifications. The ability to keep a list of current fields in a production instance of Salesforce that includes alerts when new items are added, or ability to sync that list out to another tool like Smartsheet, where other business users like a legal team would have visibility, would be incredibly useful.

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

Feedback and Knowledge Base