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; } } }

"Create" automation triggering when moving from Backlog

Brian Salman_id8ts4

Hello!

I recently created an automation that triggers from Issue Creation. The automation updates the Description based on what's in the ticket summary, and essentially templates the Description so that it's clear what is required for the team to fulfill the request.

My team's Jira project is a Kanban project with a Backlog status. I noticed that when I move the ticket from the Backlog status to the To Do status, the automation runs again. If I do that again (return the same ticket to Backlog, then go back to To Do), the automation will run again. If I go from Backlog to any In Progress status, the automation does not run.

Does anyone know what I'm doing wrong here, or if it's a bug? My first thought is that since it's a Kanban project, that maybe Jira is seeing the transition from a Backlog status to a To Do/Open (gray-colored) status is being seen as a Create event, since the issue doesn't happen if I go from Backlog to an In Progress (blue-colored) status.

Accepted answers

All comments

Trudy P Claspill

Hello @Brian Salman

Welcome to the Atlassian community!

Whenever asking for help with an Automation Rule, it is very helpful to us if you post an image of the entire rule.

Are you absolutely sure it is the same rule that is being triggered when you change the status?

Have you checked the Workflow Transition Post Functions to see what they show for events being fired. The Create Issue event should be fired only on the Create transition. If that is in any other transition it should be replaced with the Generic Event.

Trudy P Claspill

Screen Shot 2022-12-29 at 12.03.31 PM.png

Ste Wright

Hi @Brian Salman

Could you post the details and/or a screenshot of your rule?

It would also be beneficial to check the audit logs of the rule - check it is executing when you think it is - and test it based on changing the status, see if any execution is present, and if it's successful or not.

Ste

Brian Salman_id8ts4

Hello Trudy! Thanks for your reply. I've attached screenshots of the rule, and then another of the rule triggering just from a status change. I had to black out a bunch of info, but hopefully it demonstrates that the automation fired and removed everything that was added to the Description and reset it to what the automation does when the ticket is initially created. Screenshot 2023-01-03 at 12.39.48 PM.png Screenshot 2023-01-03 at 12.40.24 PM.png

Brian Salman_id8ts4

Hello Stephen! Thanks for your reply. I've attached screenshots of the rule, and then another of the rule triggering just from a status change. I had to black out a bunch of info, but hopefully it demonstrates that the automation fired and removed everything that was added to the Description and reset it to what the automation does when the ticket is initially created.

Screenshot 2023-01-03 at 12.39.48 PM.png Screenshot 2023-01-03 at 12.40.24 PM.png

Trudy P Claspill

Hello @Brian Salman

Please take a look at the guidance I offered in my answer about checking the Post Functions on the transition to the Open status, in the workflow that applies to the issue type that was affected.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud