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

[lena_vasich]

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:

What error do I have sometimes:

Action details:

User condition

Unexpected error executing rule:

java.lang.NullPointerException

What should I change?

[Anandhi Arumugam _Cprime_ · Accepted solution]

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

[lena_vasich]

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

[Anandhi Arumugam _Cprime_]

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.

[lena_vasich]

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

Thank you!

[Anandhi Arumugam _Cprime_]

Glad that helped!

[Gaurav Arora]

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]

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..