+1 - I wanted to pull in an entire thread from Slack, as a few people had very insightful comments that needed to be captured for a single Jira issue.  The thread included screenshots, URLs and text formatting (bold text, bullet points, numbering, all that Slack supports by the way).

There are problems with how it's designed today:

1. I expected the message to show up as a comment in Jira, not off in some sidebar tucked away.
2. I lost the full context of the Slack thread because the integration only works on a single message, not a thread.
3. For the message that did get pulled in, I lost the full context of the single message because it gets truncated when it comes into Jira.
4. I am being forced to context switch by having to click the link to go to Slack to see more instead of staying right in Jira.  I would then waste further time trying to read all the other comments that never made it into Jira (see #2 above).
5. I lost context because the screenshots in my Slack message were not copied to Jira.
6. I lost emphasized text, which may result in people not fully understanding my comment, because the Slack text formatting didn't come through to Jira.

So specifically I am requesting:

1. Ability to add a Slack thread to an existing Jira ticket so that I can see the entire thread directly in Jira w/o having to leave Jira.
   1. I don't think Jira supports threading, so it's okay if the replies just get stacked in reverse chronological order as Jira does today.
   2. I think this highlights the need for threading support in Jira, but that's a different topic!
2. Ensure that any screenshots that are in the Slack thread are also added to Jira in the same location as in Slack so that we don't lose context of screenshots.
3. Ensure any HTTP links in the Slack thread make there way into Jira.
4. Preserve Slack formatting, as best as possible, e.g., numbering, bullet points, bold text, spacing, etc., so that the message remains readable in Jira.
5. BONUS:  When sending the message from Slack over to Jira, I'd love to have the ability to highlight a specific portion of a comment to capture the main point of the long thread.  This would help when in Jira so that we can quickly see what the key takeaway was from that thread upon which we must take action.

Yes! Please review and implement!!

+1 - I kept looking and looking for comments that said successfully "added this message to" a Jira issue from Slack. Please, it would make too much sense to just route the Slack "add to issue" actions to the Jira issue comments.

Just over 3.5 years now everyone so based on Atlassian's average MTTR of bugs/poor design choices we are only another 2-3 years away from seeing this resolved.

Woohooo !! 🎉🙌🏼

We would get more value out of adding these as comments instead of an activity. Part of the reason of needing to add messages from Slack is conversations in regards to open issues can take place there and need to be recorded in Jira. This disrupts the communication flow if messages are stored outside of the comments section. 

+1 - I thought this was just failing to update entirely.  Getting this content logged as part of the issue history would make this feature part of our core workflow as opposed to something that just causes confusion.  Comments is what is universally used to track the status and updates for an issue.  

Yes. It' very difficult to spot out if there's any slack conversation in Jira.

Agreed. This would be great if it just added it as a Comment in Jira (or at least expose it in the Automation). 

I second that it would be great to have it in the comments section

i would really like this in slack please