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

In a Next-Gen Project, is there a way to make a custom field read-only?

In this case, the field (we'll call it Field #3) is populated via an automation which takes the input of two other custom fields (Fields #1 and #2), does a mathematical computation, and outputs the result as a numerical value in Field #3.

However, once the value is updated, you can change it manually, which is bad. Since this value is being used elsewhere, it needs to stay the result of the computation. Therefore, I want to make Field #3 read-only.

Any thoughts?

Accepted answers

Hi Brent,

No, you cannot make a custom field read only in Next-gen.

All comments

Hi Brent,

No, you cannot make a custom field read only in Next-gen.

Thanks for the quick answer. Next-Gen strikes again I guess.

Sebastian Penhouet_c5nt77

@John Funk Is there already an open ticket for this missing feature?

@Sebastian Penhouet - I am not sure as I don't really use Team-managed projects.

And not sure if this covers it, but here is an open request:

https://jira.atlassian.com/browse/JSWCLOUD-17336

Hi,

Please vote for this issue: https://jira.atlassian.com/browse/JSWCLOUD-20905

Sebastian Penhouet_c5nt77

Hi @Katarzyna I don't see how the issue you linked has something to do with the problem described here.

Currently, in next-gen you can't use global custom fields. So to make them read-only, Atlassian must add support for custom fields firstly.

Sebastian Penhouet_c5nt77

There are already custom fields in next-gen projects (just not global ones). For them to be read-only they do not need to be global.

Welcome!

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

Quick Links

Find more posts tagged with

custom-field

cloud

jira-software

jira-software-cloud

next-gen