...
Directive Values - This is a list of Custom Field values that have been set by the Script. e.g. using
resultMap.set('labels', "label1,label2,label3,label4");
Script Output - This is where the Print values are output, allowing for additional information to be displayed. e.g. using
print(`Body: \n${message.getBody()}`);
Script Evaluation Time Metrics - This is used to identify how long it took to evaluate the script against the selected Test Case.
Available Script Context
The another ticket with different subject βATH201125 β405034 β Visit Early Termination (A)β. It is showing in the auditing page but the subject was never processed & new created was not created , that is what I mentioned instead of creating new ticket , the existing ticket TDAS-55011 was commented. API | Notes |
---|---|
| Get body content of email. Not available for preprocessing task. |
| Gets the Subject content of email. |
| Get all headers of a message. |
| Get value of a message header Parameters
|
| If the email being processed is commenting on an existing issue, then this context will contain the field values for the related issue. Allowing for this data to be used within the Script. Format used is as per the Get Issue response from the Jira REST API. Note: This is only available within the Script Custom Field default and the Script Field Processor. For more info about using Issue Data see: https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/pages/3861676043/Manipulate+Issue+data+in+Scripting+features#Showing-the-JSON-object-Values-and-structure |
| Adds output that is recorded during execution and shown in the processing report. Parameters
|
| Set the processing outcome of the script Parameters
Note: |
| Used to set issue field values. See Map - JavaScript | MDN for usage. |
| Searches within string values for matching content. See RegExp - JavaScript | MDN for usage. |
Script Examples
See the following page for some example use cases: Use Script Field Processor
...