-
Suggestion
-
Resolution: Unresolved
-
None
-
None
When using the official connector for Slack, Jira sends wiki markup formatting to Slack, which is unable to properly render it.
With that said, it would be great to have the ability to disable the wiki markup parsing on the integration.
- mentioned in
-
Page Failed to load
[API-1] Disable the wiki markup in the Slack connector
| Remote Link | New: This issue links to "Page (Confluence)" [ 1013482 ] |
"Under Consideration" from February...
| Under consideration | This issue is a strong candidate for our roadmap. We’ll follow up on it in a few months time. |
any updates?
| Workflow | Original: JAC Suggestion Workflow [ 3097175 ] | New: JAC Suggestion Workflow 3 [ 3588352 ] |
| Component/s | New: Jira Cloud for Slack [ 55793 ] |
| Key | Original: JRACLOUD-71067 | New: API-1 |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 3008420 ] | New: JAC Suggestion Workflow [ 3097175 ] |
| Project | Original: Jira Cloud (including JIRA Core) [ 18514 ] | New: Atlassian Product Integrations [ 20010 ] |
| Status | Original: Open [ 1 ] | New: Under Consideration [ 11774 ] |
| Assignee | New: Trevor Thompson [ tthompson3@atlassian.com ] |
| Description |
Original:
When using the official connector for Slack, Jira sends wiki markup formatting to Slack, which is unable to properly render it.
With that said, it would be great to have the ability to disable the wiki markup parsing on the integration. |
New:
When using the official connector for Slack, Jira sends wiki markup formatting to Slack, which is unable to properly render it.
With that said, it would be great to have the ability to disable the wiki markup parsing on the integration. !message.png|thumbnail! |
| Attachment | New: message.png [ 332503 ] |
Good News! We made some progress here. We just pushed a change that will fix the tags from coming through in your Slack messages (unfortunately, we are unable to set colors of text in Slack). I missed the bit about panels and it does appear that those are still coming through in the message, so we will tackle that in a subsequent change. Thanks for your patience and keep the feedback coming!