Word Export: Organizations and Request Participants field values are not displayed

Summary

When exporting an issue to Word format(either from Issue Navigator or directly on the issue), the values for the "Organizations" and "Request Participants" fields are not displayed in the resulting .doc file.

Environment

• JSD Cloud

Steps to Reproduce

1. Create a test issue where a reporter

Expected Results

• In the .doc file, the correct values for the "Organizations" and the "Request Participants" fields are shown

Actual Results

• This is an export of an issue where the "Organizations" and "Request Participants" fields have a value set:
  

Notes

• As long as the "Organizations" field or "Request Participants" field has a value set, the exported .doc file will not have the values shown as blank.
• This bug applies to portal, email or JSD originated issues
• The behaviour when the "Organizations" and "Request Participants" fields don't have a value set is correct, the field values are displayed as "None"
  

Workaround

• It's possible to create custom fields and create a workflow post function to copy the field values on transition and have the data displayed in the custom field instead of the original fields
• The post functions can be added to as many transitions within a workflow as required
• For "Request Participants", a "User Picker (multiple users)" custom field can be used
• For "Organizations", a "Text Field (multi-line)" custom field can be used
•  Example custom fields:
  
  
• Example post function on a transition:
  
• Example exported .doc file:
  
• Notes: the field will only update when the issue is transitioned(and a post function exists)
• It might be possible to use a jira:issue_updated webhook to listen for events and then use REST API to fetch/copy(update) the relevant fields.  Please keep in mind that third-party development is outside of our standard support scope and we are unable to provide assistance with scripting.  For more information, please see:
  • JSD Cloud REST API
  • Jira Cloud REST API
  • ScriptRunner for Jira has a "ScriptListener" feature which allows a script to run when a webhook event has been triggered. ScriptRunner is supported by the add-on vendor - Adaptavist.