nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Subtask Automation won't assign assignee

Calvin

hi all, i have an automation that creates a subtask, in that subtask create it adds "Summary", "Description" "Parent" and "Assignee".

But for some weird reason, the subtask still says "unassigned" it gets created as expected, it looks good, but its unassigned? I have no idea why? There is no error, logs say "issue created successfully" I just don't understand why it would be empty.

Accepted answers

Staffan Redelius

Hi @Calvin

Could you please post a screenshot of how the rule is defined, and also a a screenshot of the log so it is easier to see what happends when the rule executes?

Does the user have the permission "Assignable user"?

All comments

Gee Espiritu

Hi @Calvin have you tried to add another action like edit work item fields then add the assignee there? just another layer to check if there will be another that will come from "assignee" field.

Staffan Redelius

Hi @Calvin

Could you please post a screenshot of how the rule is defined, and also a a screenshot of the log so it is easier to see what happends when the rule executes?

Does the user have the permission "Assignable user"?

Calvin

Thanks mate, we have a system account and turns out someone played around with how the access groups have been set up in the backend. And they removed the system account out of the correct group which removed the "Assignable user" privilege.

Interestingly though this didn't flag any error in my automation.

Gee Espiritu

Thanks, @Staffan Redelius and @Calvin

Now I have something to add on our knowledge base of error that we may encounter.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

automation