Any update here? Would also lovvvvvve to see this implemented.

I'm a technical writer, and being able to create documentation-related tickets that come up from Slack threads would save my team a lot of time. The fact that creating tickets through this integration causes a separate message in the channel, rather than threading it within the post it was created from is pretty much a dealbreaker since it adds unnecessary noise for our entire company to see.

Having to open Jira to create a new ticket and cross-reference the Slack thread link is so much more cumbersome, and creates more of an opportunity to get distracted from my current task by making me leave Slack and go to a separate application, which is super unfortunate.

This is a really important feature. The channel get messed up with a lot of messages that could be inside the thread with the request.

Edit: Open since 2019 😨

We also need this feature, otherwise the previews take too much real estate in the channels.

Would love to have this working - we have some tickets that drive several subtasks and its driving walls of text. 

+1 

Currently fleshing out a Workflow to streamline dev requests; this feature would increase visibility + issue tracking immensely. Is there an update on the progress? 

+1.

+1

+1

Does this have a dependency on API-342?  

This feature is much overdue. Having a separate post for each ticket and update is far from optimal. Even with a low number of tickets e.g. 15, if there were 3 updates intra-day for each ticket this would lead to 45 slack posts which is incredibly distracting. In addition for many posts into slack being distracting it's also difficult for team members wanting to find the most recent update for a ticket. Please add this feature. 

Yes, this would be great to have.

Need this to increase use of JIRA!

need this feature badly

This is would be a great feature. As it is right now, the channel is noisy and turns away the business partners.

The lack of this feature has led our people to switching off Jira/ Slack integration as soon as they try it, and never using it again. Also putting a link in every post is even spammier, as the generated link preview gobbles up real estate too.

This would be great. The bot is extremely useful, however, it tends to congest the main channel. Adding a thread reply would reduce the clutter, but also promote keeping conversations in a thread. 

Long needed feature. The preview is relevant to the conversation, but should not take up space on the main conversation window.

I would like to have this feature too. It would make the slack channel less messy and I don't have to switch between slack and Jira that often

Definitely a feature that my team & I would love to use, would clear the clutter in our progress channel and allow easier navigation through the channel

Would love to have this feature. This would go great with our daily stand up bot messages 

pretty please

Also desperate for this feature. The integration makes channels break down as the team cannot read the conversation any longer. Having the links in threads would be a killer feature. 

IF you could connect to a slack post and auto post Jiracomments into that thread instead of a channel - that would be amazing - not sure this feature is that but it appears other people think so 

Upvoting this feature

Upvoting this feature

Please add this feature.

The Slack channel chatter is overwhelming when there is more than a handful of notifications. The option to automatically nesting related messages in threads, by issue, would be a deity-send.

Upvoting this from my side, this would greatly help us having more control and visibility of some upcoming requests we have while keeping the flexibility and readability of Slack threads

upvoting this, this would make this plugin about 20% cooler

Up-voting this. Often our team lists a series of tickets for sprint planning and the barrage of jirabot posts completely disrupts any other communication in the channel.  

Is there a plan to add this in the near future? Has been stale for a while. Our team would really like to have this since we write a daily report on a slack channel and  we need the bot to show the description of the issues, but at the same time it makes a bit of a clutter due to the bot messages in-between the report lines. 

Would be great to have. Might try to tackle this one myself as a plugin, but would prefer to have this availble especially as a part of Jira automation!

Upvoting this.  
We have many discussion on the #channel-topic on various instances (IE Jira Tickets).  

Looking forward to the awesomeness that you do! 

up voting this. Will reduce cluttering in channels

Clumsy workaround: remember to not mention a JIRA ID directly in your initial channel message, maybe just using something like ABC - 123, then immediately start a thread and then type in the IDs like ABC-123 so as to force the bot to post the issue preview inside the thread rather than on the channel.

This is a must have... otherwise, the proper use of threading happens on the original post with the issue number (ABC-123) and the unfurled description still appears below the thread.

This would be a wonderful feature.

This is very interesting and we wish it. Would appreciate this. We are always communicating in threads in a room with much communication. The responses from Jira Cloud is cluttering the slack dialog, and we often do delete them and re-add them in the thread.

A very useful integration might be even better with this support.

This would also motivate the use of threads in Slack. 

If a Jira issue is mention all relevant information stays in the correct thread context about that issue.

Example:

1. Message #1
2. Message #2
3. Message #3 mentioning JIRA-123
   1. Bot showing details about JIRA-123
   2. Message #5 about JIRA-123
4. Message #4