Why is my automation trying to assign to a user that doesn't exist?

[Danno]

I'm using Cloud Premium and have an automation that is failing. I want it to assign to a user in a role and it is failing with this message:

Error assigning issues

PRS-1978: (User 'rk:1bbb7c4d-929b-4b89-b108-a912d6937601' cannot be assigned issues. (assignee))

I do not understand why the user code is formatted this way although it looks like a user code I have from an outside email domain. I also cannot decipher who this user would be. I don't know what portion of the code to use.

Can someone explain how to solve this issue?

[Robert Cavanna · Accepted solution]

If you can identify those areas by Component, you can build out the JQL for each team's board to include issues with their specific components. Those logging incidents would have to assign the component. You may also want a dashboard that shows incidents without components as they will need to be triaged before they show up on the team boards with component-specific filters.

[Bart Meerveld]

Our scrumteams are still starting up, the components haven't been divided that sharp to know. So that's unfortunately not an option now, but something we strive for in the future. The dashboard is a solid idea though, thanks!

[Nic Brough -Adaptavist-]

To do this, you need a method to identify which issues need to be included in a board and use it in the JQL filter for the board.

I don't think there's a way to do it quite so arbitrarily - there has to be something you can filter on, and as a JIRA issue is essentially a collection of fields and information about it, it has to be something in there, and it's only logical that is is a field (unless you can come up with some other rule that works off existing information - project, issue type etc).

You might have some success with labels instead of a drop-down custom field, but I don't think there's another approach.

[Bart Meerveld]

Thanks Nic, that's what i was thinking.