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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Deployment count in the blue banner wrong for old deployments

    When viewing old/past deployment details, that old deployment shows me the big blue banner saying that ---this--- was our {insert total number of deployments ever}th deployment no matter which old deployment I'm viewing.

    This confused me a bit because I wanted to view our say 5th deployment ever so expected the number to say this was our 5th deployment, and I ended up closing the details browser tab twice thinking I pressed the wrong button to view the latest deployment. Yeah I could have looked at the tiny timestamp somewhere on that details view, but this large blue banner/counter just…

    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 →
  2. Make "Clone package" openable in a new tab

    In Deployment history, there are two buttons I use the "view details" which I can open in a new tab without leaving the list of deployments, and the "clone package" which I can't open in a new tab. I can workaround it easily (duplicate tabs, or first view details then clone from there), but it was disappointing that I have to.

    I needed to re-deploy say 10 deployments into a different sandbox and so the clone package feature was amazingly useful, but this little nag prevented me from entering the blissful nirvana of wielding the perfect tool for the job…

    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 →
  3. Provide browser notification when refresh draft deployment completes

    It is cool that Compare tells you via a desktop notification / browser tab change when the comparison is done. The notification feature should be extended to Draft Deployment - Refresh Comparison as this can take some time as well

    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

  4. 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  ·  Team and account management  ·  Flag idea as inappropriate…  ·  Admin →
  5. Pending Validation - Copy from Pending Deployment

    Similar to "Pending Deployments" It would be nice to see pending validations. We have several users in gearset, so if we are trying to validate something while someone has already initiated a validation, we receive the error that set up has been locked. So prior to validating a package, it would be great to check if anyone is in the process.

    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 →
  6. Allow changing of public group membership via Gearset

    Right now, the only way to edit a group's membership is via the API (users or groups only) or the UI (additionally allows roles, roles and internal subordinates, etc.). Please allow the editing of group membership of public groups.

    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 →
  7. Better Targeted Static Code Analysis Feedback Surpression

    Currently, if I want to suppress errors from static analysis, the suppression seems to be all-or-none at the class level.

    I would prefer to suppress only the specific errors when they happen.
    (e.g. in the method or in the line.)

    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

    Hi!

    Our static code analysis is built on PMD. Currently, the only error suppression that works with Apex code in PMD is the `@SuppressWarnings` annotation. (This was introduced for Apex in PMD version 6.0.0). As you say, you can suppress all rules, or specific rules, at the class level, but can’t make more fine grained suppressions, unfortunately.

    There are other methods of suppressing errors within PMD for other languages, but these don’t currently work with Apex. We’ll keep an eye on future versions of PMD to see if they introduce new methods of suppressing warnings for Apex code.

  8. New analyzer check - changing field type on a custom metadata type (mdt) field

    Turns out the following can't be done:

    Change the type of a xxxmdt.Fooc (e.g. from Number to Text)

    While the Force.com UI doesn't let you do this directly, you can do indirectly by deleting the Foo__c, then adding it back with a new field type. Your sandbox is a-ok with this

    But if you try to deploy, SFDC won't let you deploy and you get this error: "This field is on an object that doesn’t support field type conversion."

    Gearset Analyzer could check this by comparing source to target and give you a nice warning. Would save the…

    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  ·  Problem analysis and deployment failures  ·  Flag idea as inappropriate…  ·  Admin →
  9. Show rows that have no set "Changed On" date when applying a date filter.

    Currently the moment you deselect a single specific date, all blank dates are also filtered out.

    I would expect only the items with the given date be removed from the list.

    This has become apparent now that the sort order of dates in the pulldown bug has been fixed.

    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  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow PMD to be configured by uploading a xml file with rules

    We use PMD locally in our IDEs to analyse during development, and the whole team shares a rule file in xml. It excludes the ones we don't like and configures other rules.

    We can configure Gearset to do the same through the UI, but I'd rather be able to just upload the file, then I will know they are the same set of rules.

    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

  11. show which deployment each metadata was a part of when doing a bulk clone.

    When doing a bulk clone, each metadata should show what previous deployment it was a part of as to allow us to verify that the bulk clone worked. Another use case is that it would allow us to find a deployment we know has changed and be able to remove or change the metadata quickly.

    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  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  Admin →
  12. Extend the ability to add and delete in a single deployment to all metadata types

    We just came across an issue in which we were deploying an HTML email template that had been moved from one folder to another in the source environment.

    When deploying, only the delete happened on the first deploy. I needed to do a second deploy to handle the addition.

    While probably not a common case, it's certainly important as the initial deployment reports that the addition was successful.

    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 →
  13. Clone deployment with favorite source:target combos

    We use Clone from Deployment History quite often. A typical use case would be:

    Deploy from feat org F to branch
    Do PR & merge to /master
    .. CI runs
    Upon successful CI
    Clone deployment with source = master and target = QA org
    Upon successful UAT
    Clone deployment with source = master and target = PROD org

    Rather than having to re-enter on the Clone dialog the source and targets, since they are always the same, it would be nice to "favorite" sources and targets (assigning a favorite name) and then reusing those favorite names on the Clone dialog

    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 →
  14. CI Validation Job report should show version of metadata API used for CI

    A nice-to-have UX feature would be to echo the metadata API version used in the CI Job on the Validation Errors report (or any CI report). This can be used to aid in troubleshooting

    This is especially helpful when a source or target org is using a Preview sandbox

    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  ·  Monitoring and reporting  ·  Flag idea as inappropriate…  ·  Admin →
  15. Optimize comparison list view

    The comparison view contains a list view in a scrollable area with an line item for every metadata item in the comparison. Depending on the comparison, this list can be exorbitantly long (10k+ lines). Displaying this many elements on screen is extremely inefficient, and causes browsers to lock up when selecting the "check all" check box (because it results in thousands of incremental manipulations in the DOM). This issue also causes mobile browsers to crash when more than a thousand or so items show in the comparison results.

    There is a common pattern for handling long lists like this, in…

    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

    1 comment  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  16. More Details for Open Draft Deployments: Show Name & Refresh Date

    When you open a Draft Deployment it would be great to see its name on the deployment page as well as its refresh date. I understand that when you open a draft deployment you're seeing a snapshot from when it was created or refreshed.

    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 →
  17. integrate with Atlassian Stride for notifications

    Gearset's ability to send notifications to Slack is great. I'd like a similar ability to send notifications to Atlassian's Slack alternative - Stride.

    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

  18. Zapier Integration

    An integration with Zapier will allow more customizations options for how we can integrate with other tools, such as Manuscript (fka FogBugz).

    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

  19. Access to Jira custom fields

    we have a custom field we use that ties to a release number. It would be great if as an additional option to selecting tickets, access this field, set the value (in this case our release number) and have gearset pull all related requests in.

    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

  20. Cache deployment inspection results

    It would be great if deployment inspection results were cached, such that the results for an identical set of metadata are available without spending the time to recheck everything.

    Use case: A comparison is performed and all changes selected. Deployment inspection is performed and recommendations are made for items to add/exclude. I select a subset of recommendations, and move forward with validation. The validation fails. The same comparison is reopened and again all metadata is selected (with the intention of selecting more of the add/export recommendations resulting from the inspection). At this point, the inspection is rerun, even though the…

    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  ·  Comparisons and difference visualization  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base