It's all about the answers!

Ask a question

"This plan item is not yet ranked" info message in


Simon Webb (4685) | asked Feb 09 '10, 6:58 p.m.
JAZZ DEVELOPER
I get a little blue "i" to represent this against tasks in an iteration plan. My project is configured (Config data -> Planning-> Plan attributes) with ranking using the Priority attribute - and the tasks all have Priorities assigned. If I move the tasks around manually by dragging in the plan editor, the blue "i"s disappear. Can anyone enlighten me as to what I am doing wrong please?

2 answers



permanent link
Simon Webb (4685) | answered Feb 10 '10, 8:46 a.m.
JAZZ DEVELOPER
Hi Simon,

RTC has an internal ranking attribute and ranking views that use it to support agile ranking. It is supposed to work as follows.

I the beginning usually there is an unordered set of work items with no priorities. The team looks at this in a backlog plan view. Then the team starts to order things (rank them) and assign first priorities using drag and drop. Dragging a work item before a high priority one makes it high priority. Or medium etc.
So while work items are shuffled around considering importance and dependencies you get an order that makes sense and the "not ranked" flag disappears. If all are gone you can be sure to have addressed each one. Plus you get a good start on priorities.

If you don't use it this way you can ignore the flag.

Ralph

I get a little blue "i" to represent this against tasks in an iteration plan. My project is configured (Config data -> Planning-> Plan attributes) with ranking using the Priority attribute - and the tasks all have Priorities assigned. If I move the tasks around manually by dragging in the plan editor, the blue "i"s disappear. Can anyone enlighten me as to what I am doing wrong please?


Terrific answer - thanks Ralph!

permanent link
Ralph Schoon (63.3k33646) | answered Feb 10 '10, 1:51 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Simon,

RTC has an internal ranking attribute and ranking views that use it to support agile ranking. It is supposed to work as follows.

I the beginning usually there is an unordered set of work items with no priorities. The team looks at this in a backlog plan view. Then the team starts to order things (rank them) and assign first priorities using drag and drop. Dragging a work item before a high priority one makes it high priority. Or medium etc.
So while work items are shuffled around considering importance and dependencies you get an order that makes sense and the "not ranked" flag disappears. If all are gone you can be sure to have addressed each one. Plus you get a good start on priorities.

If you don't use it this way you can ignore the flag.

Ralph

I get a little blue "i" to represent this against tasks in an iteration plan. My project is configured (Config data -> Planning-> Plan attributes) with ranking using the Priority attribute - and the tasks all have Priorities assigned. If I move the tasks around manually by dragging in the plan editor, the blue "i"s disappear. Can anyone enlighten me as to what I am doing wrong please?

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.