Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 370566 - Anomaly rejections shall make sure a comment is raised
Summary: Anomaly rejections shall make sure a comment is raised
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: 0.9   Edit
Assignee: Sebastien Dubois CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-03 11:00 EST by Alvaro Sanchez-Leon CLA
Modified: 2012-02-29 03:58 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alvaro Sanchez-Leon CLA 2012-02-03 11:00:36 EST
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
Comment 1 Sebastien Dubois CLA 2012-02-29 03:58:16 EST
Fixed. Will be included in next release