When to use Story vs Tasks

[@boonbroadcast]

I'm filling in for our Engineering Team Lead while they're out (Leading our PI Planning's/Refinements/Standups/etc). This is something I really needed clarified when it comes to managing our board. Thank you.

[@Natsukashigame]

The Nintendo magazine with Mario and donkey kong on the cover behind 👍🏻

[@user-cj8si9qt2u]

I wish you could make tasks children of stories in JIRA. For example, a story like 'Sign up with email' could then be broken down into tasks that different team members need to undertake. Create an API endpoint would be a task for a web dev, while Create the sign up screen UI would be a task for a frontend/mobile dev (plus each task can have very specific subtasks pertaining to their platform).

[@jacquesbooyens104]

You can - I’ve been doing this for years and didn’t realize anyone did it differently.

[@photossave5743]

I been doing this

[@XxmasteerdclassxX]

The best explanation so far, straight to the point and clear. Also, it reminded me of Adam Sandler for some reason :)

[@tharun3766]

Thank you, simple and clear.

[@nikk4]

Great idea. Wish all Projects could show Subtasks in the Backlog and Board by default to help increase awareness of all scope of an Issue for more accurate planning. But this video is great explanation! Thank you

[@Sun-mc8ph]

Great explanation much appreciated.

[@obulapathichalla414]

super explanation

[@perezokeke5266]

Excellent

[@DrorElovits]

So if for example my Product guy defines the user-story and I need to break this down to actual technical work, I should be using Sub-Tasks (by the methodology presented here?)

[@salimahhossain8161]

Can stories be moved from excel to Jira

[@jeewansingh007]

Can anyone give examples of 5 stories and 5 tasks.