Hi!
Hopeful that someone have some good ideas that could help me and my team.. =)
We have had some problems identifying our Epics from the beginning, now we are in Sprint 12 of our project and we want to be able to track the progress on our first big Release, however, when the Epics are linked to our Releases the progress decrases since they are reaching over two Releases.
Do you know any good way of managing this? Can we break the Epics down or would that cause problems in future Releases?
Do you think it would be an idea of disconnect the Epics from the Releases in order to only see progress for tasks, stories and others?
Thank you in advance!
Corinne
From what you are describing, your Epics contain multiple child items and those child items are being released to production over multiple Jira Versions (releases).
If that is correct, I believe you are correct that it would be better to remove the Epics from the release and to only track the child items. You could thus track Release progress and Epic progress independently, such as on a dashboard or with the built-in reports.
Although Jira recognizes the parent/child relationship for the issues in an Epic, I have not seen built-in reporting which displays progress reporting well for Epics spanning multiple releases. Perhaps there is a marketplace addon report which can do this better.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.