It appears to be "common wisdom" that a (Jira) Story should be accomplished in single sprint. Does this mean that a complex task that has integrity still needs to be broken down until all the pieces fit can each fit a sprint?
Does this imply that for a Unit of Deliverable value ("Epic"), there can be huge complexity between a (Jira) Epic and its (Jira) Stories?
If so how do we manage the logical continuity between the master Epic, and the Stories that are required to materialize it? To my mind it implies levels of Epics within Epics or Stories within Stories?
Or is everything reported/managed in Jira as just a two-level hierarchy?
(I assume Sub-tasks are out of the picture as they cannot earn story points, and tasks are for practical purposes (maybe a different Workflow) the same as stories.)
Recommended Learning For You
Level up your skills with Atlassian learning
Jira Align Program Essentials
Learn how to use Jira Align at the program level and how to plan for and manage your Program Increment (PI).
Managing Agile Boards and Reports
Learn how to pick the right board type for your team and customize it to fit your specific requirements.
Atlassian Certified Associate
Jira Software Board Configuration
Earn an associate-level credential from Atlassian that shows you can effectively configure Jira Software boards.