Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

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

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?

0 votes



2 answers

Permanent link
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?

0 votes


Permanent link
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!

0 votes

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Feb 09 '10, 6:58 p.m.

Question was seen: 6,615 times

Last updated: Feb 09 '10, 6:58 p.m.

Confirmation Cancel Confirm