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

347 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

    0 comments  ·  New feature  ·  Admin →
  2. Bitbucket pull request add Default Reviewers

    When using the "Create Pull Request" link on the deployment screen, please add the "Default Reviewers" to the BitBucket pull request.

    Currently we have to edit each pull request and add the reviewers manually.

    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

  3. New Analyzer to prevent endpointURL changes for Outbound Messages in Sandboxes

    A major pain point and blocker to use automated CI jobs is that we cannot include workflow rules because we have outbound messages set up to specific test endpoints per sandbox/environment. As the workflow metadata type allows us no ability to filter by workflow rule name (it's by object), this means we have no option but to manually run the comparison and deployments for each of our sandboxes.

    It'd be great to add a problem analyzer to suggest not changing the endpointURL field on outbound messages when the target is a Sandbox. This way, you can deselect it manually when…

    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

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

  5. Select the fields to deploy during a data deployment

    Hi we use the data deployment feature is it possible to only select some fields to deploy data from one org to another and not always all the fields on an object.

    19 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

  6. Allow "View Errors" in CI Job History page to be opened in a new tab

    It would be great if the button allowed to be opened in a new tab (essentially allow buttons and links to act like regular HTML elements that allow opening in a new tab via Cmd/Ctrl+click or via right click)

    Example right clicking the "View Errors" shows no open to open in a new tab https://d.pr/i/m5CNIG

    Right clicking "View comparison" allows for it https://d.pr/i/WpCfFF

    This is similar to https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/35538631-make-clone-package-openable-in-a-new-tab

    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

    Completed  ·  0 comments  ·  New feature  ·  Admin →
  7. Rerun Github validation on a PR without a new commit

    When a CI job is set to run on a PR creation, if the source destination is missing something that the deploy requires, it will fail. To solve this, we must go to the source destination, make settings changes, and then make an empty commit to the pull request to re-run the CI.

    It would be nice for there to be a link or button in Gearset to rerun the CI and update the Pull Request that the validation was successful.

    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

    In the ‘continuous integration dashboard’ in Gearset, for ‘validate pull request’ jobs, there is a ‘run now’ play button to run the job manually. You can therefore update the target and then re-run the PR validation without needing an additional commit.

    To be able to run the ‘validate pull request’ job manually, you need to have permission to run the parent CI job manually (e.g. be the job owner).

  8. Require Jira Ticket Before Validation or Deployment

    We would like the ability to make the "Jira updates" section required (i.e. ticket selected) prior to validation or deployment.

    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

    You can now require team members to link a Jira ticket before manual deployments and validations. 

    Simply, navigate to My Account -> Deployment Settings and enable the 'Require Jira Tickets' option. 

  9. Include a Comparison for a Permission Set Group's Muting Permission Set

    Include a Comparison for a Permission Set Group's Muting Permission Set. Currently, you can deploy a Permission Set and/or a Permission Set Group. However, if that Permission Set Group contains a muting permission set, Gearset doesn't pull the data. Here is a link to the SF guide on the muting permission set: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_mutingpermissionset.htm?search_text=muting%20permission%20sets

    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

  10. More granular control over CI job schedules

    Currently, a CI job that deploys from a Salesforce Org to another org or source control can only be scheduled to run at 4 hours intervals. Additionally, there is no mechanism of specifying when these jobs will run - instead, the job is scheduled randomly within the first 4 hours it was created and every 4 hours after that point.

    Providing a smaller interval (ex. every 1hr) and/or more granular control over the job execution time seems like a common sense enhancement.

    14 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

  11. Add a way to "Save" or "Save As" updated filters when in the Refresh Comparison window (like you can in the Compare and Deploy window)

    When in the Refresh Comparison window, it seems there's no way to "Save" or "Save As" the updated filters. Looks like you can only access that feature via Manage Custom Filters from the Compare and Deploy screen

    Any chance we could get that added? It would be super useful!

    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

  12. 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  ·  Data backup  ·  Admin →
  13. Enable Gearset login from corporate SSO solution

    an additional layer of security and convenience would be to enable Gearset login (that is, login to Gearset) to be done from an enterprise's SSO solution. We use Duo but Okta and others should be supported.

    Just like we can login to Salesforce from our enterprise's SSO , we should be able to login to related apps in our suite of enterprise tools via SSO

    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

    0 comments  ·  New feature  ·  Admin →
  14. Ability to create Pull Requests for AWS CodeCommit

    Gearset can create Pull Requests for many of the source control systems that it integrates with, but not AWS CodeCommit.

    As AWS users, it would be very useful to use to have this ability so that we didn't need to switch systems to create Pull Requests.

    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

  15. Functionality to Data Deploy Active Orders

    Salesforce doesn't support the creation or update or standard Order records with a Status Category of Active. This means Gearset is unable to data deploy any active orders. It would be very useful if there was an option for Gearset to temporarily set active orders to a draft status for the deployment or the Order Records and related Order Records, and then set the status back to Active for the final step.

    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

  16. Cancel a running data deployment

    Currently I am trying to copy data from production into a sandbox and mask them, but I forgot to adjust the amount of records to create. Now Gearset tries to create thousands of records for each and also mask them with a lot of fields included. I would like to abort the process but don't see any option because this huge amount of data and background services consumes a lot of time and compute resources. Also, I can’t estimate how much time is still left to complete the data deployment. Also, just to see is also a huge improvement but…

    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

  17. Add support for Currency and Percent fields to be masked during a data deployment

    We have some custom objects that hold financial data so masking currency and Percent fields will help when doing data deployments

    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

    Completed  ·  1 comment  ·  Data deployment  ·  Admin →
  18. Support flow deletion at V44+

    if the target flow is deactivated; and all prior versions are deleted, you can't delete the last remaining flow version in the target org. The error you get is "Insufficient access rights on cross-reference id".

    Copado provides a solution (https://docs.copado.com/article/8l069zes9f-destructive-changes-in-copado-doesn-t-support-flow-and-process-builder) wherein the user can specify the contents of the destructive-changes.xml file (enumerating the versions to delete) but Gearset has no way to inject such a file into a compare/deploy (esp a CI deploy)

    with SFDC pushing more and more dev into Lightning Flow, deletions are inevitable in many orgs as things get refactored/renamed

    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  ·  New feature  ·  Admin →
  19. Add friendly Name to Deployment detail and be able to add/edit from that page

    It'd be great to see the "Friendly Name" in the Deployment Summary page.

    e.g. https://app.gearset.com/finished?deploymentId=XXXXXXXXX

    And to be able to add/edit the Friendly Name on that page, same as it can be done in the Deployment Summary.

    Our use case: We audit all our deployments to make sure they have a name. It would be very helpful to be able to send a Deployment Summary link to a user to tell him to add a name if it's missing.

    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

    Completed  ·  0 comments  ·  New feature  ·  Admin →
  20. Remove botUser from Einstein Bot metadata

    The metadata for EInstein Bots includes a tag called "botUser" that contains the username of the user you've specified to run the bot as. Because it contains a username, the deployment fails unless you have the exact same username in both environments.

    My current workaround is to deactivate the bot, remove the running user (which removes the botUser tag), deploy, then reset the changes that I made.

    Can we get a problem analyser that will detect and remove this botUser tag so that the deployment will complete?

    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

  • Don't see your idea?

Feedback and Knowledge Base