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

[Brent]

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?

[John Funk · Accepted solution]

Hi Brent,

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

[Brent]

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

[Sebastian Penhouet]

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

[John Funk]

@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

[Sebastian Penhouet]

Hi @John Funk maybe you copied the wrong link? The issue you linked is unrelated to the issue described here.

[John Funk]

Then I am not aware of another open feature request. :-(

[Sebastian Penhouet]

Hi @John Funk 

can you open one then?

Best regards,
Sebastian

[John Funk]

Here ya go:

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

[Sebastian Penhouet]

👍 thanks

[Katarzyna]

Hi,

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

[Sebastian Penhouet]

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

[Katarzyna]

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]

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.