What we did: On the PI Program Board, we placed the epic at the end of the chain of stories and tasks, respecting each sprint's capacity and the size of the items allocated to it. When closing the PI, we saved the plan with the confidence vote.
What we observed: Jira saved the epic's Due Date (the end date of the sprint where the epic was placed), but it did not save the epic's Sprint field. In other words, the epic ended up with a delivery date but without a reference sprint.
What we expected: That both pieces of information would be persisted — "the epic will be delivered in Sprint X, on that sprint's end date" — keeping traceability between the target sprint and the date.
We already understand that epics are not assigned to sprints by default (the sprint lives on the child stories/tasks). Our question is about the Program Board's intent:
- Is saving only the Due Date and ignoring the epic's Sprint field the by-design behavior of the tool, or is it a limitation/bug?
- Is there a recommended configuration to also persist the target sprint on the epic when saving the PI (e.g., adding the Sprint field to the Epic screen, date roll-up, or a native feature of the app)?
- If the Due Date is the "official" way to represent the epic's delivery, what is the best practice to avoid losing the epic → target-sprint traceability?
Thanks in advance for any guidance, and screenshots of the configuration from anyone who has solved this in PI Planning would be much appreciated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.