Details
-
Suggestion
-
Resolution: Fixed
-
None
-
None
Description
I hope I have the right component here, I'm referring to the versions column on the right side of the Planning Board.
In an effort to divide and conquer our "Unscheduled" bucket we originally were linking stories as dependencies of very broad epics. We were using ranking in the Unscheduled version to keep everything grouped. This proved too cumbersome. For one JIRA seems to have very limited UI for links. Unlike sub-tasks, linked issues wouldn't drag and drop along with their parents, and you couldn't create links via drag and drop. Lastly you can't see the parent/children in the card templates as you do with sub-tasks.
As a second attempt we've setup several hierarchical "Backlog" versions to categorize the backlog instead of epics. They have no start or end dates assigned, but chronologically they're setup prior to our "Release" and "Iteration" versions. This concept is working fairly well. Using hierarchical versions new unscheduled stories and epics can be categorized by dragging them into the appropriate child of the master "Product Backlog" version. Bulk edits work well too. Further the stats functionality allows us to get an idea of the scope of the various levels of categorization in our backlog. All in all it works much better than links did, but one minor issue is the pagination of the versions board makes it rather awkward from a usability standpoint. It never splits where you would want it to. Also it's less than ideal to have the current release and iteration pushed off the first page. If we could change the page size, or disable pagination altogether, I believe that would help.