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. Include Pull Request title in the notification

    Hello GS team,

    Currently, the notifications from the pull request validations only include the PR number, I would like to request if it's possible to include the PR title.

    Current Sample: [Gearset] CI validation job Validation job for PR #11111 failed

    With the title in the subject of the notification, we can FW the results to the right teams automatically.

    Thank you!

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Gearset Service Status Page

    It would be very useful to see a status page for Gearset services. Similar to other service platforms like Github (https://www.githubstatus.com/) or Salesforce trust (trust.salesforce.com)

    This would be great to help determine if there are issues with deployments, or if Gearset has any sort of performance degradation.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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)
  4. 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)
  5. Create ListViews in the Continuous Integration Dashboard

    Create ListViews in the Continuous Integration Dashboard page and being able to grant access to specific users or groups of users.

    The idea is to avoid displaying specific jobs to a particular group of users for better organization and reduce the loading time when many CI jobs are configured.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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)
  7. 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)
  8. Hide re-ordering in a Monitoring job

    We have a monitoring job set up to check production changes. However, re-ordering in some components are popping up as false positive. For example, Entitlement Process and Site.com. Everyday I get an email saying # of changes have been made on production. I'd like to not see these false positives in the # so that I do not need to go to each comparison every day just to realize that it's a re-ordering issue.

    11 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. Ignore changes deployed to orgs from Gearset in Data Monitoring jobs

    I would like to be able to monitor changes made to tracked metadata in our Production org, but without the "noise" generated from normal deployment changes (made via Gearset deployments). Basically, I want to catch changes made directly to Production that are unaccounted for in source control.

    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. Allow all admin users to run the 'Take Snapshot' functionality on Monitor jobs not owned by them

    I would like all of my 'Admin' users (or specify which users in my org) can have access to run monitoring jobs I've set up.

    The scenario is that we're a small team, so I want to set up all of our monitoring jobs, but if an issue occurs while I'm OOO any of my other team members could run the 'Take Snapshot' function to determine which changes occurred since the last monitor job ran and roll the changes back.

    Currently users can edit/delete monitor jobs of other users and if provided 'Deployment' access can roll the changes back, but…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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)
  12. Consolidated Reporting for CI Jobs

    Hello. One item we struggle with is keeping track of CI Deployments that didn't fail, but didn't deploy as expected. The two causes we usually see are:

    1) Something was removed by problem analyzer
    2) We deployed something that Salesforce says succeeded, but no changes were made (e.g. deletion of picklist choices)

    We currently have about 100 CI jobs which makes it impractical to go into each one.

    The proposed format would look like a csv export:

    Job Name, Date, # Created, # Updated, # Deleted, # fixed by problem analyzer

    Opening a CI job history looks fine, but we'd…

    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. Have an ability to modify message which is posted to Slack channel.

    It would be nice to have the ability to modify this notification message somehow.
    E.g. include a number of PR which was merged into the main branch. Or remove extra information such number of deployed components.

    now it looks too big
    Gearset Continuous Integration
    A continuous integration run succeeded for ***** CI/CD. The job was a deployment.
    Changed objects
    3
    New objects
    0
    Deleted objects
    0
    Source commit
    1c***f2b

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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)
  15. 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)
  16. Ability to audit what users have done in Gearset

    Hi, I suggest there should be a feature which monitors what the users within your orgs have done in Gearset. As we can currently are able to view both comparison and deployment history, however this does not give an audit trail of who has changed what and where.
    For Example, the ability to review changes that a user has made to gearset comparison filters.

    6 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)
  17. 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)
  18. It would great to be able to monitor certain user actions, such as exporting a report in Salesforce.

    Right now, I am only aware of having to purchase an add-on from Salesforce to be able to get this information.

    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. Add the ability to report on validations and deployments via CI

    Currently, it's not possible to see a report on when a validation or deployment started and ended for a given CI Job across multiple PR's. This will help understand how long on average validations or deployments are taking for a given environment.

    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. Extend the functionality of configuring when are monitoring jobs run

    Hey,
    Currently it is possible to configure at what time during the day you we want to run the configuration jobs.

    For the org monitoring jobs, we really love that this is done daily, but for unit tests, we would love if we could configure the jobs to run the job weekly or monthly and not 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)
  • Don't see your idea?

Feedback and Knowledge Base