Jira Cloud app for Slack: incorrect message text parsing

[Andrey Otto]

Hello! In our company we integrated Jira Cloud app for Slack. And noticed that not all text of message parsing for task creation.

To generate complex messages we are using Slack Notifier. Slack Notifier uses attachments property to add and display extra info inside slack message.

On this screenshot is message generated through slack api and structured by attachments.

I guess Jira Cloud App doesn't parse attachment parts of Slack message when I try create task in Jira.

The question/suggestion is: Is it possible improve Jira Cloud App in this way to parse all parts of message and put those parts to "Description" section while creating task for Jira itself?

Part of code how I create message with attachments (Python api for Slack)

client.chat_postMessage(
    channel=channel_id,
    attachments=[
        {
            "text": "This is an attachment",
            "color": "#2eb886",
            "fields": [
                {
                    "title": "Priority",
                    "value": "High",
                    "short": False,
                },
                {
                    "title": "Test",
                    "value": "Test values",
                    "short": False,
                }
            ]
        },
        {
            "text": "This is an attachment 2",
            "fields": [
                {
                    "title": "Priority",
                    "value": "High",
                    "short": False,
                },
                {
                    "title": "Test",
                    "value": "Test values",
                    "short": False,
                }
            ]
        }
    ],
)

[Martin Runge]

Hi @Andrey Otto

Welcome and great to have you in the Atlassian community!

The Jira Cloud app for Slack only reads the main text content when creating an issue. As a result, any information in the attachments blocks, including your fields and secondary text, is intentionally ignored. This isn't a configurable bug; the parser simply doesn't process the attachment payload.

Did you end up solving this in the meantime, or are you still looking for a way through?
Cheers, Martin