Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Source of Truth: Jira or Confluence?

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?

1 comment


I have exactly the same problem. Well, let‘s say a similar problem. Currently, the connection between Confluence and Jira is not working. This only amplifies the issue. 

For me, the capabilities of Confluence in terms of documentation are much better compared to Jira. So, using it for documenting AND planning seems to be logical. Daily work, as the experience shows, is happening where the tickets (Epics, UserStories, Tasks) are. Jumping to another tool, even if it‘s better suited for documenting, is a disruption and simply too much effort for the lazy human. Even if the connection between the tools work.

It‘s only because I have trouble jumping back and forth that I started to think about that. 
The more steps you have to do, the more duplicate data is involved (maintain the info in two locations) the less likely it is that everybody sticks to the process. So, what is the best way to do it?

As always, there is no black and white. But there is a way it‘s more likely that it will work: reduce friction. As with every product or process finding the best was involves iteration.

Define. Use. Gather experience. Improve.

I try to do the heavy lifting in  Confluence. Everything in Jira is focussing on getting things done. And if the connection between these two works it get‘s a little easier. But, there is no doubt, you have to find YOUR way and make it work. 


Like Nic Brough -Adaptavist- likes this


Log in or Sign up to comment