Send Slack Message formatting is not applied to the message

[Romans Averins]

Slack formatting does not work either from the `Send Slack` message input field or the `Create Variable` smart value field.

What I did:

1. Created `Lookup Issues` with JQL

2. Created `Create variable` and nested there {{#lookupIssues}} as listed below

• Variable name: bugIssues
• Smart value: {{#lookupIssues}} {{issueType.name}} - <{{url}}|{{key}}> - {{summary}} {{/}}

3. Created `Send Slack` message and pasted there {{bugIssues}}

All works great but without any formatting like bullet points (*) or newline \n for slack whether it is injected into the Smart value of the variable or the Send slack message field.

Therefore, all issues are just dumped in one message without separation.

Please point me on how to inject at least \n so each item from the `Smart value` of the {{#lookupIssues}} would be listed on a new line of the Slack message.

Side note: The current approach is used to have 2 types of Issues filtered and posted in one Slack message.

[Mariette Conning]

The following worked for me:

{{#lookupIssues}}• {{issueType.name}} - <{{url}}|{{key}}> - {{summary}}
{{/}}

Note the {{/}} is forced to be on a new line.

[Daniel Eads]

Hi @Romans Averins ,

The message created from Automation should follow Slack's markdown formatting - so to include a bullet point and newline in your message, this modification to your smart value should work:

{{#lookupIssues}}• {{issueType.name}} - <{{url}}|{{key}}> - {{summary}} \n{{/}}

Cheers,
Daniel

[Romans Averins]

Hey @Daniel Eads ,

Thank you for the response! This is exactly why the topic is raised as the `\n` is not working in this case.

Tried it in various ways, even {{\n}}, or {{/}} \n, etc. but still slack is not recognizing it in the way it should.

Hence, copy-pasted the suggested solution and it just prints out all in one line with typed \n in between.

[Jose Braga Neto]

Hi @Romans Averins,

Did you manage to sort that out? I'm having the same problem with the \n

[Romans Averins]

@Jose Braga Neto this approach worked out.

–––START OF MESSAGE–––

{{#lookupIssues}}
{{issueType.name}}

{{/}}

–––END OF MESSAGE–––

[Jose Braga Neto]

haha Legend, thanks!