nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Description Field Formatting From Slack Automation not taking effect in Jira

Michelle Bantugon

I tried the **text** but it does not bold my text in Jira but when I tried to edit it in jira worked. Is there a way for it to work automatically coming from Slack workflow?

Accepted answers

All comments

Lucas Knorr

Hi @Michelle Bantugon

did you try to use only one * like: *text* ?
This should create the bold format according to this guide: https://confluence.atlassian.com/jirakb/text-formatting-notation-in-jira-cloud-1375863133.html

Michelle Bantugon

I tried that too but it does not work

Michelle Bantugon

It's weird that when you edit it in the description field like retyping the ** it worked but when coming directly from slack automation form it's not.

Bill Sheboy

Hi @Michelle Bantugon -- Welcome to the Atlassian Community!

I just tried *here is bold text* with both software and JPD projects and it worked, as described here: https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all

This was using the default Jira / Slack integration from Atlassian. Are you using a different tool to connect them?

Kind regards,
Bill

Michelle Bantugon

No. I created a jira issue from slack workflow automation but it does not work. I tried different formatting but it was still appearing the same format (see ss below) from Slack to Jira description field.

Screenshot 2025-02-04 at 2.27.46 PM.png

Bill Sheboy

That is odd... I used the "/jira create" from a channel for the issue, entered the formatting, and it saved as expected.

Perhaps check with your Jira Site Admin to learn which connector is being used (under Your Apps), and check with the specific vendor to see what they say.

Michelle Bantugon

Thanks @Bill Sheboy for checking this issue. Could you further elaborate on the connector you mention on the previous comment? Yes, I might need to ask our jira admin for this

Shawn Oster_asl6gj

Unfortunately I don't have an answer, but I am seeing the same thing using the JIRA Cloud integration via the Slack Workflow Builder.

Using `/jira create` doesn't go through the same workflow/process that the Workflow Builder does so trying to debug or shortcut investigation using that approach won't surface the bug. You must instigate it from Slack's Workflow Builder with the JIRA Cloud integration.