How to handle two dependent Issues, but unique from a workflow perspective

Two Scrum tasks.

Both in the same project

Both dependent on each other (i.e. both must complete within the Sprint)

But both have completely different work flows.

Should they reside in different Jira projects?

Or, perhaps, one should be given a different Issue Type to map it to its unique Workflow?

Although Scrum suggests the cross-functional team, in reality there is an SME team focussed on specific infrastructure tasks (such as building out new AWS environments) that the application feature team will never touch, and vice versa.

My initial thoughts are:

  • Keep them in one JIRA project (as its all contained in one Sprint) and rely on the tasking out of an individual Product Backlog Item, when produce sub-tasks, to assign the work;  but can there be different types of sub-task each with its own workflow?


JIRA version is 5.1 / JIRA Agile is being used.

1 answer

1 accepted

1 vote
Accepted answer

Yes, they can be of different issue types or different subtask types and they can have different workflows. Both can be in the same project and on the same board.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,172 views 5 10
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