Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Create an Issue" shortcut: if message is threaded, post notification to thread #1522

Open
Skn0tt opened this issue Nov 9, 2022 · 4 comments
Assignees

Comments

@Skn0tt
Copy link

Skn0tt commented Nov 9, 2022

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.

@ashokirla
Copy link
Contributor

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.

@asbjornu
Copy link

asbjornu commented Oct 19, 2023

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:

  1. 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.
  2. 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. 🙏🏼

@zpelechova
Copy link

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...

@alper
Copy link

alper commented Aug 6, 2024

It's pretty much a non-starter to use this like this if it spams the channel. The notification message should go into the thread of the message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants