Issue Link vs. Sub Task


We have a release issue type.

The release issue type may include either requirement, feature or a bug.

Should I have the reuirement/feature/bug as sub-task of the release issue type, or should I link them via link issue?



2 answers

1 accepted

2 votes

It might be better to use links because requirements/features/bugs tend to have sub-tasks of their own! It will be difficult at a later stage to switch.

In the present JIRA analogy, your release issue type can be considered as an Epic and the other issue type should be linked to it just as it happens with Epic.

In my personal experience, it is better to have sub-tasks under stories/bugs to deliver work in chunks to QA and also to separate duties of multiple people working on the same story.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,140 views 13 19
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot