resolution_fixed type_enhancement | by rjsparks@nostrum.com
The current "Complete review" form is well optimized for the reviewer, who knows the version reviewed and result when the form comes up.
If a directorate secretary is entering the review into the datatracker for any reason (say, a reviewer just sent the review to the list and won't likely come back to the tracker to enter things), the form should be optimized differently - it should start with the list search option, probably selected (which means defaulting to a list search), and fields could be populated based on automatically selecting the first non-re: result. The secretary won't know which version was reviewed or what the result was until reading the actual review.
Issue migrated from trac:2061 at 2022-03-04 05:33:26 +0000
resolution_fixedtype_enhancement| by rjsparks@nostrum.comThe current "Complete review" form is well optimized for the reviewer, who knows the version reviewed and result when the form comes up.
If a directorate secretary is entering the review into the datatracker for any reason (say, a reviewer just sent the review to the list and won't likely come back to the tracker to enter things), the form should be optimized differently - it should start with the list search option, probably selected (which means defaulting to a list search), and fields could be populated based on automatically selecting the first non-re: result. The secretary won't know which version was reviewed or what the result was until reading the actual review.
Issue migrated from trac:2061 at 2022-03-04 05:33:26 +0000