Help us improve Gearset

Welcome to the Gearset feedback forum. We love getting feedback from our users on how we can make Gearset even better.

Post your ideas and vote for others – let us know what’s important to you. We’re keen to hear about product improvements, new features, and bug fixes alike. We check this forum regularly and will keep ideas updated with their current status. If you need any further support, please contact us at team@gearset.com.

I suggest you ...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Allow deployments across managed package versions

    Gearset does not allow comparisons or deployments of custom metadata on managed packages if the versions are different. We got ourselves in a situation where a package in the sandbox was a higher beta version that we couldn't upgrade to. This required us to do all the field deployments via changsets.

    Adding a warning for deployments across managed package versions would be ideal as most changes one would deploy wouldn't necessarily cause any issues.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  2. A configuration to prevent deployment from certain Sandbox Org into Production org

    In most of Tech industry deployment lifecycle, all code or config changes are ideally pushed into production only from a FullCopy Sandbox(Commonly Known as Staging Environment).

    It would be very good to have a feature in GearSet App which if enabled shouldn't allow user deploying data from Dev/DevPro/Partial Sandbox into Production Org.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  3. Improve Bitbucket Server integration for teams with large number of project/repositories

    ideally... gearset should not be hitting https://adlm.nielsen.com/bitbucket/rest/api/1.0/repos
    first. It should hit https://adlm.nielsen.com/bitbucket/rest/api/1.0/projects to get a list of projects
    then allow the end user to select the project
    then https://adlm.nielsen.com/bitbucket/rest/api/1.0/projects/{projectKey}/repos to get a list of repos on the project the end user selects

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  4. Introduce 'ListView' as an option in 'Metadata filter' tab

    When navigating to the 'Metadata filter' tab to select filters, there are currently 122 options, however 'List View' is not one of them.
    When navigating 'Metadata Types & Components' in Workbench, 'ListView' is described independently, and I have used it previously when deploying via ANT. Therefore I would imagine there is a way to identify List Views independently of 'Custom Objects'.
    This would be a huge help with a Production monitoring job, as I do not mind if List Views are updated by certain users in Production, but currently they are flagged as differences. Basically, I want to ignore them…

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow notification for long running jobs

    Allow a for a notification to be sent when a Continuous Integration job runs longer than N minutes. Most of our jobs tend to complete in under one minute, so if a job runs longer than 30 minutes, being notified would be helpful.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  6. Warn user that clicking the "What's New in this version" will navigate away from the page they are on

    The "What's New" toast for changes in Gearset looks like it will be a popup or overlay based on the UI, but when clicked actually navigates away from the current page.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  7. Email notification selection: none, success, failed deployemnts

    In account settings allow me to choose what kind of notifications I want to receive to my email.
    [ ] Send me success deployments notifications
    [ ] Send me failed deployments notification

    No selection means do not send any notifications.

    Why? With many deployments my email is bombarded with notifications. Last two weeks 65 emails which I do not read as I see status on screen. Therefore I want to turn off those notifications.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  8. Better handle Shares on Report and Dashboard Folders in pre-validation

    during the pre-validation of a deployment, validate that the shares exist for report and dashboard folders. Currently if they do not exist in the target they fail during deployment. Only option today is to clean them up after error in source org and then redeploy. Instead, it would be useful if gearset removed them during the pre-validation.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  9. Cruise control feed for Deployment Steps

    We are planning to let our team notify and keep informed about the deployment steps status just that they can stay informed about it. These are non-Gearset users.

    Can we have a monitoring feed for Deployment steps that take place from Compare and deploy Screen 1 which contains basic deployment details (Source and Target). So as an When we progress with the deployment steps, it will keep it updated. Similar what you have for Unit Test monitoring feed. (Test monitoring Cruise Control feed)

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  10. She the commit message with the Commit ID on the CI History Screen

    The CI Job History Screen would be much more useful for me if it was able to show the commit message on the commit that triggered the CSI alongside the source commit ID.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow Downloading of git diff for Comparison

    It can be difficult to evaluate the scope of changes by clicking in the Comparison view on one metadata element at a time to see the differences. We would much prefer to be able to download a git diff and examine the delta as a cohesive changeset.

    The user should be able to download the contents of the currently selected tab (All Changes, New Changes, or Selected Changes) in the format of a git unified diff. The user can then use the software of their choice to view the diff.

    This will also enable more advanced workflows, as git diffs…

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  12. Suppress irrelevant Suggested Fixes when deploying to git

    The problem analysis comes up with a number of Suggested Fixes which may make sense for improving Salesforce deployments, but which are unproductive when applied to git deployments.

    For example, the suggestion to remove TASK.WHAT_NAME, or to omit Standard Objects, will only serve to create a git repo which is an inaccurate reflection of the source org. Each time we deploy to that git repo, we will continue to have the same changes to select or omit, since the repo is missing objects and fields from the source org.

    When the deployment target is a git repo, all suggested fixes…

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  13. Suggest related metadata for selected types in filter

    Gearset provides some very useful documentation on the importance of including groups of related metadata in a filter.

    https://docs.gearset.com/metadata-deployment-guides/using-gearset-to-deploy-profiles

    It would be very helpful if the Manage Filters dialog implemented these suggestions. For example, when a Profile is included in the filter, the user should be prompted to also select Profile Password Policy, Profile Session Setting, External Data Source, Apex pages, Layouts, and Custom Objects. Otherwise, the likelihood of Gearset assembling an accurate Profile without all of the related components will be slim.

    Gearset obviously has deep knowledge of metadata semantics and dependencies. The Manage Filter page needs to reflect…

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  14. Eliminate unnecessary XML reformatting in git

    Currently, when gearset deploys XML to git, it seems to run it through a reformatter, which creates superfluous changes in git. These changes cause extremely large deltas, which are hard to read, increase the difficulty of merges and the likelihood of conflicts, and make working with any other metadata tooling (like SFDX) difficult.

    For example, here is part of a delta gearset commited for a profile.xml:
    diff --git a/force-app/main/default/profiles/Commissions.profile-meta.xml b/force-app/main/default/profiles/Commissions.profile-meta.xml
    index 8b11e6b7..3d640a50 100644
    --- a/force-app/main/default/profiles/Commissions.profile-meta.xml
    +++ b/force-app/main/default/profiles/Commissions.profile-meta.xml
    @@ -1,10 +1,27 @@
    -<?xml version="1.0" encoding="UTF-8"?>
    -<Profile xmlns="http://soap.sforce.com/2006/04/metadata">
    +<?xml version="1.0" encoding="utf-8"?><Profile xmlns="http://soap.sforce.com/2006/04/metadata">
    + <custom>true</custom>
    + <profileActionOverrides>
    + <actionName>Tab</actionName>

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

  15. custom object translation of the Product2 object

    The custom object translation of the Product2 object, specifically, is not behaving like the other custom object translations. So when I changed the label of this standard Object : Product2 (Set-up -> rename tabs and labels)
    i can't find it in Gearset. I have to make this change manuelly.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add problem analyzers to the data deployment app

    Much like the problem analyzers for metadata deployments in Gearset, it would be great if you could add a problem analysis feature for data deployments after having configured what you want to deploy.

    Some scenarios will almost certainly cause the data deployment to either totally fail or only partially deploy some of the records and skip records it can't deploy. Providing automatic fixes (e.g. choosing not to include duplicates) would improve the number of deployments that work 100% of the time.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data  ·  Flag idea as inappropriate…  ·  Admin →
  17. Clean up source/destination drop downs to be consistent across all UI elements.

    The drop down lists for picking source/destination are different in the UI.

    For example, in compare and deploy production salesforce connections are not in the list alphanumerically, they are appended to the bottom while in a clone deployment they are all listed alphanumerically.

    Just being picky, but consistency one way or another would be great.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  18. Allow deployment of unlocked packages

    At the moment, you can select "Installed package" as a metadata type to compare, and I think you can use this to install a package (without installation key).

    However, unless I'm missing them, 2nd Generation Unlocked packages don't appear in a comparison like this.

    It would be really useful to be able to deploy 2GP with Gearset because I sometimes need to make metadata changes at the same time as installing

    e.g. I'm moving some old functionality into an Unlocked package and that old code has logic in the triggers. I want to be able to delete the old triggers…

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  19. Problem analysers - to ignore the user config element

    On metadata deployments, I frequently struggle with Report Folders, Workflow Updates, and other configuration elements that have individual users assigned to them. The struggle is that individual users assigned to these config elements often do not exist in the target org. This results in the entire deployment failing, and many times, manually configuring the report, report folder, etc.

    A nice solution to this would be a new section on the Problem analysis screen that allows me to exclude the users from the config element that is being deployed.

    It is useful to call these scenarios out, because I need to…

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
  20. Give users the ability to update field/object permissions for specific profiles only

    The issue is, when promoting from one org to another and changing either Custom Object Permissions or Custom Field Permissions and if more than the profile you want has been changed, the extra profile changes get promoted anyway. So we need a way to control which profiles get applied when promoting field and object level security.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 16 17
  • Don't see your idea?

Feedback and Knowledge Base