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

Team field read-only

Nico Maikranz

Hello Community,

I want to use the native atlassian team customfield in my service management project.

I want this field to be read-only in the beginning so that I can update it via jira automation because we need to "migrate" from a own single-select team field to this new one.

When adding the atlassian team field to my projects view screen it can still be updated.

Does anyone know if this is normal behavior or a bug? Other customfields added only to a view screen are working as read-only fields.

Thank you

Nico

Accepted answers

Christos Markoulatos -Relational-

Hey @Nico Maikranz

What you're seeing is expected behaviour rather than a bug. The native Atlassian Team field is a platform level field that you enable through the issue layout, not through the normal Create, Edit and View screens, so the usual read-only trick of adding a field to the View screen but leaving it off the Edit screen simply does not apply to it. There is no Edit-operation screen to remove it from, which is why it stays inline editable while your other custom fields behave as read-only, and that is working as designed rather than misconfigured on your side. The good news for your migration is that editability has no bearing on your automation, so your rule can write to the Team field regardless of whether users can also edit it, and the move from your old single-select field will work fine. One thing to note, if you use a workflow post function rather than a normal automation action, you need to pass the Team UUID rather than the team name or it will error. There is no native way to lock this field as read-only in Jira Cloud today, so the cleanest approach during the cutover is to let your automation be the source of truth and have it correct any manual changes, then retire the old field once everything has migrated. If you want Atlassian to confirm the behaviour for your instance or point you at any open feature request to vote on, raising a support ticket is the best path.

Hope this helps!

Helpful links:

Teams in Jira projects (enabling and automating the Team field): https://support.atlassian.com/platform-experiences/docs/using-atlassian-teams-in-jira-projects/

How to make a field read-only in Jira Cloud (for standard custom fields): https://support.atlassian.com/jira/kb/how-to-make-a-field-read-only-in-jira-cloud/

All comments

Christos Markoulatos -Relational-

Hey @Nico Maikranz

Hope this helps!

Helpful links:

Teams in Jira projects (enabling and automating the Team field): https://support.atlassian.com/platform-experiences/docs/using-atlassian-teams-in-jira-projects/

How to make a field read-only in Jira Cloud (for standard custom fields): https://support.atlassian.com/jira/kb/how-to-make-a-field-read-only-in-jira-cloud/

Nico Maikranz

Hi @Christos Markoulatos -Relational-

thanks for your detailed answer. That helps me a lot.

Best regards

Nico

Christos Markoulatos -Relational-

Happy to help @Nico Maikranz if u need anything else ask.

Tomislav Tobijas

Hi @Nico Maikranz ,

Are users only able to access the dropdown or also edit the value? I'm asking as there's this known issue around this: JRACLOUD-82368: Team field should not be Editable when removed from Edit screen

Cheers,
Tobi

Nico Maikranz

Hi,

its the same behavior as described in the issue https://jira.atlassian.com/browse/JRACLOUD-82368

the field is only added to the view screen and the field is editable.

Thanks.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-service-management