1 answer
- 10-1
Do you need to update the fields (or not)?
- Asle Kristian Andersen
Exalate scripts should update fields, but ticket agents on the receiving side should not. To them the fields are read-only.
- Francis Martens (Exalate)
That's a bit of a head scratcher.
The fields must be editable on the create/edit screens such that the REST api provided by Jira are allowing an update of the field.
But by adding these fields to the forms, agents can modify the values, which against your requirement.
Is my statement correct and if it is, I'm not sure if there is a solution - Asle Kristian Andersen
Fair enough.
If there is no option through the REST api to update read-only fields, then that would be a limitation that we have to work with and adjust scope accordingly.
Maybe it is sufficient that agents seemingly can update fields, but we don't syncronize them back to the remote issue. And when a new sync happens the changes is overwritten by the original values from the remote issue.
- Francis Martens (Exalate)
ok - that might be an option indeed.
Add your comment...
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.