Eric Kintzer
My feedback
-
3 votes0 comments · Help us improve Gearset » Deployment automation · Flag idea as inappropriate… · Admin →
-
3 votesPlanned · 1 comment · Help us improve Gearset » Comparisons and difference visualization · Flag idea as inappropriate… · Admin →
-
2 votes1 comment · Help us improve Gearset » Comparisons and difference visualization · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment -
5 votes
An error occurred while saving the comment This issue also occurs during validation runs in Pipelines. I'd be happy if I could a) specify the log levels (apex info, db info, etc) + b) enumeration of the failing tests so I could rerun the validation and capture just the debug logs I care about.
Turning debug logs on unconditionally for the unit test or validation jobs is not desired as they can cause the runs to exceed CPU time.
Even cleverer would be for Gearset to identify the failing tests and rerun those with pre-configured debug logging so results would be available for inspection
-
3 votesUnder review · 1 comment · Help us improve Gearset » Comparisons and difference visualization · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment this idea was written before PB was deprecated by SFDC;
-
4 votes
An error occurred while saving the comment There's another use case for this -- sometime in the future, hopefully, Gearset will enable scratch orgs to be created pre-populated with metadata AND test data. (see sfdx force:data:tree) If we can populate VCS with sample test data from a dev org then this enables the scratch orgs to be easily constructed fuly-formed and ready-to-go
-
7 votes
An error occurred while saving the comment "reminder to activate a flow" is a great idea; same for adjust custom metadata records or edit various other Settings
-
4 votes
-
9 votes0 comments · Help us improve Gearset » Comparisons and difference visualization · Flag idea as inappropriate… · Admin →
-
3 votes
-
9 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Flag idea as inappropriate… · Admin →
-
7 votes
-
9 votes0 comments · Help us improve Gearset » Monitoring and reporting · Flag idea as inappropriate… · Admin →
-
7 votes
-
10 votes0 comments · Help us improve Gearset » Comparisons and difference visualization · Flag idea as inappropriate… · Admin →
-
1 vote0 comments · Help us improve Gearset » Deployment automation · Flag idea as inappropriate… · Admin →
-
1 vote0 comments · Help us improve Gearset » Problem analysis and deployment failures · Flag idea as inappropriate… · Admin →
-
7 votes0 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Flag idea as inappropriate… · Admin →
-
2 votes0 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Flag idea as inappropriate… · Admin →
-
2 votes0 comments · Help us improve Gearset » Monitoring and reporting · Flag idea as inappropriate… · Admin →
PermComparator can do this job for you - see https://perm-comparator.herokuapp.com/