Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 358635 - Information missing when adding anomalies
Summary: Information missing when adding anomalies
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: ---   Edit
Assignee: Sebastien Dubois CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 358711
Blocks:
  Show dependency tree
 
Reported: 2011-09-22 13:58 EDT by Sebastien Dubois CLA
Modified: 2012-01-24 17:46 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastien Dubois CLA 2011-09-22 13:58:27 EDT
When adding anomalies from a file not included in the review, the position in file for the anomaly is not set

When adding linked anomaly in basic reviews, Rank, Class and due Date are not set properly at creation
Comment 1 Sebastien Dubois CLA 2011-09-23 15:02:51 EDT
The following problems are fixed:

- No more exceptions when adding anomalies
- Position is correctly set regardless from where the anomaly is created
- Class, Rank and Due date are set correctly
- The update Rule dialog shows and records the correct information
Comment 2 Jacques Bouthillier CLA 2011-09-26 09:46:46 EDT
When testing on LINUX environment, I noticed the following:
- Select a file not in the review,
- Select a few lines from the editor and Add anomaly
- Enter a due date and use the rules set to define the class and rank
- Select OK
--> The anomaly shows in the R4E Navigator view with the proper line range, but
if you look in the R4E property view, All fields are not refresh from the previous data
Also, the "Rule ID" is never displayed.
Refresh the data by selecting the anomaly from the Navigator view, then most of the data is refreshed in the navigator view except the "Rule ID".
Now, Press "Update" to open the Anomaly details dialogue, we don't know which "Rule ID" was used
to define this anomaly. It should be highlighted.
Comment 3 Sebastien Dubois CLA 2011-09-26 15:20:52 EDT
The follwing was done:

- Fixed small bug where RuleID was not displayed properly all the time
- Fixed bug where the properties view is not refreshed properly (not only for anomalies) when the element added to the review is done from any other view than the navigator view
- Improved Anomaly update dialog to pre-select the currently used Rule (if any)
- Removed unnecessary code that was refreshing properties