Sub-task Influence story state

[蘇家郁]

Hi everyone

I would like to automate something, but I'm not sure how to do it. I have a Story that contains many sub-tasks. I want the status of the Story to change automatically when any of its sub-tasks moves from "To Do" to "Doing," because once a sub-task starts, it means the Story has also begun. This should also apply to the "Code Review" stage. Additionally, when all sub-tasks are marked as "Done," the Story should automatically be marked as "Done" as well. How can I implement this automation?

[Trudy Claspill]

Hello @蘇家郁 

Welcome to the Atlassian community.

Regarding the last scenario:

transition the parent issue to Done when all it's subtasks are Done

When you navigate to the Automation Rule screen you will see a tab named Templates. On that tab are several rule templates including one that specifically matches that scenario.

For the other scenarios there is not a template available. The basic concept would be a rule triggered by transition of the subtask. That rule/rules would be a bit more complicated.

Does your workflow allow issues to move backwards through the workflow?

If a parent issue is Done and a subtask is reopened how should that affect the parent issues?

[蘇家郁]

After thinking about it, I realize the problem I'm facing is that the sub-tasks are already in progress, but the Story is still in the "To Do" status. This leads to the Story status always being inaccurate when reviewing reports. Of course, I can manually update it, but I'm just wondering if there's a more convenient way to handle this.

To address your question, ideally, the Story shouldn't be marked as "Done" if there are still open sub-tasks. Perhaps, at that point, a new Story should be created.

Additionally, I'm curious how others are handling this because this seems like a common scenario.

[Trudy Claspill]

Hello @蘇家郁 

Thank you for the additional information.

To address your question, ideally, the Story shouldn't be marked as "Done" if there are still open sub-tasks. Perhaps, at that point, a new Story should be created.

That did not quite address the question I asked. 

If a parent issue is Done and a subtask is reopened how should that affect the parent issues?

In my question the scenario is that the parent and subtasks are all Done, and then, at a later point, a subtask is reopened (transitioned back to To Do, or In Progress, or another "not done" status).

There are a variety of ways to address the sychronization of status between a parent issue and its subtasks. To provide some suggestions we need more information from you.

1. What is your subscription plan? Free, Standard, Premium, or Enterprise?
2. Is this for a Company Managed project or a Team Managed project? Get that information from the View All Projects page under the Projects menu.
3. What is your level of access? Are you a Project Administrator for the target project? Are you a Jira/Product Administrator for the Jira Application?
4. Do the subtasks and the parent issues all use the same workflow? Can you show us the workflow diagrams for the issue types?
5. Do you have any third party apps that extend the capabilities for customizing the workflows?
6. How closely synchronized do you want the statuses to be? Originally you said the parent should move forward with each subtask that first moves forward, but they in your last response you mentioned only that the parent should be "in progress" while subtasks are in progress.

Depending on your answers you may be able to implement some automation in either your Workflows or through Automation Rules or both. There are service limits on Automation Rules based on your subscription plan, and that may impact the suggestion of which path is best for you.

Your level of access will affect which solution you specifically may be able to implement without help from somebody in your organization with more access than you.