In a Jira Service Desk project I have created a custom field of type Text Field (Read only). I update this field by means of a ScriptRunner script that runs when an issue is updated.
I am displaying the custom field on an Edit Issue screen, but the field can be edited (as a string).
If this field is meant to be read only, why is it possible to edit it?
How can I prevent this?
Hi Nick,
Thank you for your response.
I can confirm fields shown inside of Jira Service Desk are only shown read only in the Customer Portal and this means they will not be shown as Read Only when displayed on the edit screen in the standard Jira view.
This means you will need to remove the field from the Edit Screen as this behavior is the default behavior of Jira Cloud and that this behavior is no caused by ScriptRunner for Jira Cloud.
Also I can confirm that the plugin cannot make fields read only like it can in the server version can with the Behaviors feature.
The reason we are unable to provide this functionality is due to the restricted functionality and API's which Atlassian provide inside JIRA Cloud, due to the fact that Atlassian only provide a Rest API in Jira Cloud and not the same Java API that the server version contains.
You can see more detailed information on the differences between ScriptRunner for JIRA Cloud and ScriptRunner for JIRA Server inside of the documentation page located here.
I hope this information helps.
Regards,
Kristian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.