How to group related issues: Epic vs Story

We're working on a requirement in our project to view images that we get from some place.

It's my job to send the images, a colleague will do the processing and another will show them on a website. How do we group these issues together? Note that there are a lot of dependencies, we can't process or show without having sent them.

I found that an Epic could have issues, but a Story only has sub-tasks, not plain issues like "New Feature", "Task", etc. What's the way to go here?

1 answer

0 votes

Hello Dave,

Based on what you said, I recommend you to use epics instead of stories, since it can group different issue types and not only sub-tasks.


Arthur Gonçalves 

We have same problem. Our hierarchy is Epic-->Story-->Tasks-->Sub-Task, Epic will include multiple stories and each of this story will in turn have many tasks. Task can have sub-tasks. 
Right now there is no way to link story to task other than using related ticket which is not ideal way. Having Story field in Task(Just like Epic link) would be great.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,663 views 18 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you