If a story (parent issue) is meant to include subtasks (child issues) ( eg a global feature includes sub features) , what would be a user story to describe a parent issue? My understanding is that a story should sounds - as I user I want to be able to do X to achieve Y. In case of a parent tickets it sounds to me - As a user I want to be able to do X1, X2...X6 to achieve Y1, Y2...Y6 - which does not sound right to me.
What are your thought?
Hi @Tatyana,
A Story is a parent ticket in Jira, and it describes an end-to-end functionality to be implemented in the product, but small enough to be completed in a sprint (or two). A story can be a stand-alone functionality, or it can be part of a larger feature (Epic in Jira). Stories are divided in sub-tasks, which usually represent actions (work) to be performed for implementing that story / functionality.
Hope this helps.
Danut
Hi @Tatyana,
The main difference is that Epic > Story is at a higher level than Story > Sub-tasks, which means that Epic > Story is meant for defining and planning work to do (at a higher level), while Story > Sub-task is for planning/executing the work within a story (at micro level).
So some differences are:
Hope this helps.
Danut.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.