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

Read-only custom fields for new Issue View

Oleg Polivannyi

As I understand, Jira migrating to new Issue View, where you can view, edit, transit issues, etc.

Before it was a known way to restrict editing of some field, placing it on View Screen, but omitting it on Edit Screen. How to achieve this behavior nowadays?

Links:

Comments

Tuncay Senturk _Snapbytes_

This is an interesting discussion.

@Oleg Polivannyi, could you please clarify more? Maybe screenshots, articles.

Thanks

Oleg Polivannyi

Added links section to initial post

@Oleg PolivannyiI've turned off the New Jira Issue View, I've been asked then, what's the reason.

And I've replied that due to this bug (no read-only fields anymore) I cannot work properly.

I recommend you to do the same unless you've already figured out how to fix this.

But this applies to my user only :-(

Anyone else would still be able to inline edit read-only fields :-(

Welcome!

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

Quick Links

Find more posts tagged with

custom-field

jira

jira-administration

restriction