Bugzilla – Full Text Bug Listing
| Summary: | Anomaly rejections shall make sure a comment is raised | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Alvaro Sanchez-Leon <alvaro.sanchez-leon> |
| Component: | Mylyn | Assignee: | Sebastien Dubois <sebastien.dubois> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | lmcbout, sebastien.dubois |
| Version: | unspecified | ||
| Target Milestone: | 0.9 | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
Fixed. Will be included in next release |
There is a need to make sure an explanatory comment is raised at the time an anomaly is transition to the REJECTED state, Today the rejection reason is not handy and it is not visible in the three. Proposal: There are two ways to transition the state of an anomaly to Rejected. 1) Via the "Progress the element" command This action triggers a pop-up that allows the transition to e.g. REJECTED When the transition happens a new Text box can be dynamically displayed and the sensitivity of the OK button removed until the user enters some text. This text shall be used by R4E to create a comment to this anomaly. This will make the reason for rejection visible in the three. 2) Via the Properties "State" Transitioning the state to REJECT shall pop-up the same dialog as mentioned above with the state pre-populated to REJECTED and the Reason for Rejection field visible, with the sensitivity of the OK button disable to force the user to enter a reason as mentioned above. Once the solution above is in place the "reason for rejection field" becomes obsolete and shall be removed