Currently we run our projects where we have User Stories and Acceptance criteria in Confluence, and Jira tickets are used to organise the implementation of these via Sprints and agile boards (and to log time via Tempo).
We're finding that:
We've started to do the following, in an effort to mitigate some of these issues:
This solves a lot of these problems however after some research I've found that a lot of places are doing the opposite of what we're doing where Confluence is used as just a list of User Story titles and have a link to a Jira ticket that has all of the meat (User Story, AC, status, conversation). There's even a blueprint in Confluence that drafts this (Product Requirements) for us.
I actually think this approach is better, but wanted to see what others are doing and how they find it?
Some issues with this approach that I haven't solved for yet:
Keen for any insights from anyone.
Deliver better and faster value to your customers with the Jira automation platform. Watch this Demo Den series below to learn how to use the new interface and set up automation rules to help your te...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events