Hello, looking for some assistance on creating an automation Scenario: I have an automation that currently clones a ticket when it is created on a board. * The original issue is created on a standard Kanban - Company Managed Project. * The cloned issue is created on a Jira Product Discovery Project as an "Idea". I would like the status of the cloned issue to be updated when the status is updated in the standard Kanban board. Both projects use the exact same statuses and the workflow of the JPD project allows for any status to be transitioned to any status. * The permissions of the rule are set to multiple projects (Kanban project / JPD project) * The Actor is set to myself who has Creator level access on the JPD project side of things Try 1: I have tried to setup the automation flow as flows: When: Issue is transitioned Branch: For: Linked Issues Type: "is idea for" Then: Transition the issue to: "Copy From Trigger Issue" I get the following error in the Audit Log: Unable to transition your issue to the selected status: SDRP-51 (Dev Backlog - 10270)Try 2: I have tried to setup the automation flow as flows: When: Issue is transitioned Branch: For: Linked Issues Type: "is idea for" Then: Transition the issue to: "Same Status (Loop)" The Audit log Returns "Success" * however after checking the JPD project it doesn't seem to change the status. Anyone got any ideas of doing this?

Okay Updated the flow this was the error, think its the same as last time

So, let's try this, take out any reference to the link type and just have check if there are links there and the transition what is linked to to it for your test.

Also, here are the Rule Details now with myself as the Actor.

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

Automation to move a cloned issues status when the Original ticket is moved to new status.

Jack Young_slboby

Hello, looking for some assistance on creating an automation

Scenario:

I have an automation that currently clones a ticket when it is created on a board.

The original issue is created on a standard Kanban - Company Managed Project.
The cloned issue is created on a Jira Product Discovery Project as an "Idea".

I would like the status of the cloned issue to be updated when the status is updated in the standard Kanban board. Both projects use the exact same statuses and the workflow of the JPD project allows for any status to be transitioned to any status.

The permissions of the rule are set to multiple projects (Kanban project / JPD project)
The Actor is set to myself who has Creator level access on the JPD project side of things

Try 1:

I have tried to setup the automation flow as flows:

When: Issue is transitioned

Branch: For: Linked Issues

Type: "is idea for"

Then: Transition the issue to: "Copy From Trigger Issue"

I get the following error in the Audit Log:

Unable to transition your issue to the selected status:

SDRP-51 (Dev Backlog - 10270)

Try 2:

I have tried to setup the automation flow as flows:

When: Issue is transitioned

Branch: For: Linked Issues

Type: "is idea for"

Then: Transition the issue to: "Same Status (Loop)"

The Audit log Returns "Success"

however after checking the JPD project it doesn't seem to change the status.

Anyone got any ideas of doing this?

Accepted answers

All comments

John Funk

Hi Jack,

Just set the Actor back to Automation for Jira and see what happens.

Jack Young_slboby

Hey John, Thanks for your response but looks like its still throwing back an error.

I have now tried to switch the Link between the clone and the original as i noticed using the "is idea for" didnt show up in the "linked issues" field on the JPD project...

When i switched it to be Clones / Is Cloned by the "Linked issues" field at least recognised there was a linked issue.

But still didnt have any luck with that.

John Funk

So I don't see a message about the transition in this latest one. Did you take that out? Can you share a screenshot of the entire rule?

And the error now is about a field not being available. Make sure the field is on the Edit screen used by the project, and also check the context for the field to make sure it is available for that project and issue type.