nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

I have set a series of sub-tasks. But I want to set the status of these sub-tasks to "To do"

Jerin Geevarghese

I have set a series of sub-tasks created by an automation rule. But I want to set the status of these sub-tasks to "To do" instead of the usual "Open".

In the automation rule page I only get the option of using the additional field "current status", which as already been set to "To Do". It does not reflect in the statuses of the sub-tasks though. How can this be resolved?

Accepted answers

Jack Brickey

What does your workflow look like for subtasks? Often the initial status for issues is “To Do” not “Open”. In my mind the two statuses are the same. If your workflow has both statuses and To Do follows Open and you want. The status to be To Do then you can add an action in your automation to transition to To do.

All comments

Jack Brickey

Mykenna Cepek

Interestingly, the Create Issue action does not offer the Status field as something that can be set on create.

To implement @Jack Brickey's suggestion, after the "Create Issue" action for each subtask, you'd add:

a Branch with Type = "Most recently created issue"
a "Transition Issue" action with Destination status = "Open"

However, I'd also suggest you inspect the workflow. I'm wondering why newly created issues in your project aren't starting out in the status you want.

Jack Brickey

Precisely

Jerin Geevarghese

Thank you for your responses.

I am not sure why it does not reflect either. But I added the transition to issue as "To do" and now it works.