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

Admin cant assign user to certain issue but can on other issues of the same project

Nicolás Macció

Hello, sorry for my bad english, we are having a really weird case in my job. Me and 2 other users are admins in jira.

We created a new project "WC", copied from a existing project "PD".

There are already 5 issues created in the project WC, the first three were created by me, the fourth by a normal user, and the fifth by me again.

The problem is: LS, the admin, wasnt able to assign the user issue to a user, she has the Assignee field uneditable, as if it was read only, BUT she can assign normally in the other 4 issues of the same project and in the same status.

Me and LL, the other admin, can assign that issue without problem, so its happening only for LS and only in that issue.

I have searched all internet and even asked chatgpt. Nothing makes sense, so here is my last hope.

Thanks you in advance

Accepted answers

Nicolás Macció

UPDATE:

Today we were going to make a test to make it work, changing the status and permissions of the issue, but when we opened it, sudenly there was no problem no more, now LS can assign that issue without problems, but we didnt change anything.

So i guess in the end it was just a weird bug/cache glitch of that day...

Leaving this answer here in case someone in the future gets the same problem

All comments

Natalya Ozhigova

Hi Nicolas,

Do you use any third apps, for example Scriptrunner? This app can regulate the field behavior depend on some conditions.

Also, I have several questions. Do you assign issue during transition, or just edit the work item?

In any case it is really interesting. Look forward to know the real cause.

Best regards

Natalya

Nicolás Macció

Hello Natalya!

Nope, there are no thrid apps, and we just edit the work item, it is not during a transition of status.The issue is created in the status "Ingresed", and when trying to edit the work item "Assignee" in that specific issue, The LS admin cant edit it, but she can on the other issues.

I'll notice you if we find a solution.

Thanks!

John Funk

Hi Nicolás - Welcome to the Atlassian Community!

Can you check the transition to the Ingresed status to see if there are any Properties entered?

Screenshot 2025-05-27 075820.png

Nicolás Macció

Hello

The first transition (when first created) has this property defined.

I dont really know what this does or what it means.
But again, the admin LS can assign on other issues of the same project, so it would be weird if a condition in the workflow only affected one issue

imagen (43).png imagen (42).png

Nicolás Macció

John Funk

Sometimes it can be a caching issue with the browser. Glad it is working for you now.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-service-management

jira-service-desk-data-center

jira-service-management-data-center