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

113 results found

  1. 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)
  2. 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)
  3. From the gearset pipeline view, i wish there an option to export all the pull-requests including the respective git branches in a csv or .xl

    From the gearset pipeline view, i wish there an option to export all the pull-requests including the respective git branches in a csv or .xlsx format

    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)
  4. Allow Automations For Job Configuration Changes

    This could also go under: Problem Analysis and Deployment Failures, as it affects how you can analyse why pipelines may be failing.

    I would be nice to be able to have the ability to set up an automation which alerts one or more GearSet users that when a Job's Test configuration for Apex Unit Tests -> Run Tests is at a certain value for a specific amount of time or at a certain time.

    e.g. the value for Run Tests is not set to "All your tests" and it is 8am in the morning, I want to be able to…

    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)
  5. User Access audit Report to contain "role"

    Please update the User Access Report to include the Roles a user has been granted.
    For User Access Review and Role Review audits, need to provide this information to auditors.

    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)
  6. Collective list of release components

    It would be great if we have a way to find out details regarding the components being deployed to lower orgs or part of the release/sprint that team is working on. For Example, we have Gearset integrated with Azure DevOps (boards) and if Gearset can pull the iteration path along with work item details and when I specifically click on the iteration path for a sprint or release, I should get a list of all the components that are linked with work item deployment. This will help us a lot before the release to check the list and see if…

    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)
  7. Notification on job start, end with the Salesforce deployment/validation Id

    When a new Job is created, it would be great to have the notification/webhook sent on start and end the job, that way, we have a monitoring outside of the Gearset on it. As well as this, to be able to build soe automations based on 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)
  8. Visual Sync Alerts for "Commit more changes" Workflow

    Summary:
    Introduce a sync indicator for features in the pipeline. This would alert users when a feature branch has received additional commits (via the "Commit more changes..." button) that have not yet been promoted to downstream environments.

    Problem:
    When an admin or developer adds metadata to an existing feature branch that is already sitting in a downstream environment (like UAT or Stage), a "parity gap" is created. Currently, the pipeline doesn't visually signal that the version in UAT is now "stale" compared to the version upstream.

    This creates a risk where a user might promote a feature from UAT to…

    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)
  9. Allow Archive Notifications for both successful and failed runs

    Currently, when an archiving policy runs, you can send out a notification if a run has been successful or a notification when a run has failed. I cannot see a way to have both notification types as I would like to see at a glance how many records have been archived in each run, but I also need to know when it fails with permission issues after deployments or major releases. I do not go into the Archive section every day.

    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)
  10. 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)
  11. 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)
  12. 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)
  13. 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)
  14. Terse Slack/Teams Notifications

    Provide a Terse Notification format for Teams and Slack Notifications.

    Currently, the amount of information in Teams and Slack notifications is satisfactory, however the presentation in the chat app is very dense and can take some time to grok when you're browsing the history of these messages either scanning the jobs that have run over the past few hours in your channel, or just trying to understand what just happened from the push notification that went to your phone.

    Ideally, the first sentence is terse and is separated by white space from the remainder of the current paragraph format.

    The…

    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 the ability to add "Shared Mailboxes" to "Deployment Notification."

    It would be logical to have the ability to add a shared mailbox to the "deployment notifications" for individuals.

    The current logic is that you need to add a user, however the only way to do this is create a SF user in a DEV org for the shared mailbox which is not clean or logical for a mechanism of a notification.

    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. Audit API - Production Filtering

    From a compliance perspective, we only need to ingest production changes. It appears there are fields like 'SalesforceOrgType' on Anonymous Apex Endpoint and 'TargetMetadataLocationType' on Deployments Endpoint.

    It would be great if we could filter those, even better if you could bring in Production Org ID / Name into that filtering ability and in response 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)
  17. Make the PR Title same as the validation friendly name and deployment friendly name

    This helps us find the related validation and deployment to the CI job without having to open multiple validation/deployment records.

    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. Create a Combined view of Monitoring and Pipeline with Alerts

    Monitoring is great, but doesn't have a correlation to Gearset deployments (direct or Pipeline).

    A view of all changes to org and call-outs of which were Gearset-driven and which were manual would allow us to use Gearset more directly in SOX audits as proof of controls.

    Giving us actionable items, whether its in Gearset UI or Source Control to document review and approval of manual changes would be a huge win.

    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. Allow automated unit test execution to run tests synchronously

    When unit tests are run in parallel you can often get intermittent errors such as UNABLETOLOCK_ROW. When running tests from Salesforce you are able to specify running tests synchronously which takes longer but prevents conflicts between tests. Can this option be added to Gearset for the automated test running?

    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. Deploy monitor results changes to target org directly from the compare screen

    I get the a monitoring results email. When I click it it takes me to the comparison screen
    Right now to deploy those changes I have to go to Monitoring > Filter by name > View History > Select the right one > Deploy changes to target org.

    Those are 5 clicks to get to a place I just was in! It would be great if I could deploy the changes to the target org directly from the screenshot comparing screen.

    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?