Note
We've packed up and moved from Confluence to Discourse to bring you a better, more interactive space. Out of courtesy we didn't migrate your user account so - you will have to signup again
The Exalate team will be on holiday for the coming days - returning Jan 4
Enjoy & stay safe
With the new issue-viewer in Jira Cloud, we have a few problems with text fields that should not be updated by agents in Jira Service Desk.
There is a text field type that is read only in customFields, but it doesn't prohibit agents to inline edit them in the new issue view.
We have tried to remove the fields from CREATE and EDIT Screen operation Screens and leave it on the VIEW operation screen - which works in the new issue screen - the fields can't be edited, but neither can Exlatate scripts, which throws an error that the customField is not on a valid screen - problably refering to Create or Edit screens.
Anyone struggling with a similar case? How to implement read only fields that is only given content by remote issue.