Subtask Dependencies for Request Type

[Jennifer]

I have a request type in Jira Service Management that contains five subtasks within it. A few of the subtasks can be done simultaneously while there are other tasks that depend on the task(s) immediately preceding it to be complete before becoming available for assignment.

Example:

Task A and Task B can be done simultaneously but both must be done before Task C is available. 

Task C must be completed before Task D and Task E are available.

I've seen other articles on here about a similar scenario but they're not giving me quite what I need. I was hopeful someone had recommendations. Can this be done with automation or do I need to also do something with the workflow?

I know how to create the subtasks but I don't know how to make them dependent on one another.

This is NOT tied to any scrumboard, epic, story, etc. It's strictly within the service management side that customers will use to submit issues.

[Trudy Claspill]

Hello @Jennifer 

When you say the dependent task should be "available for assignment" only when the predecessor task is complete, what exactly does that mean to you?

1. The Assignee field can't be set?
2. The status can't be changed?

[Jennifer]

Task C cannot be available for someone to handle/work on until Tasks A and B are complete. Tasks A and B should be Closed/Done before Task C is in a status of Open for someone to handle. 

Also, I'm using "task" in my wording, but it should be subtask.

[Trudy Claspill]

Hello,

Thank you for that additional information. I am still not clear on what a user can do with a task that is "available" vs. a task that is "unavailable". What does the user do when they "handle/work on" a task? How do they interact with that task in Jira? Should be prevented from...

• making any edits to the task
• setting the Assignee of the task
• changing the status of the task
• adding comments to the task
• logging work (the time tracking function) against the task?

Does a task sit in another status when it is "unavailable", and not get changed to Open until it is available?

We need to understand what Jira functionality needs to be blocked when the task is "unavailable", to whom those blocks should be applied, and if there are any exceptions about who is blocked from that functionality.