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

369 results found

  1. Select more than one item at the same time

    On "Items to include/exclude for Custom application" view, it would be really nice if we could select more than one item at the same time, using SHIFT shortcut.
    When clicking on "Named Item", and if you want to select from the 49th line to 63th line for example, and to avoid to select manually 15 lines with 15 clicks.
    We could just select the 49th line, and with SHIFT, click on the 63th line to select them.
    Thx

    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

    1 comment  ·  New feature  ·  Admin →
  2. Upgrade to PMD 6.17.0

    Current version is 6.11.0.

    We should be consistent with newer version. We are having issues with older version in Gearset regarding the ApexDoc rule.

    The issue was described and discussed with Valerio in the chat.

    Thanks

    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

  3. Deployment screen to show which components were selected vs included

    When you get to the summary page, often times you will be deploying with the need for sub-components to be included in the package despite them being actual changes.

    When you're selecting those items inside the comparison page, it would be helpful to see that total be reflected in the deployment summary page. So if you picked 50 items to deploy but it needed an additional 1,000 components (despite them having No Difference) then we should see those breakdowns on the Deployment Summary

    Gearset soft alrt message "Some components with difference type of No difference have been added to 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

  4. Refresh specific item in comparison through context menu

    It would be great to refresh a specific item within a comparison that I know has changed since the last comparison.

    107 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

    Gearset now supports:

    - Refreshing a single item - available either from the context menu (by right-clicking an item in the comparison results table) or by using the "Refresh item" button in the XML preview window

    - Refreshing selected items - available from the context menu once one or more items are selected


    Thank you for commenting on and upvoting this request. We hope this new Gearset feature is going to speed up your workflow!

    If anyone has feedback or suggestions, please contact us via the in-app widget.

  5. Allow multiple Team owners to Connect to the bitbucket server through OAuth instead of creating a new link every time with in same Org

    With in an org if we have multiple owners working as multiple teams, Gearset should be able to allow other owners to connect to the same Biibucket server through OAuth, instead of creating a new link every time.

    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

  6. Stop Reordering Package.xml

    We would like to keep our package.xml file in alphabetical/lexicographical order by the <type> element. Gearset appears to change the order so that datatypes that include all <members> elements (i.e. use an asterisk) are placed at the bottom of the file. This inconsistent sort order makes datatypes harder to find when viewing or amending the file.

    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

  7. Deploy permissions for Lightning Record Pages

    provide a means of deploying the profile/recordtype/app permissions for lightning record pages without having to deploy the whole app.

    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

    3 comments  ·  New feature  ·  Admin →
  8. Dependency Enhancement for App Menu metadata

    Currently, when we compare App Menu metadata, the "Depends On" tree is empty, even though it definitely has dependencies on connectedApps and customApplications.

    Please add dependency analysis for App Menu metadata,

    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

  9. Include support for new metadata type 'PermissionSetGroup' (Winter '20)

    As feature has moved from pilot to beta in Winter '20 release, looking for support in differencing and deploying the new 'PermissionSetGroup' metadata type.

    20 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 deploy permission set groups in Gearset!

    PermissionSetGroup isn’t included in the default metadata filter, so you’ll need to include it in any comparison filters you’re using.

    Please get in touch if you spot any problems.

    Thanks,
    Tom

  10. Add link to test results in Microsoft Teams

    Please add a link to the test results as part of the notifications sent to Microsoft Teams. The integration with Slack already includes the link so it would be very helpful to have a similar integration in Microsoft Teams.

    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

  11. User Last loggged in and User Usage

    It would be great to see when a team member last logged in on the user account management page. It would also be great to see like a report or extension on the user page where we can see user usage information. Like number of compares, deployments, etc.. may when last compare was done.

    23 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. Separate Filters for CI Jobs to reflect filter edits

    Currently, if you have a saved filter being used in CI jobs, any edits/changes to that filter are not reflected in the CI jobs that use said filter.

    It'd be great if we could isolate filters for CI jobs so that we could edit CI job filters that would then affect every CI job they're being used with instead of having to edit every job and re-select the filter whenever a change is needed.

    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

    2 comments  ·  New feature  ·  Admin →
  13. CI dashboard: Show commitId when job is in flight; Show queued commitIds

    On CI Dashboard page, a CI job in flight (deploying/validating) should show the commitId that triggered it (if any) PLUS show all pending CI jobs.

    Reason: If two developers are sequentially merging to a shared branch tied to the CI org (and webhook is setup to run immediately), then the first developer's merge starts CI job 1 while the second developer's job is queued.

    Yet, from the CI job page there is no way to even tell which commit to the branch is running (so as to clue the developer that his/her job is running vs queued. Commit message would…

    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

    Thanks for the suggestion! When a CI job is running from git, the commit hash and the commit message is now visible for all git providers. In addition, for GitHub, Gitlab and BitBucket sources, a link to go to the relevant commit will be displayed.

  14. 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,

    You’ll now see the option to create a draft pull request in GitHub, if your repository supports draft pull requests.

    Draft pull requests are available in public repositories with GitHub Free, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see https://help.github.com/en/articles/about-pull-requests#draft-pull-requests.

  15. Add Prompt metadata type

    Please add the new Prompt metadata type

    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. There should be an option to schedule unit test jobs weekly in Gearset

    Hi Gearset,
    I would suggest you to provide an extra option where we can select weekly ,daily or monthly schedule jobs in Unit Testing Jobs.

    Thank you,

    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 →
  17. List the unit tests failures in the email notification being sent out

    Currently, when the unit test job fails, we can view the test history and results by going to the web page. However, we would like to view the summary of unit tests that failed in the email notification that is being sent out.

    9 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  ·  2 comments  ·  Testing  ·  Admin →
  18. Add an option to disable the "repository sanitizer"

    The "repository sanitizer" performs unsolicited/silently changes which confuse users and generate issues. For instance, if you have Apex class permissions in profiles for classes which are part of a managed package and are not present in the repository, this sanitizer will modify the permissions to false which is obviously a disaster, (and the changes can happen any moment, while users are trying to deploy something completely unrelated hence the confusion).

    We know the solution is to have the classes also in the repository but for managed packages that's unnecessary extra work since then we need to be updating them every…

    12 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

  19. Optimize "Refresh Comparison" to only pull metadata that has been changed since the last comparison

    Currently, clicking Refresh Comparison does not optimize the comparison in any way, it just allows you to skip selecting some of the configuration steps from running a new comparison.

    This means that it takes the same amount of time actually comparing the orgs.

    It would be nice if on clicking of "refresh comparison" the logic didn't run a full compare and instead just looked at metadata that had been changed since the last compare in order to reduce the comparison time.

    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

    Hi everyone

    We have now shipped the three key improvements to refreshing a comparison. 

    You are now able to:

    • refresh a single item (right-click an item in the grid or use Refresh Item button in the Diff viewer)
    • refreshing selected items (right-click a selected item in the grid)
    • refresh only additional types in the filter (via Refresh comparison -> Filter dialog)


    We hope these enhancements will greatly reduce the comparison time for you. 

  20. Report CI validation/deployment status to source control

    When a CI job is triggered by a commit to source control, please update the source control system with the result of the build - so that e.g. with Bitbucket we could see the build result from pull requests as at https://confluence.atlassian.com/bitbucket/check-build-status-in-a-pull-request-945541505.html

    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 2 5 7 9 18 19
  • Don't see your idea?

Feedback and Knowledge Base