Jira tasks created from Confluence automation do not assign user to task

[Tim]

Hi, our company uses both Confluence and Jira Cloud.

I don't know if this is a Confluence or a Jira issue.

I got a "hint" from Confluence today when I published a minutes of meeting page that an automation could be created that will create a Jira issue automatically when the page is published.

I created my automation and the Jira is created in the project backlog with the right description based on the task text, but the person who was mentioned in the task is not the assignee of the Jira issue, it stays as "unassigned".

The user in the task mention does exist in Jira and is a team member of the project. The assignee in the Automation is set to Automatic because it should be dynamic based on who is @ mentioned in the task as far as I can read.

There are no errors in the Audit log for the Confluence automation, it shows successful.

Any ideas

[Danno · Accepted solution]

You will have to check the details section in project settings for the project you are creating the task in to see what the default value is for new tasks, otherwise you will need to specify ythe assignee in the automation.

[Tim]

Thanks, Danno. The default assignee is Unassigned  (our preference). But then what is the point of @ mentioning someone in the task if I later have to manually assign it also in Jira?

[Tim]

Thanks, Danno. The default assignee is Unassigned (by purpose). But then what is the point of @ mentioning someone in the task if it does not assign that person to the Jira?

[Danno]

The @mention only assigns an Action Item in Confluence. You can create an assigned Jira task by highlighting the text of the Action Item and selecting create task vs. comment.

[Tim]

Ok, thanks. It was the Atlassian AI that "suggested" that I create Jira's out of tasks. Maybe for some it works ok, but for me it doesn't make sense if I have to eventually go into the Jira and assign someone when I already mentioned them in the task. But, not your problem :)

Thanks.

[Stijn · Accepted solution]

Hi Tim,

Sorry to revive this topic, but I was looking into the same thing and got it to work.

You can use the smart values "{{task.assignee.accountId}}" in the assignee field to asign the new Jira ticket to the person that was "@-mentioned" on the task.

I created this automation to do exactly that. It creates a task, assigns it to the mentioned person and I added the link to the Conlfuence page in the task description for convenience.

Hope it helps.

[Tim]

Hi @Stijn ,

Thanks for posting the solution! Never a problem reviving a topic when there's a better answer available :)

I tested it and it works great! I even went a little further and tried to find a way to put the due date as well (important for us). This way we don't have to edit the Jira manually. It seems that you have to use "plusDays(1)" or it will put the due date one day earlier for some reason. I just added the /Action Item (for the task), @ User and then //date and the automation added the correct due date to the Jira.

Thanks a lot for your advice!

Tim