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

1176 results found

  1. 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)
  2. Delta comparison between two unit test reports

    Hi team. Would be good to have a feature that allows us the comparison between two unit test results. We are interested to export the delta errors from one day to another.

    Use case: We are executing deployments for more than 50 pull requests against the same target sandbox, hence regression errors might be introduced throughout the day. We are running nightly unit test jobs and usually, in the morning, we have extra tests which are failing comparing with the previous day.

    We are currently exporting the gearset errors from 2 reports, in Excel tables, and compare these ones to…

    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. Comparison of draft deployments

    Two teams who are supposed to be working on different parts of the sandbox org have created two draft deployments. I would like to compare these draft deployments to see if there is any overlap of selected items.

    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. Highlight "Failed Validation" Components

    If the metadata Deployment Validation step fails, and the user clicks the "Back to Comparison" button, the components that caused the failure should be highlighted on the screen for manual review.

    Currently, when a deployment fails on the validation step, my process is:
    - Wait until the Validation step is done
    - Sort by the Status to show Failures on top
    - Take a screenshot of the list of errors (hopefully less than a full screen of errors)
    - Click the "Back to Comparison" button
    - Use the screenshot like a checklist to work through the errors
    - Run Validation…

    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. Configure the "Saved Comparison Pair" to always use a specific Comparison Filter

    When managing multiple orgs, and running comparisons, the Saved Comparison Pair saves a lot of time. However, sometimes we need to use different Comparison Filters, based on which environments we are comparing.

    Instead of first choosing the Comparison Pair, then manually selecting the Comparison Filter to use, it would be great to be able to (optionally) configure the Comparison Pair to use a specified Comparison Filter.

    Example Use Case:

    When committing work from our Dev org to BitBucket, we exclude Apex Classes & Triggers, and mainly commit declarative functionality (Apex code is committed separately from our dev team). All development…

    4 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. Automate Jira Status when a Pull Request is created in Pipelines

    Presently, the capability to automatically update the Jira Status of a ticket is limited to transitions occurring between different environments in Pipelines. Enhancing this functionality to include automated updates triggered by the creation of a Pull Request would prove beneficial, eliminating the need for manual intervention when transitioning to stages such as "Code Review."

    5 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. Multiple sort columns for comparison results

    It would be helpful to be able to sort comparison results on multiple columns (e.g. first by Metadata type, then by Name). Currently it seems that the results can only be sorted by one column at a time.

    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. Show Created by and Created Date in Comparison view

    I'd like to see created by and created date in the comparison view. Sometimes we have multiple users working on items and I may not be the last to modify something but I am the one to deploy it and if I am the creator, I know what it is named but it makes it hard to sift down if I can only show modified by and modified date.

    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. Soft delete of deployment History

    When a person deletes a deployment history that was successfully deployed, it would be good if that deletion was only a Soft Delete and could be recovered within 90days.

    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

    0 comments  ·  New feature  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Add pipeline support for CPQ

    CPQ deploys to and from Github/Salesforce so it should be a relatively simple issue to include this in the pipeline deployments. You could add a checkbox or just warning to ensure that triggers are manually disabled when that is needed.

    5 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. Improve audit API to extract list of users and their entitlements. Additionally, allowing us to provision & deprovision user access via API

    We use 3rd party tools to audit all of our user access at our company. Automating this via API instead of exporting CSV and loading that into another tool would be very beneficial. Additionally, we use that tool for provisioning and deprovisioning so if an API for that existed too, we could automate Gearset users.

    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)
  12. Schedule Release Validation

    We've run into ROW LOCK issues in the past while running unit tests during validations in production which caused some issues with external Community Users, thus as a best-practice we try to run production validations after business hours.

    I'd like to be able to schedule release validations from Gearset, or expose an endpoint that would allow me to trigger a CI validation for a release or PR.

    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. Add a date filtering mechanism on comparisons

    . Currently we can select individual dates on the dropdown list or select from a select few "Last X days". Would be a great option to be able to set something like "See changes from X to Y" or "Select since X", especially useful given we have the dropdown selection on a per minute step, so the list gets very large, very quikcly.

    For compliance checking, tracking who changes what when, periods of criticality (especially around new features coming in) or just for retrospectives.

    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. Ignore line endings in pipelines conflict resolution

    It would be useful if the pipelines conflict resolution tool ignored line endings. As at present if you have one file with LF line endings and another with CRLF it will show the whole file as different, where as that is not the case, it's just line endings. Most other devOps tools work in this way.

    There is another idea to ignore whitespace in apex comparisons - but this should also be extended to conflict resolution.

    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

    0 comments  ·  New feature  ·  Admin →
    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 Order of Steps for Data Deploys

    When configuring a data deployment, currently "Planning Deployment Steps" is the last step, but this is where I often encounter the "Error while planning deployment" because of recursion/etc. That means I need to back up through the previous 4 steps, adjust, and then go BACK through the related objects, data masking, disable rules steps before it will try again.

    The disable rules step in particular takes some time, making this a really tedious cycle to repeat.

    I understand needing the related objects step before validating the deployment, but if the order changed to:

    1. Select Objects,
    2. Select Related Objects
    3. Plan Deployment…
    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

    0 comments  ·  Data deployment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Please introduce an external ID in the background as some other products do. This would make it flawless.

    Without the external ID, your solution is time consuming and prone to troubleshooting errors.

    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

    0 comments  ·  Data deployment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Deployment pipeline view personalization

    Currently, the view in continuous integration (deployment pipeline) is sorted by ABC, which is not user friendly when there are many team members. In this case I appear last and I need to find myself in this screen.
    I suggest you to either:
    1. allow creating personal views per user, so I can see only my dev sandbox, full sandbox and production.
    2. change the scroll into a "regular" scroll, and not the current drag scroll

    4 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

    1 comment  ·  New feature  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Gearset Unit Test Monitoring ignores test methods in classes at V27 or earlier

    For older orgs, one may have Apex classes at V27 or earlier. Such classes were allowed to also include testmethods.

    Gearset's Monitoring job ignores these test methods leading to a false sense of security that one's org is "correct"

    Example class is at V24

    class Foo {
    void doStuff() {}
    static void testmethod myTest() {
    new Foo().doStuff();
    System.assert(...);
    }

    The myTest will not be run by Gearset Unit Test Monitoring. It will be run by Setup > Apex Test Execution > Foo > Run tests

    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

    0 comments  ·  Bug  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Permission set changes not displaying without drilling down

    You shouldn't have to drill in to see the changes in a permission set. I was stumped b/c it showed no difference, but in reality I had to drill down to see the difference. This is bad UI

    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)
  20. Help users Deploy Sales Cadences between orgs

    Sales Engagement for Salesforce allows users to build Sales Cadences. These seem to be record based, so being able to move these between orgs would be great.

    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

    0 comments  ·  New feature  ·  Admin →
    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