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:
- Using the agile Plan mode to drag a story to a minor milestone version only assigns that fix version, not the parent.
- As a consequence, when we use version reports for burndown (or burn-up, rather) purposes, we fail. If we want to observe the version report both for the current minor milestone, all is well, but if we look at the major milestone, issues assigned to the child version are missing.
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?
