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 vote

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 

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Tuesday in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

213 views 1 18
Join discussion

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