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

Status and assignee does not update in cloned issue

Sophie Petenko

POV: issue is created in project A, it's automatically cloned into project B, and linked. If any field is updated in trigger issue (in any project), the cloned issue is updated subsequently.

I have set the automation, however, Status and Assignee are not updated in the cloned issue, they do not even trigger the rule as showed in audit log ;( Screenshot 2022-10-10 121054.png

Accepted answers

Sakina

@Sophie Petenko could you try using field value change trigger add all fields that you want

All comments

Ismael Jimoh

Good day @Sophie Petenko

With the following topic, I would say for status, you would need a transition rule because though it is a field, the status needs to be transitioned to get to. Make sure the automation user has the transition permission.

As for the assignee, make sure the user in question can be set as an assignee(Assignable user in project B permission scheme) and the automation user can assign issues (Assign Issue in project B permission scheme).

I will suggest breaking this out of the bulk field edit change to test it first and validate that it works and then adding the step that worked for you also to the main Automation.

Regards.

Sophie Petenko

Unfortunately, all mentioned above was tried still no trigger of the rule

Sakina

@Sophie Petenko could you try using field value change trigger add all fields that you want

Sophie Petenko

Thank you! It's working just perfectly

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