Ranking stories in Agile 2.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2018 01:12 PM
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
- Labels:
-
Agile Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2018 01:16 PM
Do you have the Context Ranking plugin activated?
Thanks,
Laurie
Please mark Correct or Helpful as applicable!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2018 01:23 PM
Hi Laurie, yes we do.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2018 10:31 AM
So I've done a bit more digging on this and it seems the specific issue I'm experiencing right now is because we're kind of stuck in a middle ground.
We do have the Context Ranking plugin enabled but this tool is the old Agile (let's call it 1.0) tool for ranking. This method leverages the "index" fields that are added to the table in question such as Product Index, Sprint Index etc. Agile 2.0 seems to have turned off these index configurations with the implementation of their new, sequential ranking model. These new values are stored in new fields Product Rank, Sprint Rank etc. Rather than the random index numbers (often in the hundreds of thousands or even millions) these are simple 1, 2 3 etc.
The middle ground reference I made is the combo of Agile 2.0 and Jakarta (our current version). On Jakarta, from what my research has produced, the only way to rank stories using the new field is in a list view. Set a story to 1, another to 2, and on and on. With a backlog of a couple hundred stories you can imagine this is a pain. I discovered though that in Kingston, they a have a new Agile Board that has a ranking tool in drag-n-drop fashion. So we'll have to wait a bit to leverage these ranks.
Details on the Agile Board in Kingston: https://docs.servicenow.com/bundle/kingston-it-business-management/page/product/sdlc-scrum/concept/a...
Unless anyone has more info about something I'm missing here.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-10-2018 03:30 AM
Hi,
Sorry for the late reply. The UI button "Rank" is an UI action and the ServiceNow by default had d=made them inactive in the latest versions. You can search for the UI action for "Story" table in the name "Rank". I have noticed that there are quite a few UI actions under same name for Story table. You can make the appropriate UI actions for stories where the parent table is Sprint and Release. I hope this will get the buttons on related list. May be ServiceNow people might have disabled them for some reasons. It is best to include the developers in community and discuss the thread. But I think you can get them back by activating the respective UI actions
Thanks and Regards,
Jagadeesh