You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
We recently started using the new Jira Ops for incident handling. As incidents unfold, we use Slack to push notifications and tagging the relevant people (or groups of people) with each update. They can then tag others, thus ensuring the right people get notified throughout the company.
The problem we're having is that not all updates are company-wide. Some information is sensitive, and while important for the purpose incident management and post-mortem analysis, should not be visible to everyone (or is not relevant for everyone).
How do others handle this dilemma? Do you maintain two parallel incidents, one with all the details, and the other only with the company-wide updates? Do you record sensitive updates somewhere else?
Curious to hear your thoughts.
I'm John Allspaw, co-founder of Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events