You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?