You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'm always frustrated when I use the "Create an Issue" shortcut (which is great!) on a message that starts a Slack thread. I'd expect the notification about the issue being created to be posted to the end of the thread, but instead it's posted to the channel where the thread lives in. This makes it non-obvious for people reading the thread, that there was an issue created from it.
Describe the solution you'd like
I'd like to either have a setting, or have this behaviour be default:
When an issue is created from a message that starts a thread, the notification should be sent to the end of that thread.
Describe alternatives you've considered
As a current workardound, I link the message in the channel into the thread manually.
The text was updated successfully, but these errors were encountered:
Thanks for the feedback. Currently, we are using create issue card as the parent card for subsequent notifications added to the thread. We will evaluate this feedback and see what are the alternatives.
I would like "Create an issue" to result in a thread comment regardless of whether a thread already exists for the message or not. Jira's Slack bot works this way, so it's a bit of a let-down to see GitHub not being as user friendly as Atlassian's offering on this front. Creating a GitHub issue from a Slack message, should imho:
If the message doesn't have a thread already, create a thread where the issue creation comment is a reply to the message from which the issue was created.
If the message is within a thread, just add a reply to the end of the already existing thread.
This is somewhat related to #660, in that it seems like a general issue with GitHub's Slack integration in that threads aren't used in much capacity at all. Threads are an awesome way to make comments more precisely notify only the people interested in the comment. As you write:
Threading gives context, reduces noise in the channel and helps improve collaboration.
Please consider implementing threads throughout the Slack integration. 🙏🏼
I would also really much like this option.
When we deal with several subjects in one channel and dont react immeadiately, the issue post gets lost from the original issue and disturbs the channel...
Is your feature request related to a problem? Please describe.
I'm always frustrated when I use the "Create an Issue" shortcut (which is great!) on a message that starts a Slack thread. I'd expect the notification about the issue being created to be posted to the end of the thread, but instead it's posted to the channel where the thread lives in. This makes it non-obvious for people reading the thread, that there was an issue created from it.
Describe the solution you'd like
I'd like to either have a setting, or have this behaviour be default:
When an issue is created from a message that starts a thread, the notification should be sent to the end of that thread.
Describe alternatives you've considered
As a current workardound, I link the message in the channel into the thread manually.
The text was updated successfully, but these errors were encountered: