We are a SAAS company.
We move quickly with 2 week sprints.
No matter how much we attempt to make Confluence the "Source of Truth" for requirements, we consistently overload Jira tickets with acceptance criteria/requirement changes that make the corresponding Confluence content out of date. When we need to understand the actual functionality, after the fact (like for support, customer facing documentation), it's buried in Jira somewhere.
How do folks:
Balance documentation between Jira and Confluence - what is the source of truth?
How do you keep the Source of Truth updated in an efficient manner?
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