Community
Participate
Working Groups
[Mylyn 2.0 on Eclipse 3.3.1.1 on Mac and PC against Trac 0.11 / XmlRpc] I often use the following priorities as custom priorities in trac: urgent / critical / required (default) / desired / wished This has worked well for the projects I've been on. However the more I use mylyn the more I want it to recognize MY priorities - and both sort and mark them up the same way that trac does. Trac simply puts orders tickets as per order of priorities, and colours them accordingly (middle one being default colouring -> P3 in mylyn). Could mylyn do that too? There's really no need to match the trac defaults exactly - ordering is good enough yardstick for assigning icons (and certainly good enough for ordering. (this isn't really a bug, but a feature request, but am filing following http://dev.eclipse.org/newslists/news.eclipse.tools.mylyn/msg00403.html)
We use Bugzilla to track enhancement requests as well as bugs so it is perfectly fine to file any wishes for features or improvements. It should be possible to provide a better mapping by using the priority value as you have suggested. I look into supporting this in the next release.
*** Bug 213961 has been marked as a duplicate of this bug. ***
In my opinion the requirement is to be able to make a mapping between the priorities in the taskrepository and mylyn. For each priority in the taskrepositor a corresponding mylyn priority should be assigned to map it. Eg. Critical P1 Major P2 Minor P4 Medium P3 (default) This mapping should be stored by the taskrepository. At the company where I work we have several Trac environments. Some of them have a different priority list. In my Eclipse environment I have linked several trac environments. So the mapping has to be per taskrepository (and not per workspace). This mapping is also specific for that taskrepository not for others (that is another reasons why to store it per taskrepository. In line with this you can also think about a mapping for tasktypes. In Trac you can customize the types as well.
You're right. We have the same scenario here.
I have committed support for customized priorities to CVS. The mapping is based on the order (values) of the priorities of the respective Trac repository. The priority with the lowest value which is by default "blocker" with a value of 1 is mapped to P1. The priority with the highest value is mapped to P5. Other priorities are mapped to P2, P3 and P4 depending on their value. This feature will become available in next week's build.
Created attachment 87964 [details] mylyn/context/zip
