Create Jira from Slack doesn't include full description

[Jessica Herbst]

I had a long Slack message (1,000 characters give or take). After creating my Jira issue from Slack, I went to view the Jira issue and it only had about the first ~175 characters. This is not helpful at all when trying to create Jira issues from Slack. Is this a setting or a limitation of the integration?

[Daniel Eads · Accepted solution]

Hi @Jessica Herbst , welcome to the Community!

I've just given the Create Issue action a test and noted some behavior around character limits.

1. The summary is limited to 200 characters - the integration shows you the characters remaining (170 in this example) when typing:
   
2. The Description field will pre-populate in the modal window with the first 3,000 characters from the Slack message that was selected
3. You can enter more than the initial 3,000 characters into the Description field in the Slack modal, and the description will still all populate in Jira
   
   

Given that all - I'm wondering if potentially the summary is what was limited? Or possibly the selected message in Slack was one of several sent at the same time? The integration should allow the description field to be quite long. A screenshot of the behavior you're seeing might help me track what's causing trouble.

Cheers,
Daniel | Atlassian Support

[Jessica Herbst]

Hi @Daniel Eads thanks for getting back to me! 

Here are some screenshots. So, the first is the complete Slack message (all one message). Then when I click to create a Jira issue from the message it doesn't populate anything for the Summary, which is good and the Description is the full contents of the Slack message you see here (just didn't capture it all in the screen shot). Then the final screen shot is what the actual issue gets populated with. As you can see it starts with user info, database info, then the first word and email from the bigger paragraph, but then it gets cut off.

**Edit: I Just added the full modal so that you can see the description field does populate with the whole Slack message.

[Luiz Silva]

Hi @Jessica Herbst,

I was able to confirm there's an issue with the way the Slack integration translates the Slack formatting into Jira formatting.

What seems to be happening is that everything within the first < and the last > in a given line is being swallowed except for the first mailto link.

For instance:

Foo (<mailto:some@example.com|some@example.com>) bar (<mailto:some@example.com|some@example.com>) baz.

Becomes:

Foo (some@example.com) baz. 

I noticed the "swallowing" only occurs when there are mailto links, though regular links will also not be properly formatted in Jira.

I have created a bug you can follow in https://jira.atlassian.com/browse/API-392. Unfortunately, there's no workaround at this moment but not using multiple mailto links in the same line.

Sorry for the inconvenience. I hope that explanation helps for the moment and that soon we can tackle the issue.

Cheers!

[Jessica Herbst]

@Luiz Silva thanks so much for debugging this issue, I really appreciate it!