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. Make fail job optional for warning PMD analyses

    As a developer leader, I don't want the job to fail if I get a warning from PMD. But I want to be notified if the code has any warning.
    I would like the failure for warnings to be optional. But always be warned that it has flaws.

    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. Add an option to ignore location changes for Flow

    Hi, when reviewing changes for flows that are being deployed, it would be great to have a toggle option to hide or alternately color location changes which are just the location of elements on the flow canvas editor.
    <locationX>1353</locationX>
    <locationY>1305</locationY>

    Sometimes there are hundreds of location changes and it obscures the important information about what else changed.

    21 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

    The "simply differences" toggle in the comparison grid now hides location changes in flows to make it easier to identify important changes. The location changes are still included when deploying changes to the flow.

  3. Prevent Deployments from Including LiveChatButton with Omni-Channel Routing

    https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_livechatbutton.htm

    LiveChatButton metadata that is routed using OmniChannel is not supported with the Metadata API and the deployment will fail.

    It would be great if Gearset had an analyzer to remove this for end-users to prevent the error.

    The following property is null for LiveChatButtons routed through Omni-Channel

    <routingType xsi:nil="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

  4. Search option when selecting a Data template

    When choosing a template in a Data deployment, an option to search all templates is needed. We will be updating/modifying/saving new templates often and a manual scroll will become inconvenient. Control F works to find a template, but a dedicated search option would be preferable

    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

  5. Select individual fields in a Data deploy

    Having the option to move up only selected fields in a Data deployment is needed. If we are required to move up all fields in each deployment, there are scenarios where our work will get bottlenecked in a sandbox on the way to production and at that point all the deployments will be identical.

    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

    Completed  ·  1 comment  ·  Data deployment  ·  Admin →
  6. Allow renaming of data deployment templates.

    It would be very useful to be able to see the details behind data deployment templates and manage / rename them

    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

  7. Ability to activate / deactivate Flows / Processes as part of the meta data and/or data deployment process

    It should be possible to have gearset to deactivate flows and/or processes based on a selection. And to roll-back afterwards. Similar to what has been created here: https://sfswitch.herokuapp.com/

    10 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

    Hi, thank you for voting on this UserVoice. 

    Flows can now be deactivated in Gearset alongside validation rules and triggers before data deployments. 

    Click the View and disable rules... button in the bottom-right of the pre-deployment summary page (next to DEPLOY DATA) to prepare a special metadata comparison.

    To deactivate a flow, simply select & deploy its corresponding flow definition.

    https://docs.gearset.com/en/articles/4536761-disabling-validation-rules-triggers-and-flows

  8. Default option for the deployment component list for JIRA issues

    I really like the feature to add a deployment component list to a JIRA ticket. I would like to have the ability to default this ON.
    It is currently defaulted to OFF.

    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 →
  9. CI Job notification email should report the actual errors directly instead of linking to CI Dashboard.

    This potentially can help the team to collaborate on the errors directly on Teams messages.

    For example, at present, the MS team notification says [A continuous integration validation job failed for validation job for PR # xx], but doesn't say which CI job name or what the validation/deployment error was.

    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. Validation job ownership should be transferred

    Good to have capabilities to transfer ownership of validation job to other member in the team so as if one person is on vacation then there should be easy way to transfer ownership of validation job to other member so as if required - Adjustment can be done to CI jobs.

    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 →
  11. Retain source control branch selection when cancelling a comparison

    If you click "compare now" and then click "cancel" before it finishes, the "compare metadata" screen retains your selection for orgs, but does not retain the branch selection for source control.

    It defaults to the first branch by alphabetical order versus what I selected before I cancelled. This can cause confusion for users who do not notice.

    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 →
  12. Ability to lockdown access to delete Deployment history

    It'd be nice if there was a way for admins to restrict access for devs/other users when it comes to deleting items from deployment history. The use case here is when a sprint is done and we're promoting changes from QA to UAT, it'd be nice to select all the sprint packages and combine them from deployment history so a user doesn't have to go through each change at a time. Providing full access to everyone opens the possibility for them to delete a package that should've been bundled with other packages on the promotion to UAT.

    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

  13. Add a search function to the Monitoring > Unit Tests

    Add a search function to the Monitoring > Unit Test page to quickly find a specific Test outcome

    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 →
  14. Exclude LWC Jest files from validation and deployment

    We introduced LWC - Jest tests for our project, which seems to cause validation errors with Gearset.

    As per Salesforce recommendations it is recommended to keep jest tests only locally and in VCS and avoid trying to push them to SF as they would cause validation errors.

    Is there an forward path that allows us to tell Gearset to exclude LWC - Jest files from validation/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

  15. ci owner

    Allow CI jobs to be reassigned to new owners. Or allow for out of office functionality when CI Owner is out of office.

    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

  16. Change default sort order of Saved Comparison Pairs to use 'Friendly Name' (or last used sort column)

    The new Saved Comparison Pairs feature is great! However, the page appears to load connections in a seemingly 'random' order on each use.

    Confirmed with Gearset Support the default sort order is by create date of each connection pair. However, if feature is used with multiple connection pairs spanning multiple individual instances this requires manual re-sorting of connections every time page is loaded if you want to view pairs logically by naming convention (e.g. Alpha 1->2, Alpha 2->3, Bravo 1-> 2 , Bravo 2 -> 3 etc.) or something other than system create date.

    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. Include more details in webhook notifications

    It would be great if webhook would include, at least, the same information as email notifications. For example, Unit Testing job notifications via email contains the details about the unit tests that failed; however, webhook notification don't. We wanted to use webhooks to get notifications in MS Teams but without the same details, it's not that useful.

    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

  18. Restore/export certain fields on objects

    We (the user) would like to be able to restore data, but only select certain fields to be restored.

    Usecase:
    A business user triggers some automation that modifies a field or specific fields on a large number of records that should not have been modified. In the meantime, other fields may have been modified that were correctly modified. We would want to restore a set of records from a specific backup, but only the specific fields that should not have been modified.

    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

    0 comments  ·  Data backup  ·  Admin →
  19. Add "Show selected" button to the Custom Filter editor

    This button needs to be in the type and items columns. This way the developer will see the already selected components and be able to check faster if everything required is selected

    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

  20. Option to group and show all selected items while creating new custom filters

    Option to group and show all selected items while creating new custom filters

    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

  • Don't see your idea?

Feedback and Knowledge Base