Scriptrunner behavior plugin - removes read-only fields when user changes "Configured Fields" settings

[Rami Bechara]

We've configured a specific custom field to be readonly in Scriptrunner's Behavior plugin.

We started noticing that for some issues, the value for the readonly field is being deleted. The issue history shows this action as a regular field edit operation (ie. it wasn't a Move or something else)

We discovered that the readonly custom field in question is being blanked out, whenever a user goes into Edit Issue mode and then clicks on Configure Fields to change the default field selection. If the user customizes the fields, and adds the readonly custom field to his field selection, this field is blanked out but stays un-editable.

And when the user commits his other unrelated changes, the value of the readonly field is then lost.

We're running JIRA 6.4.12 and the latest Scriptrunner version 4.1.3.16

Any ideas why this is happening ?

This is the XML for the field configured in Behaviour:

<config use-validator-plugin="false" name="ExternalissueIDReadOnly" description="Make External IssueID readonly" guideWorkflow="null">
<field id="customfield_11904" required="null" readonly="true" hidden="null"/>
</config>

[JamieA]

This is not handled at the moment - https://productsupport.adaptavist.com/browse/SRJIRA-233

Some users have disabled the Configure Fields dropdown using javascript, but I don't have the details of how.

[Florian Fahrenberger]

I've encountered some problems as well with the "Configure Fields" dropdown, namely the default Description via Behavior will replace anything within the description field when the dropdown is applied...

I am trying to catch this within the script, but can't figure out what to look for. Things like getFieldChanged(), getActionName(), and underlyingIssue?.description don't give any reasonable result (Null pointers or "Create", just as if the screen just popped up). Do you have any good guess on how I might try to see that the "Configure Fields" dropdown has just been applied by the user? That would be of great help to create a workaround for this issue.

[JamieA]

Not really... I guess when we start working on it we'll know how to do it... nothing I can share at the moment. I doubt you will be able to fix this issue using the current API.

[Viacheslav Starovoytov]

I also met this behavior when I tried to change fields displaying. I hid the field by using of Behaviors, and it appeared when I was customizing fields view. I could be able to change a value of the field. And then it disappeared again.