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

1429 results found

  1. Scroll to top of category, when switch between All Items, Changed Items etc

    Just a user preference item – when you switch tabs (ex: New Objects to Deleted Objects), it doesn’t place you at the top of the window.

    So if I scroll down through all the New Objects and then switch tabs to the Deleted Objects, it just places me in the same relative location as I was in the New Objects tab.

    It would be nice to have it reset to the top of each window when I switch tabs.

    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. When migrating ReportFolders, either remove running user or let me map users between Sandboxes/environments

    When migrating ReportFolders, either remove running user or let me map users between Sandboxes/environments

    The SharedTo User doesn't exist in the target org causing my deployment to fail.

    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. New commits pushed during PR validation aren’t picked up until manual re-run

    In Gearset Pipelines, if a PR validation is already in progress and a new commit is pushed to the same feature branch, Gearset does not automatically trigger a follow-up validation for the latest commit after the current run completes. This leaves GitHub showing “checks not triggered yet” for the newest commit until we manually re-run validation.

    Expected behavior:

    When a new commit is pushed while validation is running, Gearset should automatically schedule/trigger another validation after the current run finishes (or cancel + restart, depending on design), so the latest commit is always validated without manual intervention.

    Actual behavior:

    The in-progress…

    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  ·  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)
  4. During Data Deployments, allow us to relate records to the User using an External ID instead of the Email and Profile.Name.

    During Data Deployments, allow us to relate records to the User using an External ID instead of the Email and Profile.Name. In sandboxes, the email address is changed. It's frustrating, for me at least, to change many email addresses so I can use the current process of linking the User Email and Profile.Name. It would be much simpler to be able to use an External ID.

    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 backup  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Allow OR operator at the top-level of object data filtering

    Currently when creating field filters, we only have AND at the top level. I would like to have OR at the top level as well:

    ( Field {operator} Value )
    OR
    ( Field {operator} OtherValue AND OtherField {operator} OtherFieldValue )

    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)
  6. 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)
  7. Change the build view in Bitbucket Pull Requests

    In the Pull Requests build checks summary on bitbucket, I’d like the view to only display builds that are failing for the current pull request. Right now it shows what is failing for the repo at large.

    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. Syncing Clayton Code Review Findings

    Having an easy way to dismiss Clayton findings directly in Bitbucket—and have that dismissal sync back to Clayton’s code reviews—would be extremely helpful.

    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. Receive Email Notifications for Backup Job's Successful Backups and Text Message Notifications for Failed Backups

    I would like to get an email for every run our backup job does, but I would like a text message if the backup job fails.

    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 backup  ·  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. 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)
  11. Delete configuration data records

    Gearset currently does not allow deleting configuration data records.
    For example, in advanced approvals, you cannot delete an approval condition. There are workarounds but those records that can't be deleted are just tech debt.

    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)
  12. How Wiki Page Creation Services Ensure Notability Compliance

    One of the biggest challenges in publishing a wiki page is meeting strict notability guidelines. Professional wiki page creation services begin by conducting in-depth research to determine whether a subject has sufficient coverage in reliable, independent sources. They gather credible references from reputable media outlets, journals, and publications to establish authenticity. These services also ensure that content remains neutral, factual, and free from promotional language, which is essential for approval. Proper citation formatting and adherence to editorial standards further strengthen the page’s credibility. In some cases, providers also offer a Wiki page translation service to maintain consistency and compliance across…

    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)
  13. 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)
  14. Add the ability to lock down Releases in Pipelines

    My team has a release cutoff of Thursday EOD, we've recently begun exploring scheduling our releases to begin at 5:00 PM on Friday, and we had slight concerns that other coworkers may add items to the release after the cut off since it isn't being manually monitored anymore. I would like to add the ability to prevent additional items from being added to releases in Pipelines after a certain day, perhaps add it to the same section to schedule the release.

    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. Add a button or option to run an ad hoc "Policy preview" for archiving jobs

    When an archiving job is first created, the "Policy Preview" is run. This shows the records that the policy will find and archive, once the job is actually initiated for the first time. After the job is run for the first time, there is no longer an option to run a "preview". It would be helpful to be able to run a preview at any time in order to see what the policy will archive the next time it is run.

    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)
  16. AI PR Descriptions With Custom PR Template

    Using the AI PR descriptions and the 'Summarize changes' features needs to be extended to include the use of PR templates pulled from VCS.

    Currently, you can only use the 'Summarize changes' without using a custom PR template. The AI output is helpful but using any of the suggested content has to be copy and pasted into your PR template. Instead, it would be more useful if the suggested content (##What has changed?specifically) can be injected into the use of an existing PR template.

    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)
  17. Exclude inactive flows from metadata deployment easily

    We often have flows that are in an org but inactive that we don't want to include in our deployment. It would be nice if we could filter on the inactive status and exclude them - similar would be helpful for other metadata like apex triggers.

    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. Subscribe for notifications

    Would it be possible to have the option to subscribe / receive wider Gearset platform notifications or updates, please? (e.g. release updates, maintenance items, etc)? This will help ensure awareness of any recommended items which require attention. Thanks!

    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. Extend permission to enable ArchiveViewer connector for users

    Enabling ArchiveViewer connector is limited to only the Archive Owner. Ownership can be transferred but maintaining Archive Owner is crucial to organization structure and should not be changed. However, the ability to enable ArchiveViewer connector for Archives should be extendable to other users as Archive Owners are usually Platform Owners/Management that does not perform deployment/development work.

    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. automagically refresh the list of salesforce connections when I add a new one.

    When I am choosing a source or destination salesforce organization, I can add a new connection, but when I save it and return to the choice page the new connection isn't listed in the drop-down unless I refresh the page. Seems to me that you could trigger a background refresh on save so that the drop-down is auto-updated.

    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