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

Why in View screen associated with "view issue" operation edition of fields is allowed?

Begoña Bonet

I have defined a Screen scheme with 3 screens:

Vista for issue view operation
Edición for issue edition operation
Crear for issue creation operation

Vista has the same fields/customfiels as Edición. When I'm in Vista screen (making view issue operation) JIRA allows me to edit every field. I thougth that in "view issue operation" edition is not allow? I´m wrong? How can I forbiden the edition of fields in "Vista" screen?

Accepted answers

All comments

Nic Brough -Adaptavist-

This is the "inline edit" function that lets you quickly change fields without having to leave the view screen.

The function respects the settings in your "edit" screen, so if you remove fields from edit, they will no longer be editable in view.

There's a request to be able to partially or totally disable inline edit if you want to watch/vote on it: https://jira.atlassian.com/browse/JRA-29091

Begoña Bonet

Thanks, now I understand how JIRA works in that sense. I've voted JIRA-29091

Begoña Bonet

Only one question more..... the "inline edit" function doesn't take into account the Behaviour defined for fields? For example, I can edit in "view Screen" fields that appears in "Edition screen" even when I've defined them as "Readonly".... Is this right for "inline edit" function?

Nic Brough -Adaptavist-

You can't define a field as read-only in Jira unless it's a genuine read-only field (can only be set by code) or a field you do not put on Create, Edit or Transition.