User can’t edit fields when they are in the sidebar?

Question

Hi community!

I’m having a very strange problem. A user let me know they weren’t able to edit some fields in issues in their project. I checked permissions and roles and those seemed normal, the same as other users in the project who WERE able to edit those fields.

Finally I asked if they could edit the description field and they said yes, and it occurred to me that all the fields they couldn’t edit were in the issue view sidebar.

So I moved one of the fields from the sidebar to the main body of the issue view, and now they can edit it.

Any theories as to what’s going on here?

G subramanyam · Answer

Hi @corey.r I'm actually of the similar thinking while I replied to your post. I'm not sure, I can think of other options at this moment. If not already, could you please reach out to Atlassian support just in case they might shed more light on the situation!

corey.r · Answer

Thanks, I’ll definitely do that.

If you can think of any ways in which changing the location of a field in the issue view could affect those permissions, that would give me something to investigate. Because as far as I can tell, without making any other changes, simply moving the field was all it took to make it possible for the user to edit it.

And that seems super weird to me.

I really appreciate your input here. Thanks so much.

G subramanyam · Answer

Hi @corey.r thank you for quick reply and clarification. As far as my knowledge is concerned, "edit issues" permission allows people to alter the summary and description, and change the value of fields that aren’t restricted by another permission (like the Assign issues, Modify reporters, or Schedule issues permissions). This permissions also allows people to convert issues to subtasks or vice versa.

Having said, edit permission may depend on product access to be useful:

* In software projects, people must have product access to Jira Software to use this permission.

* In business projects, you may grant this permission to anyone logged in to your Jira site

I would suggest to have a check with that user permissions or recent changes happened in the backend for that user.