| Summary: | [regression] priorities mapped to P3 when migrating from Bugzilla 3.4 or earlier | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Peter Kullmann <peter.kullmann> | ||||||
| Component: | Mylyn | Assignee: | Steffen Pingel <steffen.pingel> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | major | ||||||||
| Priority: | P2 | CC: | eclipse, mauromol, robert.elves | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | 3.4.1 | ||||||||
| Hardware: | Macintosh | ||||||||
| OS: | Mac OS X | ||||||||
| Whiteboard: | |||||||||
| Bug Depends on: | |||||||||
| Bug Blocks: | 309105 | ||||||||
| Attachments: |
|
||||||||
|
Description
Peter Kullmann
The reason for our problem was this: - Bugzilla 3.6 ships with priorities "Highest", "High", ... instead of "P1", "P2", ... - The Mylyn Bugzilla connector has mappings for priorities hard coded. If Bugzilla version is >= 3.6 it expects "High" and not "P2" Our bugzilla installation was just updated to 3.6 and therefore kept the old "P1" priorities. After my update to the newest Mylyn it seemed as though as the tasks have lost their priorities. The good news is that it is possible (and easy) to update the priority field values in bugzilla. After setting them to the expected values mylyn works again as expected. The issue here is related to bug 242739. I'm leaving this open, but for us it is no longer an issue. Please update to the latest version of Mylyn. *** This bug has been marked as a duplicate of bug 310875 *** Thanks for the detailed explanation, Peter. Sorry for closing this bug prematurely. It's a very common scenario that Bugzilla repositories are migrated, so it seems likely that priority levels would be P1 - P5 even in version 3.6 and later. Created attachment 175453 [details]
fix and test case
Created attachment 175454 [details]
mylyn/context/zip
Patch committed to head and e_3_6_m_3_4_x branch. |