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; } } }

Issue assignment to a team

Jira Softera

Hello,

We're facing a problem after Jira upgraded to 8.16.0 version. Users noticed, that after assigning issue to a team it still shows up in worklog as unassigned issue. Before the upgrade issues were visible only for users, who are members of a team, to which it was assigned.

Accepted answers

All comments

Nic Brough -Adaptavist-

You do not assign issues to a team, you assign them to a single person.

An unassigned issue is one that has no assignee set.

In Advanced roadmaps, you can associate a team with an issue, effectively saying that the issue needs to be dealt with by that team, but that's still not an assigned issue.

Check the "unassigned" issues assignees, I expect you'll find them to be, well, unassigned, missing a named person in the assignee field.

Jira Softera

Thanks for an answer.

Maybe I didn't formulate question correctly. What I meant was, when you associate team with an issue, it used to disappear from the worklog filter.

Nic Brough -Adaptavist-

What worklog filter?

Jira Softera

When a worker looks for issues, he can choose filters:

If he uses My open issues filter, he also sees issues, which are associated but not assigned.