Slack Workflow Builder
slackhq.com
Slack Workflow Builder
1–10 of 10 posts
Re: Slack Workflow Builder
#2"Hey Jim, instead of a single email inbox with threaded travel requests, we are gonna throw them all in a single chat room with no organization or queuing system. Be sure to check it every 10 minutes, or you'll miss the ones that get pushed off the screen! It's designed exactly like a chat room, but it doesn't need any chat functionality at all (and actually operates nothing like it). Good luck!"
Re: Slack Workflow Builder
#3I think the devs at Slack have run out of things to do. "Hey Jim, instead of a single email inbox with threaded travel requests, we are gonna throw them all in a single chat room with no organization or queuing system. Be sure to check it every 10 minutes, or you'll miss the ones that get pushed off the screen! It's designed exactly like a chat room, but it doesn't need any chat functionality at all (and actually ope…
Re: Slack Workflow Builder
#4I think the devs at Slack have run out of things to do. "Hey Jim, instead of a single email inbox with threaded travel requests, we are gonna throw them all in a single chat room with no organization or queuing system. Be sure to check it every 10 minutes, or you'll miss the ones that get pushed off the screen! It's designed exactly like a chat room, but it doesn't need any chat functionality at all (and actually ope…
I'd settle for being able to manually sort my channels.
Re: Slack Workflow Builder
#5A couple things keep me from trying to manage issues in Slack (like the travel example): threads don’t have a filterable status or a way to mark them resolved, and a channel can’t be ordered as most recently updated. What workarounds are popular to address these limitations?
Re: Slack Workflow Builder
#6I think the devs at Slack have run out of things to do. "Hey Jim, instead of a single email inbox with threaded travel requests, we are gonna throw them all in a single chat room with no organization or queuing system. Be sure to check it every 10 minutes, or you'll miss the ones that get pushed off the screen! It's designed exactly like a chat room, but it doesn't need any chat functionality at all (and actually ope…
I get the impression they're going to get more into collaboration tools. Better document/file sharing, some light project management features, etc. I'd settle for being able to manually sort my channels.
Re: Slack Workflow Builder
#7Earlier quoted context omitted.
I get the impression they're going to get more into collaboration tools. Better document/file sharing, some light project management features, etc. I'd settle for being able to manually sort my channels.
I use Slack sparingly (mostly on Microsoft Teams and Discord), but does Slack have a equivalent to Discord's Ctrl+K or Teams' command bar to search for a channel/user? That's mostly how I started getting around in those applications.
Re: Slack Workflow Builder
#8I think the devs at Slack have run out of things to do. "Hey Jim, instead of a single email inbox with threaded travel requests, we are gonna throw them all in a single chat room with no organization or queuing system. Be sure to check it every 10 minutes, or you'll miss the ones that get pushed off the screen! It's designed exactly like a chat room, but it doesn't need any chat functionality at all (and actually ope…
Re: Slack Workflow Builder
#9This looks potentially pretty useful. A couple things keep me from trying to manage issues in Slack (like the travel example): threads don’t have a filterable status or a way to mark them resolved, and a channel can’t be ordered as most recently updated. What workarounds are popular to address these limitations?
When the work is completed, the fulfiller inserts a reaction. X hours later, that work is moved from #request-active to #request-closed through an automated bot.
Re: Slack Workflow Builder
#10This looks potentially pretty useful. A couple things keep me from trying to manage issues in Slack (like the travel example): threads don’t have a filterable status or a way to mark them resolved, and a channel can’t be ordered as most recently updated. What workarounds are popular to address these limitations?
What if you set up 2 channels - #request-active (where task threads are submitted) and #request-closed (where task threads are archived and no other posts are allowed). When the work is completed, the fulfiller inserts a reaction. X hours later, that work is moved from #request-active to #request-closed through an automated bot.