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

Automation is failing for Read only fields in Jira cloud. Please find the details.

thumuluru.shreya

Hello Team,

We have multi select custom field, based on that field values we are auto updating 3 read only custom fields.

But automation rule is failing with below errors.

Edited work item successfully, however some of the set fields aren't available. Fields ignored:
User-Not Applicable (customfield_16419), User-Acceptable (customfield_16420), User-Actions Completed (customfield_16418)

Similar automation is implemented in other work type and its working fine. Same kind of rule is not working here.
We have single screen for both edit and view screen. and added above fields in that screen.

Accepted answers

All comments

Walter Buggenhout

Hi @thumuluru.shreya,

Can you provide details on how you make these fields read only. If you say you use the same screens for edit and view, the screens are not what makes the fields read only. So I am guessing you are either applying workflow properties or the field configuration to make them read only.

Having said that, automation does respect the settings you apply to fields. If you make fields read only, they will be read only for automation too and you won't be able to update them through an edit action.

You'll rather have to script or API-call a way around that or update your edit / view screens and allow updating the fields through a workflow transition with a bespoke workflow screen with just those fields on them.

Hope this helps.

Marc -Devoteam-

Hi @thumuluru.shreya

You mention these fields are on the screen, but how are the context of these fields set.

As you also mention it works on another work type, this tiggers the context option for me. As it seams the fields might only be available for a certain work type.

Prathap DL_66helr

Hi @Walter Buggenhout

I'm replaying on behalf of @thumuluru.shreya

We have created read only type custom fields. and added those custom fields to Edit screen and view screen. (Single screen for both edit and view)

We are not applying any properties.

Prathap DL_66helr

Hi @Marc -Devoteam-

It worked on another work type means; we have similar kind of automation in other work type and there we are not seeing any issue. there also updating read only fields based on other field value changes.

Only We are facing issue with below fields

These fields are Read only type custom fields we created and added in Edit and view screen. These fields should be updated through automation only. user can't fill it manually.

When value changes in multi select custom field then automation should trigger and update the below read only custom fields automatically.

User-Not Applicable (customfield_16419), User-Acceptable (customfield_16420), User-Actions Completed (customfield_16418)

Marc -Devoteam-

Hi @Prathap DL

Custom fields have a default context set, contextt can be modified or added.

Custom field context can define if a context is based on project or multiple projects or work item types or multiple work item types.

As you mention, it works on a different work item type, check the contexts of the custom field.

https://support.atlassian.com/jira-cloud-administration/docs/configure-custom-field-context/

Walter Buggenhout

I do not have a test setup in place where I can immediately replicate your use case. Documentation seems a bit inconclusive as well, but this custom field type seems to be a concept introduced at some point to support import scenarios from Mantis, a another JSM solution, into Jira.

While I can't find any immediate documentation on cloud, this support article on Jira Data Center explains how the field can be updated through the REST API. In cloud, most references I can find mention that this type of field can not be update through automation once it has a value. Which seems to make sense, as read only does quite strongly suggest editing would not be allowed.

Prathap DL_66helr

Hi @Marc -Devoteam-

I set project and issue type context. Still facing the same issue.

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