Skip to content

Kenny

My feedback

8 results found

  1. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Kenny supported this idea  · 
  2. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Kenny supported this idea  · 
  3. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Kenny commented  · 

    Yes! This would be a huge timesaver! I'd rename the title "Option to ignore Package Versions during comparison" Most of the time, our deployment does not depend on the package versions so, being able to ignore is helpful.

    When things like NPSP get upgraded, suddenly, I have 95 differences in my comparison! these diffs won't affect functionality at all and require a lot of manual intervention to ignore, instead of enabling better CI automation.

    Kenny supported this idea  · 
  4. 11 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Kenny commented  · 

    Since Test Suites can be managed via source code, this would also allow the ability to determine flexible test runs during deployment instead of needing to manually define them as part of the gearset CI job

    Kenny supported this idea  · 
  5. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Kenny commented  · 
    Kenny supported this idea  · 
  6. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Kenny shared this idea  · 
  7. 29 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Kenny commented  · 

    Yes, Please! These are supported natively in SF API now as per: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_territory.htm

    Please add this component type to your list!

    Thanks!

    Kenny supported this idea  · 
  8. 69 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Kenny supported this idea  · 

Feedback and Knowledge Base