Ranking stories in Agile 2.0

[KenC]

Hey all, 

We've been using SDLC/Agile Development for a few years starting in Fuji and we're now on Jakarta.  We're moving from a Release > Sprint structure to the new Group Backlog/Sprint structure in 2.0. 

In the old (let's call it 1.0) version of Agile we had a "Rank" button on related lists of stories under sprints and releases in which we had a UI to move stories up or down and the Story Index or Release Index was adjusted automagically. 

I'm not seeing any similar functionality in the UI now and the docs information discusses the activity of ranking (here) but doesn't actually explain "How" to physically adjust the rank.  From what I can see it's just a list edit method that's available.  Am I missing something here? If we have 150 stories in a group backlog we shouldn't have to list edit enter 150 times to apply a rank. 

Thanks, 
Ken

[anthonybrown]

I found this post about the topic of ranking Stories for Agile 2.0 and was surprised no other posts have been created!  We moved to Agile 2.0 (Kingston) at the turn of the year and have the same issue you are describing.  We assumed that in the Product Backlog view, the drag and drop functionality would "stick" across Agile Board sessions.  For example, moving the Story in position 3 to the top, would now make it the top ranked Story in that particular backlog.  From what I can see, anything that is moved around while in the Agile Board is lost once you leave the page/browser.  Do I have a pop-up blocker or cookies disabled somewhere?  What are others doing to work around this...the documentation doesn't really address this seemingly obvious shortcoming.

[Madhu80]

Anthony, A new UI called Agile board is introduced in Kingston which can be used to manage backlog, rank stories, plan sprints. Global ranking was introduced along with the new Agile board. Upon upgrade to Kingston, a fix script would populate values for the global rank column for existing stories. If drag and drop on Agile board doesn't persist the position of the stories, it is possible that global rank column is not populated for the stories - might have happened if stories were imported post upgrade with business rules turned off or the fix script returned an error. To fix this, please refer to point 2 Troubleshooting tips with Agile 2.0