Community
Participate
Working Groups
This ticket is related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=176964. Currently, you can sort on "Priority", "Rank", "Summary", "Date Created", "Due Date", "Modification Date", "Task ID" or "Type". Trac does not natively use "Rank" or "Due Date", however many people may have created these fields as custom fields. Because the connector doesn't appear to use ANY custom fields either in Queries (as per https://bugs.eclipse.org/bugs/show_bug.cgi?id=176964) or Sort, if you have developed a workflow that prioritizes tickets with priority but "orders" them within that priority using a custom field, the order is lost within Eclipse/MyLyn. We're having to rely on our ticket list in the browser, then enterting the ID of the ticket we want to work on in Eclipse to start working on it. The back and forth makes the Task List view somewhat moot - except to track context. I tried creating a custom field named "Rank" but that didn't work. It seems that it would be a great leap forward in usability before tackling the more difficult project of full integration of custom fields.
It sounds reasonable to support a rank field in Trac. In the past we have added this for fields where we had reasonable indication that it was a commonly used convention, e.g. tasks of type "story" are decorated differently although it's not a default type in Trac. Can you provide more details how you defined the rank field or point me at Trac plug-ins that support ranking?
(In reply to comment #1) > It sounds reasonable to support a rank field in Trac. In the past we have added > this for fields where we had reasonable indication that it was a commonly used > convention, e.g. tasks of type "story" are decorated differently although it's > not a default type in Trac. > > Can you provide more details how you defined the rank field or point me at Trac > plug-ins that support ranking? I created "Rank" as a custom field in Trac, but as stated it did not use this field when sorting.
Could you post the definition for the custom field from your trac.ini?
(In reply to comment #3) > Could you post the definition for the custom field from your trac.ini? rank = select rank.format = plain rank.label = Rank rank.options = 1|2|3|4|5|6|7|8|9|10 rank.order = 10 rank.value = 0
Just to add to this: I was using "Rank" because it was already an option available in the sortby options. I think it makes sense for existing fields that are already available to be used for sorting to be able to be read if the user has created a custom field of the same name. That way, I could also create a "Due Date" field in trac, and that could be read within Mylyn. Do you think this is reasonable, and any idea on how complex it would be? Perhaps could you point me in the general direction so maybe I could determine a patch of my own?
We are also doing similar thing with bugzilla. We have defined a custom field ("Priority Order") with in Bugzilla to set priorities of bugs. However, Mylyn doesn't have the option to sort by this custom field so we rely on web browser to figure out our priority.
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
