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
  1. Allow Filters to be Customised in Pipelines UI

    Currently, you can create new filters in Compare & Deploy, but when you are comparing and deploying from within the Pipelines UI on your development org, you can only select existing ones. This either means you have to get your team to go into standard Compare & Deploy to set up specific filters first, or they always have to select the filter that includes everything.

    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  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Change language to focus less on Source Controls and be more user friendly

    Gearset is great for non-technical users or those that find Source Control daunting. However, the terminology used in Source Control has leaked over to Gearset, and I think this detracts from the useful aspects of it, and at times just makes it feel like an extension of Source Control.
    e.g. "Create Pull Request" in the Pipeline UI should be labelled something more friendly like "Request Feature 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  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Hide the "Create Pull Request" button on Deployment Success Screen

    Currently, we are setting our team up to use Pipelines, which has the benefit of guiding users down the pipeline in the right way (they can't create a pull request from a qa branch straight to main without going to uat for example). However, when they perform a commit from an org to a feature branch, the Deployment Success (commit success) screen has a button that allows them to create a Pull Request directly to any branch that they want. There should be an option to hide this from users, especially given the benefit of only being able to move…

    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  ·  Flag idea as inappropriate…  ·  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. support blank values and/or regex in the "Find What" field on Environment Variables

    ...support blank values and/or regex in the "Find What" field on Environment Variables.

    I would like to replace the value in a field on a Custom Metadata Type with an environment specific value, regardless as to what the value is in the source file. Currently I need to specify an specific value in the source to be replaced.

    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  ·  Flag idea as inappropriate…  ·  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 field level granularity in CI Jobs

    Would like the possibly to set up a CI job that only syncs a sub-set of fields on a custom object. For example, we have an org to org sync where we want to update picklist fields but not autonumber fields. Currently we are running this job manually twice a 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

    0 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  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. Enable admin visibility into a Gearset team member's shared orgs

    As a Salesforce implementation partner (SI) I have a lot of organizations to manage, well over 50. Each time a new org is added, I can go through and add all the users to that org, but whenever a new person is added to my team, I have to go through each connection and add that user to the list.

    As the owner, I would also like to be able to see all the shared orgs inside my account, so I can centrally manage them, rather than just the ones that team members may have added.

    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  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Prevent deployed validated packages from being deployed subsequent times

    Currently, after you deploy a validated package it no longer appears under the Validated Packages menu, however, if you still have the link for the validated package and navigate to that package it doesn't give you any indication that the package has already been deployed and allows the user to click the Deploy button again, assuming they have deploy permissions on the target org connection.

    As part of our production deployment approval process, we store the link to the validated package in our external ticketing system (https://app.gearset.com/validated-package-details?deployPackageId=<package id here>). When completing the ticket, users use that link 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

    0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Send Email when a package is Validated successfully with PDF of Deployment Summary.

    We currently receive an email with deployment summary as PDF attachment after successful deployment, but we also want this feature for successful manual validation. This is help us review the validated package summary with Deployment approval teams in our 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

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  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. Allow more than one instance of Jira to be connected to.

    It would be great to have the capability to connect to more than one instance of Jira. We are switching to a different instance and we have to delete and recreated the Jira connections each time we switch instances.

    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. Allow account admins to run reports on their team's usage of Gearset.

    I am managing a Gearset account and I need to be able to know who is using Gearset and who isn't so I can more properly assign licenses.

    This might be an Enterprise feature, https://app.gearset.com/account/account-report, but really should just be something an account admin can 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  ·  Flag idea as inappropriate…  ·  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. Only notify the Pull-request creator on validation errors

    Hi team, not sure if there is a way to do that in the current setup, but I think it would be helpful to add the option to only notify the Pull-request creator/owner on the validation errors, instead of "hardcoding" the email recipients. Regards, Adrian

    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  ·  Flag idea as inappropriate…  ·  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. Allow squash merge for Github PR

    We have our GitHub PR settings set to only allow Squash and Merge for PRs because we want a clean history on the long-lived branches. It seems Gearset doesn't support this, when I attempt to promote it issues an error. This should be configurable or should detect this automatically from the settings.

    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. Pull Request From Deployment History

    Making a pull request via Gearset is only available from the Compare & Deploy Flow.

    I'd the link to make a pull request available from deployment history so that users can make the pull request to the various Git/Salesforce environments.

    Currently, I am telling my users to note the deployment id for their comparison and hit the link. This appears to work, but isn't user friendly.

    https://app.gearset.com/finished?deploymentId={deploymentId}&notify=true

    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  ·  Flag idea as inappropriate…  ·  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. Show me where the Salesforce Release Changes are in the metadata files.

    As a gearset user, I want a guide to the location of metadata components created by Salesforce in each new release so that I don't have to guess and look for the metadata 3 times per year when Salesforce publishes changes to their platform.
    Please user your business relationships with product owners at Salesforce to submit this story idea on behalf of clients everywhere.
    For example, today I was looking for metadata, if any, created by enabling permission set expiration dates in my sandbox. This won't be availabe in production until release on 10/7 but I was curious if I…

    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  ·  Flag idea as inappropriate…  ·  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. enable UTAM

    In the same way you enable Jest tests to run during deployment like that:
    https://docs.gearset.com/en/articles/5204895-pilot-feature-source-control-setup-for-lwc-test-runs
    We would need to run UTAM tests:
    https://utam.dev/guide/introduction

    Those are stored in utam folder and as sucha re not deployed to Salesforce org but rather "ran" by the test system.
    UTAM is very similar to Jest but do a simulated browser test (including integrated services and login of users) that covers full scenario and several pages. It's possible by using Chromedriver through WebdriverIO. All these are nodejs libraries used by UTAM.

    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. Precision Deployments (available for Layouts) for all the meta data

    Precision Deployments for Layout is a great improvement, it would be great to have the same feature for other meta data, particularely for : Fields picklists, global value sets, List Views, Reports, Profiles, Permission Sets and why not Lightning Pages, now that the Dynamic Form is available for Acc, Contacts & Opp

    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

    Planned  ·  3 comments  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  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. Have the Jira ticket which was selected at the point of the commit stay with the PR in Pipelines

    At the moment when you select a Jira ticket at the point of commiting to a branch, you are able to track that actionback into Jira.

    However when a PR is opened from that feature branch to the next environment branch (in the Pipelines UI specifically) the Jira ticket association is lost, and has to be reattached manually.

    Workaround:

    1. Put the ticket ID in the branch name, i.e. name your branch "feature/AL-99- new-flow"
    2. Use the drop down menu provided in the Pipelines UI to re select the Jira ticket
    3. Open the PR from the Commit successful screen and tick the…
    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)
  19. Have the Jira ticket which was selected at the point of the commit stay with the PR in Pipelines

    At the moment when you select a Jira ticket at the point of commiting to a branch, you are able to track that actionback into Jira.

    However when a PR is opened from that feature branch to the next environment branch (in the Pipelines UI specifically) the Jira ticket association is lost, and has to be reattached manually.

    Workarounds:
    1. Manually add the ticket ID to the PR description, which will reassociate it
    2. Use the drop down menu provided in the Pipelines UI to re select the Jira ticket
    3. Open the PR from the Commit successful 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)
  20. Disable Jira notifications for individual CI Jobs

    We like that the Jira integration posts changes to the associated Jira ticket during a deployment, but we only want notifications for specific CI Jobs. For example we want our staging and prod deployments to post a notification in our Jira ticket, but not for other jobs such as back-deployments. Each post potentially emails Jira users and we want to limit these notifications. Currently the only work around is to remove the Jira ticket association from the PR in Gearset before promoting it, and this gets tedious if you have a lot of development orgs.

    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)
← Previous 1 3 4 5 48 49
  • Don't see your idea?

Feedback and Knowledge Base