| Summary: | Postponed Anomalies function does not work properly | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Sebastien Dubois <sebastien.dubois> |
| Component: | Mylyn | Assignee: | Sebastien Dubois <sebastien.dubois> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | alvaro.sanchez-leon, lmcbout |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
|
Description
Sebastien Dubois
After more tests on newest release, it seems that the only problem left is that we cannot disable the postponed container Another problems that are still occuring: - The postponed file /postponed anomalies entries could end up duplicated in the model/navigator tree. Closing/reopening the review does not clear the problem. This happens when we disable the postponed container and then immediately import postponed anomalies - When the original anomaly state is changed, the postponed anomaly state does not get updated Fix is implemtented and will be delivered at next release |