Advice on Choosing Best Issue Type for Workflow

We are a team of tech writers who are trying to figure out the best way to assign tasks on JIRA. Our product owners create Epics and user stories for their team and we need to track these tickets and create our own tasks without affecting their workflow. Is is best to create new user stories to link to their stories or is it best to create sub-tasks? Again, we do not want to affect their ability to close tickets before we finish with our work. But we do need to assign the tickets back to them for review and be able to close the ticket once we're done. Any feedback would be appeciated!

2 answers

1 accepted


Using sub-tasks will not prevent your product owners from being able to close out issues. I believe the default Jira settings have a technical sub-task issue type as well. The interaction between the issue types will all depend on how your workflows are setup.

Hope this helps.

Hi Sharon, Thank you! This info is very helpful. I wanted to make sure that the product owner's work is not dependant on the tech writer's completion of their projects.

Suggest an answer

Log in or Join to answer
Community showcase
Emilee Spencer
Published yesterday in Marketplace Apps

Marketplace Spotlight: DeepAffects

Hello Atlassian Community! My name is Emilee, and I’m a Product Marketing Manager for the Marketplace team. Starting with this post, I'm kicking off a monthly series of Spotlights to highlight Ma...

37 views 0 3
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
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