It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,877
×12,005

question asked: Mar 11 '16, 2:38 a.m.
question was seen: 2,090 times
last updated: Mar 28 '16, 11:45 a.m.

Related questions

Changing attribute "planned for" of a WI holds rank in the plan. How you force again "not ranked"?

0
Fran Burgos (123●1●23●52) | asked Mar 11 '16, 2:38 a.m.
We have two plans with a rank view. When we swap the iteration in "planned for", the WI holds rank from the old plan. Is there any way to avoid this and re-forcing "not ranked"?

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Ralph Schoon (63.5k●3●36●46) | answered Mar 15 '16, 5:37 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I am not aware of any automation for that.

PS: With all the versions out there it becomes more and more important to mention the version in use.
0
permanent link
Fran Burgos (123●1●23●52) | answered Mar 28 '16, 11:45 a.m.
In RTC 5.0.2 I found a trick:

 IAttribute rankAttribute = workItemServer.findAttribute(projectAreaHandle, 
NewRankingAttributeHelper.NEW_RANKING_ATTRIBUTE_ID, monitor);
if(newStateCopy.hasAttribute(rankAttribute)){
newStateCopy.setValue(rankAttribute, null);
workItemServer.saveWorkItem2(newStateCopy, null, null);
}

NewRankingAttributeHelper.NEW_RANKING_ATTRIBUTE_ID is a copy in the WI of the rank in the plans for keeping the value between iteration changes. Hence if you set null this value, the WI is set as "Not-Ranked". 

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.