The incident workflow about halfway down reads to me like a lingoed-up version of "create a bug, escalate, put a Slack (etc.) URL in the bug, send the bug to blamees/ondutys, message boss(es), finish fix and push, schedule a meeting for the next day." Which it turns out that I've guessed reasonably well, having read the rest of the article. I mean, there's decades behind this very use-case, and at the end of the day it's possible to hook out to Slack from RT, too. But they're not using RT, true.
I don't have a problem with the work -- like I said, it's a persistent use-case -- it's just the way it's described here, as if it wasn't and with puffery. And the thin-ness of my skin with this is not the issue!
https://rt-wiki.bestpractical.com/wiki/WorkFlow#Modeling_Wor...
I don't have a problem with the work -- like I said, it's a persistent use-case -- it's just the way it's described here, as if it wasn't and with puffery. And the thin-ness of my skin with this is not the issue!