How to change the assignee when issue moves to another project?

lena_vasich July 25, 2024

What I need:

If the issue is moved to another project

and

current assignee is not in one of roles of a new project (= has no permission to be assigned)

then

change assignee to project lead.

 

What I made:

autom1.jpg

 

What error do I have sometimes:

 

Action details:
User condition
Unexpected error executing rule:
java.lang.NullPointerException
What should I change?

2 answers

1 accepted

0 votes
Answer accepted
Anandhi Arumugam
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!
July 25, 2024

Hi @lena_vasich You can try something like this. Hope this works for you. 

Automation Rule_Update Assignee when issue moved.png

lena_vasich July 25, 2024

Thank you for your answer. You mean add logging action? I'll try, ok

Anandhi Arumugam
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!
July 25, 2024

Hi @lena_vasich Can you try adding a condition to check if the issue has an assignee? Also try to log the smart value's result and the assignee to see why it failed for specific issues. Also check rule actor to see if it is Automation for Jira.

Like Gaurav Arora _Wipro Id_ likes this
lena_vasich July 25, 2024

Genius! There can be no assignee =) that's why nullPointer

Thank you!

Anandhi Arumugam
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!
July 25, 2024

Glad that helped!

0 votes
Gaurav Arora _Wipro Id_ July 25, 2024

I would suggest you to double check if the target project have a Project Lead or if the current Lead is an active user. Also, try this rule with another target project.

Apart from this, I don't see any error with your approach. I replicated it and it worked for me.

lena_vasich July 25, 2024

Thank you for your answer. Project lead is active, everything is fine with it...

Sometimes this rule works, sometimes not, I can't understand why can I have the nullPointer..

Suggest an answer

Log in or Sign up to answer