Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 165518

Summary:	[api] support customized priorities
Product:	z_Archived	Reporter:	Joseph Marques <simcoen>
Component:	Mylyn	Assignee:	Robert Elves <robert.elves>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	ekuleshov, juerg_billeter, tobias_widmer
Version:	dev	Keywords:	helpwanted
Target Milestone:	2.0
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Joseph Marques

2006-11-22 15:05:46 EST

I just realized that for the last several hours my eclipse error log has cataloging instances of the following:

Plug-in: org.eclipse.mylar.core
Severity: Info
Message: Mylar: unrecognized priority: The request should be considered desireable but is not an immediate necessity.
Exception Stack Trace: An exception stack trace is not available.

I've been getting these messages every 15 minutes, which is precisely my auto-synchronization interval.

Since this is an informational message, I guess Mylar can work with whatever is the unrecognized priority value, but if the error message were changed to be more informative (include the repository type/name, bug id, description/summary, etc) then the user could know exactly what could be awry and take the appropriate steps to fix it.  At the very least, I think the message should include the value of the invalid priority.

Comment 1 Mik Kersten

2006-11-27 11:21:10 EST

Is this for Bugzilla as indicated by the component, or for JIRA?  As far as I know only JIRA will issue these messages.

Comment 2 Joseph Marques

2006-11-27 11:24:18 EST

I didn't know what it was for at the time, but yes I do believe it was for a JIRA issue now.

Comment 3 Mik Kersten

2006-11-27 13:30:18 EST

I think that it does include the value, which in this case is being returned as: "The request should be considered desireable but is not an immediate necessity."  However, we should not be polluting the error log in this way, so instead I have documented this as a known limitation in the FAQ, and will consider this a request to support customized priorities (which may be difficult if JIRA does not provide an ordering). 

http://wiki.eclipse.org/index.php/Mylar_FAQ#JIRA_Connector_troubleshooting

Comment 4 Juerg Billeter

2007-02-28 11:27:16 EST

We also need support for a more flexible priority system for our connector. Our custom priorities are comparable, i.e. they can easily be used for sorting.

Comment 5 Mik Kersten

2007-03-16 22:04:59 EDT

The Tasks framework needs to support connectors customizing priorities in this way.

Juerg: let me know if you have a proposal or patch.

Comment 6 Mik Kersten

2007-05-04 10:29:34 EDT

Tobias: could you describe how you want this to work?  The only thing that's fixed right now is the number of priorities, so are you asking for more or fewer?

Comment 7 Tobias Widmer

2007-05-04 11:42:14 EDT

As far as I understand, Mylar has support for P5 strings (representing low priority) to P1 strings (representing high priority), which is kind of designed for Bugzilla workflows.

For our connector, we have custom priorities, basically representable by the numbers 1 to infinity (or more realistically determined by team process).

I was just wundering whether Mylar has some support for mapping repository connector-specific priorities to a common denominator, in order to be able to compare priorities and to convert them correctly.

Comment 8 Mik Kersten

2007-05-04 13:27:35 EDT

Yes, a connector controls how one of its tasks is created and sets the priority accordingly.  Fore example, by default JIRA has priorities called trivial/minor/... and these are mapped into the 5 priority levels understood by the Task List.  The Task Editor allows them to be edited by name and could allow editing of a larger set of attributes.  The fact that we eventually map to "Px" strings is only used for externalization.

So I'm not sure if there is anything else that needs to be done here.  Connectors have their own richer notion of priorities and the Task List reduces that to a UI that's easy to use with 5 separate levels, the icons for which a connector can specify.  We could turn this into a request to support more than 5 priority levels supported in the Task List, but my feeling is that having more would reduce usability.

Comment 9 Robert Elves

2007-06-21 21:29:14 EDT

Based on Mik's points in comment#8 I'm marking won't fix. If this requires further discussion feel free to reopen.