Congrats you turned Slack into (an even worse version of) Jira.
This got me thinking though. Instead of turning your chat into a ticketing system, has anyone ever turned the ticketing system into a chat?
Like instead of “comments” on a ticket, you get a live chat channel (that can be reviewed later as “comments” for historical data).
Most companies I’ve worked for will setup channels on slack in a similar fashion for projects and initiatives but these are not really ergonomic for someone that prefers to “live” in the ticketing system for work management. And context gets lost the older things get.
You could pair this with a general channel for unfocused chitchat, but all relevant work would be discussed under the work item itself. Perhaps a “slack-like” view where you can see all your watched work items at once in “channels”.
Yes, it’s just an IM client. Like all in history, what matters is whether it can post images and whether other tools are integrated with it. Another generation will invent a new one and suddenly all app will say “Insert your $nextGenChat key here”.
You can rebuild a chat client, but you can’t make up for popularity. Atlassian tried twice: Once with HipChat, once with Stride, and failed at both - like everything Atlassian does, I know, but you have to admit they are popular in corporates.
Also, it’s so vastly better than MS Teams. But Discord is so vastly better that a lot of companies use it, despite it being aimed at communities.
(Protip for confused skim-readers: This is called context. It helps you understand the rationale for why a group - not a company - might enjoy having 150 Slack channels with such intense micromangement. Ctrl-F for "Inkhaven", then look up Inkhaven, Lightcone Infrastructure, and LessWrong.)
The context should be included in the piece. Also, when I reach a page chock-full of low-quality AI images [1], I assume the contents are also AI slop and stop reading.
> Each member of the staff has their own channel, in which they give updates on their work status, ask questions of other teammates, notify of their unavailability, share their uncertainties and thoughts on the program.
When a piece of work require input from two persons, should I ask in project channel or channel of person A or channel of person B?
> Each resident has their own channel, in which they talk to their coach, ask questions of the team, request improvements to their room or writing setup or just generally throw anything they want someone to look at.
If I want input from my coach and not discuss in public, why not DM but channel?
I'm a chat maximalist (we all are going to be as agents improve), but this article makes the idea look bad. Chat should be the interface, not the system of record.
I wish they’d just display chat lines as cards, for queue channels, with a clear status, search JQL, and allow external apps (if they want) to sync those items with Jira.
Meanwhile it feels like half my colleagues don't understand the difference between starting a new Teams conversation ("thread" in Slack), or replying to an existing one. And there's no way to move a message that was posted in the wrong conversation. AFAIK it's the same with Slack threads.
Getting people to post in the "correct" channel faces similar challenges.
Imagine the chaos that would result if we ran everything through Teams.
Readit News
This got me thinking though. Instead of turning your chat into a ticketing system, has anyone ever turned the ticketing system into a chat?
Like instead of “comments” on a ticket, you get a live chat channel (that can be reviewed later as “comments” for historical data).
Most companies I’ve worked for will setup channels on slack in a similar fashion for projects and initiatives but these are not really ergonomic for someone that prefers to “live” in the ticketing system for work management. And context gets lost the older things get.
You could pair this with a general channel for unfocused chitchat, but all relevant work would be discussed under the work item itself. Perhaps a “slack-like” view where you can see all your watched work items at once in “channels”.
Honestly I preferred Google hangouts because they were better integrated with my email.
Channels as far as I can tell are a mix of group chats or replacements for mass email distribution lists. Nothing special.
Also point 7in this blog is truly insane. The whole point of a dm is I don’t want others to see it.
You can rebuild a chat client, but you can’t make up for popularity. Atlassian tried twice: Once with HipChat, once with Stride, and failed at both - like everything Atlassian does, I know, but you have to admit they are popular in corporates.
Also, it’s so vastly better than MS Teams. But Discord is so vastly better that a lot of companies use it, despite it being aimed at communities.
https://news.ycombinator.com/item?id=44819849
(Protip for confused skim-readers: This is called context. It helps you understand the rationale for why a group - not a company - might enjoy having 150 Slack channels with such intense micromangement. Ctrl-F for "Inkhaven", then look up Inkhaven, Lightcone Infrastructure, and LessWrong.)
[1] https://www.inkhaven.blog/about
> Each member of the staff has their own channel, in which they give updates on their work status, ask questions of other teammates, notify of their unavailability, share their uncertainties and thoughts on the program.
When a piece of work require input from two persons, should I ask in project channel or channel of person A or channel of person B?
> Each resident has their own channel, in which they talk to their coach, ask questions of the team, request improvements to their room or writing setup or just generally throw anything they want someone to look at.
If I want input from my coach and not discuss in public, why not DM but channel?
Hence why lots of people hate Slack now - it just becomes a ticketing system, and it ends up being a not-particularly-good one.
Getting people to post in the "correct" channel faces similar challenges.
Imagine the chaos that would result if we ran everything through Teams.
What does?