We are using JIRA 6.0, locally hosted. We use hierarchical versions to represent major milestones (e.g. 2.0, 3.0) and minor milestones (e.g. 2.1, 2.2), and use both epics and user stories for planning.
While the hierarchical versions on the surface seem to be well suited for this purpose, in practice the feature does not seem to work as documented. Our problems are:
Our workaround is to manually enter BOTH the parent and the child version to the issues, which is becoming unbearable. The documentation says:
All issues under the child version are considered to be a subset of the parent version.
That does not seem to match the behaviour, at least as far as the version report goes.
What are we doing wrong?
Using the drag and drop feature in the Agile board Plan mode does not support adding several versions (or epics for that sake) to a single issue.
Usually you will see
ISSUE-30 My title <version x> <epic y>
If you _manually_ assign two or more versions you will see
ISSUE-30 My title <multiple versions> <epic y>
Dragging and dropping this issue to yet another version will wipe the current version assignment and replace it.
So not a solution rather a "I do not think it can be done" using drag and drop in Plan mode.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs