[inevaexisted]

I introduced a similar thing at my work place and it works (there's a few points where people forget or sometimes there's cross over) we added some state to it to so in the context of triaging bugs.

we reacted to the original message with:

ticks - to indicate the bug or issue was accepted and we had enough information to raise the problem/issue into our tracking system

cross - to indicate not a bug

jiraicon - to indicate a ticket had been raised (and linked into the thread) all the information so far would be in the ticket and further comms hence forth would be in the ticket system.

in the channels we did this in, messages would be pinned till they were given the tick/cross so people knew what needed triage and what didn't (treated triage as a team sport, whomever got to it first saved the rest from having to dive into it, unless they so wished)

[woutr_be]

I don't really understand this workflow, why does this need to happen in Slack at all, when you already use Jira? Wouldn't it be far easier to raise a ticket in Jira directly, have all the info there, and then mark is as a bug/no bug?