Product Design board

[João Mota]

Hey everyone!

First of all thank you so much in advance.

I am responsible for creating a jira board to manage design tasks.

Right now we have Epicos, we have Story and we have substasks associated to those Stories.

Do you think this logic makes sense? Or should it be a Story and then tasks?

Any advice? Suggestions?

Thanks

[Zulfiqar Bin Zafar]

Dear @João Mota ,

Welcome to the community,

The approach you are using are good because inside epic there are multiple user stories and you can create sub task in those stories. 

Because an epic is a large body of work that can be broken down into a number of smaller user sub tasks while user stories in Jira are concise representation of a feature in a developing system described by an individual who needs this new functionality.

Thanks & Regards,

Zulfiqar Bin Zafar

[João Mota]

Thank you so much @Zulfiqar Bin Zafar ,

Your answer helped a lot!

I guess the main question that keeps popping in my mind is: so what not follow this logic: Epic -> Story -> Task? 

As stated above right now we are skipping the “task” hierarchy and use this one : Epic -> Story -> Subtask

Thats the part that is confusing me a little bit.

Thank you 

[Zulfiqar Bin Zafar]

Actually the task or subtask itself is same if you consider because Jira has 3:

• Epic 
• Story
• Task 

So it is totally upon how you treat that task according to your requirement. 

The both approach is good Epic -> Story -> Task or Epic -> Story -> Subtask 

Because "Task" in Jira terminology indicates a particular piece of work to be done and subtask can be created for an issue to split the issue into smaller chunks. 

Thanks & Regards,

Zulfiqar Bin Zafar 

[João Mota]

Thank you so much @Zulfiqar Bin Zafar 

You helped a lot!

[Zulfiqar Bin Zafar]

@João Mota if that helps you a lot please accept the answer so that it can be beneficial for other as well