Dear all, We find a wierd issue in our customer Jira cloud instance. * We have a USER1 who is a reporter of an issue * User1 has all necessary permission to be aasignable to any project and any issue * User1 is reporter of an issue * If an other user try to assign an issue to a USER1 who is already the reporter of that issue, then USER1 is not part of allow ist of users from Assigne user picker list If we remove USER1 as a reporter, then we are allowed to assign USER1 to the issue. Question : Is this a particular behaviour of Jira cloud that user as repoter can not be assign to the issue they are reporter ? We did not find this behaviour in Jira DataCenter Thanks for clarification regards

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

User cannot be assigned to an issue if he is already a reporter

serge calderara

Dear all,

We find a wierd issue in our customer Jira cloud instance.

We have a USER1 who is a reporter of an issue
User1 has all necessary permission to be aasignable to any project and any issue
User1 is reporter of an issue
If an other user try to assign an issue to a USER1 who is already the reporter of that issue, then USER1 is not part of allow ist of users from Assigne user picker list

If we remove USER1 as a reporter, then we are allowed to assign USER1 to the issue.

Question :
Is this a particular behaviour of Jira cloud that user as repoter can not be assign to the issue they are reporter ?

We did not find this behaviour in Jira DataCenter

Thanks for clarification

regards

Accepted answers

Nic Brough -Adaptavist-

No, that's not how Cloud works either, the assignee field does not care if someone is logged as the reporter. In fact it's a common practice to set the assignee to the reporter when an issue is resolved, so they can confirm and close it off.

I'm not able to replicate this on my Cloud service, which suggests you have some form of customisation doing it.

All comments

Nic Brough -Adaptavist-

I'm not able to replicate this on my Cloud service, which suggests you have some form of customisation doing it.

serge calderara

Hello @Nic Brough -Adaptavist- ,

what do you mean by sorte of customisation ?

What is strange is that we noticed it happens only for a particular user

We have check project permission and roles between an other same user in the group and all is the same.

Any idea where I could check ?

Nic Brough -Adaptavist-

I mean that you've added something to your system that enables this behaviour and then used it!

Interesting that it's only for one user though.

For debugging it, I would want to see all of the rules in the permission scheme for "Assignable user" (i.e. what groups/project roles/dynamic roles/fields/etc are set to get assignable user) and then how this one user matches any or all of those rules.

The only time I'd expect to see a user dropped out of the assignee list like this is if they are already the assignee, in which case, their id just moves to the top of the list and is the default (rather than appearing part way through the possible assignee list)

Nic Brough -Adaptavist-

Oh, and also, I'd like to know if it happens for different assignERS and what the exact occurrences are.

Let's say your user is Bob. Bob reports issue XYZ-123 but does not assign it. Bob looks at XYZ-123 and clicks Edit. Is Bob offered their own name in the list of possible assignees? Cancel the edit and then try "assign issue". Again, is Bob listed in the possible assignees?

Now you log in and go to XYZ-123, and repeat the edit and assign tests - are you offered the option to select Bob in either of them?

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud