We are importing data from another system into Jira through the API. There is one field that should be visible but a user must not be able to edit it (this applies to all users/roles/groups).
Prior to "issue layout"
The screen scheme would be used to have two different screens for view & edit. The "view" screen would include the field and the "edit" screen wouldn't include the field.
With "Issue layout"
Now "issue layouts" are based on the view/edit screen. The differentiation by 'action" (~ view, edit) is gone.
Question
Is there a way to support this use case (field X is visible in view, but can't be edited)?