I'm trying to create a variable that gets the field value as it appears in
https://my jira.atlassian.net/rest/api/2/issue/ikey-180231?expand=names
for example the field :
From JIRA the issue appears without the new line chars.
I tried using the following with no luck {{LW_EscalationData2.replaceall("(\r\n|\r|\n)","\n")}}
it always retrieves my variable as a single line without the new line char.
Hi @david_levy
When you note:
...it always retrieves my variable as a single line without the new line char
How do you know that?
For example, if you are writing that field to the audit log, the newline and carriage return characters will not display. The log view appears to display them as a single space.
Perhaps if you post your entire rule and audit log details showing the rule execution, those will provide more context. Thanks!
Kind regards,
Bill
I have a string in a multiline field (as seen above) and I want to send it via webservice.
I found out that I could not send multiline in webservice so I created a new simple text field with the same text and I sent it via the webservice but I got an invalid string error all the time.
When I set explicitly the message with the new line chars in the Jason body, it can send it through.
The automation:
The audit log:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that information, David.
Rather than moving the data to another custom field, have you tried using one of the encoding functions on the original multi-line field and then sending that in the message? That should preserve the characters using the relevant protocol.
https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#Encoding
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, Bill,
I tried the {{issue.summary.jsonEncode}} and it works as you suggested.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.