Eric Kintzer

My feedback

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

    Eric Kintzer shared this idea  · 
  2. 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

    An error occurred while saving the comment
    Eric Kintzer commented  · 

    If the sandbox was created from a PROD org that has Shield encryption enabled and where a tenant secret has been generated, then the sandbox will also have the proper <encrypted>...</encrypted> XML. However, for sandboxes like UAT, you might not have done this step and hence that sandbox will not have the XML. Thus, this request can be worked around by making the sandbox "features" aligned with PROD

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

    Eric Kintzer supported this idea  · 
  4. 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

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

    Eric Kintzer shared this idea  · 
  6. 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

    2 comments  ·  Help us improve Gearset » Testing  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Eric Kintzer commented  · 

    Ideal user interface would be

    1 - Drop down w/ check boxes of available Test Suites
    2 - Option to add individual classes (also via checkboxes - perhaps filtered by some pattern)

    Use cases:
    a) Changing class Foo; hence want to run Footest
    b) Changing class(es) in some subsystem defined by a test suite, e.g. "Orders"; hence run Test Suite "Orders"
    c) Changing classes that span two subsystems "Quotes" and "Orders"; hence run test suites "Quotes", "Orders"
    d) Changing classes in subsystem "Orders" plus also change to a Util class; hence run test suite "Order" + file UtilTest

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

    Eric Kintzer supported this idea  · 
  8. 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

    Eric Kintzer supported this idea  · 
  9. 45 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

    An error occurred while saving the comment
    Eric Kintzer commented  · 

    looks like I'm not the only one who has experienced the browser UI crashing and all buttons inoperative after (in my case) the Analysis Phase results screen is displayed. Auto-saving the deployment as a draft when clicking NEXT after making selections on the Compare screen would be great. These auto-saves should have life of < 24 hours

  10. 61 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

    An error occurred while saving the comment
    Eric Kintzer commented  · 

    This would be soooo helpful. We use the fflib Enterprise Architecture pattern wherein there are domain classes for each sobject, service classes (typically by sobject) and selector classes (also by sobject). Plus a common Application.cls.

    All it takes is two developers working on stories that both affect the same aforementioned Enterprise Architecture class file and it requires way too much out-of-band work to resolve merges due to timing issues between when the feature sandbox/branch was created and the current master branch.

    Since we do PRs before merging into master, the PR reviewer is apt to say "hey, you are wiping out changes I made in master". Though resolvable with GITHub merge it would be best to avoid that step before the PR is presented for review.

    Being able to selectively 'not' deploy a block of code from source to target (because target is more current) would be helpful. For us, this is typically just Apex class files but I can appreciate the point about page layouts as well

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

    Eric Kintzer shared this idea  · 
  12. 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  ·  Help us improve Gearset » Bug  ·  Flag idea as inappropriate…  ·  Admin →
    Eric Kintzer shared this idea  · 
  13. 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

    Eric Kintzer shared this idea  · 
  14. 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

    Eric Kintzer shared this idea  · 
  15. 57 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

    Eric Kintzer supported this idea  · 
  16. 89 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 comments  ·  Help us improve Gearset » New feature  ·  Flag idea as inappropriate…  ·  Admin →
    Eric Kintzer supported this idea  · 
    An error occurred while saving the comment
    Eric Kintzer commented  · 

    another good use case for this is email2case settings. In sandbox, the routing address might by sandbox-support@mycompany.com but in PROD the routing address is support@mycompany.com.

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

    1 comment  ·  Help us improve Gearset » Deployment automation  ·  Flag idea as inappropriate…  ·  Admin →
    Eric Kintzer supported this idea  · 
  18. 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

    Eric Kintzer supported this idea  · 
  19. 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

    Eric Kintzer supported this idea  · 
  20. 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

    Eric Kintzer shared this idea  · 

Feedback and Knowledge Base