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

Cannot inline edit the Assignee field on some issues

Michael Thompson

We recently upgraded Jira Server to version 9.3.0 and have been experiencing some odd issues.

In one of our projects (possibly others), users are not able to inline edit the Assignee field from the issue View screen, but only for some issues. I have been able to reproduce the problem as a Jira admin, so it is not a restriction on users. I have also confirmed that the Assignee field is part of all screen schemes used by the project.

There doesn't appear to be any pattern to which issues have the problem, and I do not get any pop-up messages recommending a re-index. Any ideas what could be happening?

Accepted answers

Michael Thompson

Oddly enough, the solution to the problem was even more basic than expected. The solution is to clear browser data (browsing history and cached data), restart the browser, and go to the View screen to try an inline edit to Assignee. I and several of my users tested this and successfully performed an inline edit on issues we formerly could not.

I would think the problem would be more global than a few random issues, but such is life. Thank you to Tim and Nic for your great input!

All comments

Tim Perrault

Hi @Michael Thompson

Do you have any plugins in your system? Specifically Scriptrunner. I know that Scriptrunner behaviours will disable in line edit.

Tim

Michael Thompson

We do have a number of plugins in our system, especially ScriptRunner. However, we do not use any behaviors on the Assignee field, and this problem only started after the upgrade to 9.3.0.

Also, If it were Scriptrunner behaviors disabling inline edit it would affect all issues, not just a random set of issues.

Thanks for the input!

Tim Perrault

Best thing to do then is tail the log file and recreate the issue. That should at least help you narrow down where the issue is.

Nic Brough -Adaptavist-

Have you checked the "can assign issues" permission for the project? Could it be that the users who can't inline edit do not have the permission?

Also, it's possible to adjust permissions inside workflows, changing the users and groups who can assign issues depending on status, could it be that?

Michael Thompson

Hi Nic,

This is the weird thing. All the users in question do have the "can assign issues" permission including myself (and I am in jira-admins). They are able to inline edit most but not all issues in the project. I was able to proxy into the user account (using ScriptRunner) and reproduce the problem on 1 of 3 issues. I then switched back to my account and reproduced the problem on the same 1 of 3 issues.

All of the issues in question are using the same workflows and permission schemes.

Nic Brough -Adaptavist-

I'd look next at the workflow and users combined - as I said, you can apply status level permissions which could be causing this.

Michael Thompson

I would think the problem would be more global than a few random issues, but such is life. Thank you to Tim and Nic for your great input!

Tanu_ik3gvh

+1
I am facing exactly same issue as @Michael Thompson after upgrading to version 9 . Is there a fix ? or its a bug in version 9+

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server

inline-edit