The Update Roulette Problem

[Evan Fishman - Quely for Jira]

Who else can relate to the detective work required to find the information you need about a task?

It's a special kind of chaos where the Slack message says something different from the email and meeting notes. And the ticket is super bland.

How're you dealing with it?

[Amanda Barber]

I'm really loving the ability to search in Confluence or use Rovo to find updates across multiple apps!

[Michael Karl]

Well sometimes the multitude of communication-channels these days annoys me quite a bit. We have three important contractors with their own Jiras plus a Jira on our own. We use google chat internally plus Slack for external communication. Plus E-Mails and conference calls on google meet. And we use google docs and Confluence.

Usually we try to centralize the latest version in our own Jira, Sometimes people write updates in the comments of a Jira-issue. I try to convince everybody that the recent version of "What's to do?" belongs in the description of the issue. Always.

When feeling completely lost (once in a while that can happen) I try to get the relevant players in a short meeting to find out about the latest version, where we should put it and who is to be informed about it.

My role in a Jira-Project is actually quality assignment, but still I'm partly in project management.

[Evan Fishman - Quely for Jira]

@Michael Karl 

You just described the job nobody formally owns: context custodian.

Multiple Jiras.
Updates split between comments, docs, chat threads, and meetings.
Then a recurring “reset meeting”

Quely is basically built for people doing exactly what you’re doing now, trying to stop context from leaking across Jira instances, chat tools, docs, and meetings.

Instead of chasing the latest version, the context stays attached to the work itself.

You’d be a dangerously good test case.