Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Help with Jira automation, wrong status on issue

Replaceable
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 5, 2023

Hello everybody,

So I have an automation setup that creates three issues (tasks) upon creation of an epic on our kanban. Our kanban has 3 columns, todo, doing and done. Now all issues are automatically assigned the status to do, except for one. The first issue that is automatically created gets the status backlog. Which also makes it appear in the first column like the other two issues, but with a different status. Now I added a step, changing the epic status from backlog to to-do before creating the issues. But this did not change the anything. I still end up with the first issue having status backlog and the other two having the status to-do.

Is there anyone that could point me in the right direction? Im lost and cant seem to find a solution. I just wat to create all issues with the to-do status.

2 answers

0 votes
Fernando Eugênio da Silva
Community Champion
January 5, 2023

@Replaceable , Welcome to the Atlassian Community!

Are the tasks that are created within the same Epic project?

Have you noticed the flow these tasks use? I ask because whenever an item is created it falls into the first status of its flow. Can you confirm if the first status of the task flow is "To Do" or "Backlog", it may be that you have some other event transiting one of these tasks after creation.

 

Please, if possible, share your automation rule as a print here.

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 5, 2023

Hi @Replaceable -- Welcome to the Atlassian Community!

For automation rule questions, please post images of your complete rule and the audit log details showing the execution.  That will provide context for the community to offer suggestions.  Thanks!

Without seeing your rule, I suspect this is either a branching or a timing issue causing this symptom.

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
TAGS
AUG Leaders

Atlassian Community Events