"I want to assign the issue to the issue assignee at the end of a project. I created a rule for this

[Simon Meyer]

[Marc - Devoteam · Accepted solution]

Hi @Simon Meyer 

Welcome to the community.

What is your exact issue?

I see an automation rule that completed.

[Simon Meyer]

I want to assign the issue to the issue assignee at the end of a project. I created a rule for this. However, the audit log keeps showing that 'The issue's assignee has already been cleared', even though it can't be due to the workflow, such as a post-function."

[Marc - Devoteam]

Hi @Simon Meyer 

I don't get you. If an issue is assigned it already has an assignee.

Based on you rule it seems you want ot assign it to the current project lead?

Then use the smart value: {{issue.project.lead}}, also mentioned by @Tessa Tuteleers 

[Simon Meyer]

I explained it ambiguously. I don´t want the projectlead from the whole project. My firm has an custom field in every issue/ticket which is also named projectlead. I have already implemented it in my test board/project (there the rule works perfectly), but not yet in the main project, because the assigned user keeps being cleared. The audit log shows that the issue was assigned, but below it says 'The issue's assignee has already been cleared.' Unfortunately, this is in German on my screenshot.

[Marc - Devoteam]

Hi @Simon Meyer 

Hi, check the history in you main projects issue, is there another action that clears the Assignee field, via automation or a workflow post-function.

[Simon Meyer]

In my history, it doesn't show that the assignee was changed in any way. However, the audit log shows that the issue was assigned. Am I misunderstanding the audit log?

[Marc - Devoteam]

Hi @Simon Meyer 

So the summarise.

The issue is raised assigned to a user and a custom field is used to set the project lead (field Projektleiter).

What type of field is this, a user picker field or other?

The rule you have needs to set the field assignee to the user specified in the field Projecktleiter, correct?

The use of smart value, in the edit action, should work.

The audit log tells it's cancelled. Check the automaton history on the issue, are their no other rules active on the transition to any of the statuses mentioned in the rule.

[Simon Meyer]

Hi Marc,

The field is a user picker. 

The rule is to set the field assignee to the user specified in the field Projecktleiter.

Only another automation rule has been triggered in the automation log in the issue. The first one is mine, which I already sent as a screenshot, and the second one is in the lower screenshot. This second rule is solely responsible for sending an email.

And 

[Marc - Devoteam]

Hi @Simon Meyer 

What does the "History" tab tell you on the issue?

Also check the workflow is there a post function on the transition(s) to a "Done" state that clears the field Assignee?

Something has to clear the Assignee field.

It could also be a global or multi project automation is acting on this.

[Simon Meyer]

The history only shows that the status was changed, the rank was updated, and the resolution is now 'Done'.

A global automation would also appear in the automation history on the issue, wouldn’t it?

And the only rule on the transition is a condition restricting who can move the issues (see screenshot 2).

[Marc - Devoteam]

Hi @Simon Meyer 

So then what are the differences baed on the project your testing with and the active "live" project?

As your automation works on your test project, there needs to be a difference in relation to the live project.

Some difference on the project causes this problem, as having the same field, with the same setup and context should not compromise the automation rule.

[Simon Meyer]

Problem solved! There were actually two fields named 'Project Manager', which must have caused the confusion. Appreciate your help!

[Tessa Tuteleers]

Hi @Simon Meyer , 

Welcome to the community!

This is the smart value you want: {{issue.project.lead}}

kr, 
Tessa