Anyone else struggling to keep customer journey maps connected to their Jira work?

[Kranthi Kiran Pulluru]

Hey everyone,

I've been doing a bunch of research into how teams handle customer journey mapping alongside Jira, and I keep hearing the same story:

1. You run a workshop (often in Miro or on a wall of sticky notes)
2. You digitize it into Miro, a Confluence table, or maybe a dedicated tool like Smaply or UXPressia
3. You manually create Jira issues from the pain points and opportunities you identified
4. Within a few weeks, the map and the backlog have drifted apart. Nobody updates the map when work progresses. It becomes a snapshot of that one workshop, not a living document.

The result? Someone asks "did we actually fix the onboarding drop-off?" and you're digging through Jira filters because the journey map hasn't been touched in months.

A few specific gaps keep coming up in my conversations:

The map-to-backlog bridge is manual and fragile. You spot a pain point at the "checkout" stage, create a Jira story for it, but there's no link back. You can't look at your journey map and see which pain points have been addressed and which are still open. The map and the work live in two different worlds.

Confluence has templates but not tools. The journey mapping template is a static table. You can't filter by persona, track progress, or connect touchpoints to actual Jira issues. It's a document, not a workspace.

Miro is great for workshops but rough as a system of record. Teams love it for the initial mapping session but then struggle with the "now what?" part. Priority and context captured on the board gets lost when you move everything into a flat Jira backlog.

Nobody's connecting journey maps to JSM data. ITSM teams are running journey mapping workshops to understand service experiences, but none of the maps pull in actual service data like ticket volumes, resolution times, CSAT scores by touchpoint. The maps end up based on assumptions rather than evidence.

Journey maps don't cross Jira project boundaries well. A customer journey touches frontend, backend, support, marketing. But Jira work is siloed by project. There's no good way to see "everything we're doing that affects the onboarding journey" across projects.

I'm working on building a journey mapping tool for the Atlassian Marketplace that tries to address these gaps. Structured journey maps with real connections to Jira issues, not just a canvas.

But before I go further, I'd love to hear from this community:

• How are you handling journey mapping today? What tools, what workflow?
• Which of these pain points hits hardest for your team?
• What would make you actually keep a journey map updated instead of letting it go stale?

And if you'd be open to a 30-minute research call, I'd really appreciate it. Happy to share early access when we launch - https://calendly.com/thought-flow/thoughtflow-user-research

Cheers, Kranthi

[Bill Sheboy]

Hi @Kranthi Kiran Pulluru 

You seem to have created a duplicate of your other post, rather than contacting the community managers and waiting for their assistance to move it to App Central.

• https://community.atlassian.com/forums/Jira-questions/Anyone-else-struggling-to-keep-customer-journey-maps-connected/qaq-p/3213442
• https://community.atlassian.com/forums/Jira-questions/Anyone-else-struggling-to-keep-customer-journey-maps-connected/qaq-p/3213452

Please contact them to delete one of these and move the other to App Central.  You may need to wait until their working hours before they take action.  Thank you!

Kind regards,
Bill