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.

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

43 results found

  1. Page Layout Deletion Not Detected

    When I remove a page layout from my Git repository (the file and the package.xml entry) and then do a comparison to an org that it still exists in, Gearset fails to detect a deletion. It doesn't even show up in the All objects tab. It happened to me yesterday and then I just reproduced it now.

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Bug  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. The number of differences does not appear to the left of the Prev/Next buttons in XML view mode

    However, the number of differences does appear when viewing the same Apex class in APEX view mode.

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Bug  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. False positives in managed code

    When I enable comparing managed packages (e.g. when I have added a field to a managed custom object), I get lots of false positives saying that there are differences in apex code.

    On the source org, the code is show as "(hidden)"; on the target it is shown as empty. And Gearset lists this as a change.

    Obviously, I know it's not a change, but it adds a lot of clutter to the comparison view.

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Bug  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
1 3 Next →
  • Don't see your idea?

Help us improve Gearset

Categories

Feedback and Knowledge Base

(thinking…)