Automation Rule won't assign an issue correctly

[Daniel Lowe]

I have an automation setup to create a ticket in project 2 based upon a ticket going through a certain transition in project 1, I edit the newly created ticket and copy a number of fields, which all work as I expect.

The issue I have is I seem unable to set the assignee of the newly created ticket correctly, I've attempted using edit to copy the assignee field from the triggering issue and I've also attempted the using the assign issue automation, I'm getting an error in the automation which makes no sense to me:

The automation is advising there's no parent issue to copy the assignee from, but as you can see on the left I'm asking it to copy from the trigger issue (not a parent).

When I used the edit automation to copy the assignee field, it seems to incorrectly copy the reporter field.

Is this a bug or am I missing something?

EDIT: for clarity, Project 1 is a Jira Service Desk Project and Project 2 is a classic org administer Jira Software project.

[Mohanraj Thangamuthu]

What is the access level on the project and also this user(assignee) is added to the project to any project role ?

[Daniel Lowe]

I'm an org admin and admin and user on both projects, the ticket from project 2 fails to assign to me where I am the assignee and not the reporter

[Deepak Jain]

Hi @Daniel Lowe ,

Thank you for reaching out.

Indeed, Jira Next-gen projects have a different architecture than Classic projects, so some functions in Jira automation might not work as expected.

I would suggest following things here:

•  Try and add the action "Re-fetch issue data" to the rule before the final action
• Or Create two automation rule:
  • 1st one to create issue in SD project
  • 2nd one to copy assignee value, and trigger this second automation rule once first one is completed.

Let us know if it works for you.

Regards,
Deepak

[Daniel Lowe]

Thanks @Deepak Jain , the SD project is a classic project, but the HD project is a Jira Service Desk project.

I realised I had made a mistake by not branching the rule (I'm trying to assign the newly created SD ticket to the assignee of the HD ticket), but branching and re-fetching still encounters the same issue complaining there wasn't a parent (even though I'm trying to copy assignee from trigger rule not a parent).

In the end I've settled for branching and assigning the newly created SD ticket to the user who triggered the rule, this seems to work and will meet most of my use cases.