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

This widget could not be displayed.

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.

This widget could not be displayed.

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 Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

162 views 1 3
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