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)?
Hi @Meinhard
Welcome to the community!
If it's a company based project. use the old way it's set up in the issue screen scheme. Have a separate view screen and edit screen configured. Then if the custom field is not in the edit screen, you will not be able to edit the custom field.
I hope this helps.
Hi Fabian,
I just started using a free Jira account. When I set up a company managed project and follow your step it works. When I do this at work (using the company Jira account) then it doesn't work. I guess I have to dig a little bit more to find out what is going on.
Thanks for your help.
Regards,
Meinhard
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join us to learn how your team can stay fully engaged in meetings without worrying about writing everything down. Dive into Loom's newest feature, Loom AI for meetings, which automatically takes notes and tracks action items.
Register today!Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.