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

How to Prevent Dead/Lost Knowledge

How does everyone prevent losing research knowledge when working on a project?

My company develops hardware/firmware for clients.  When working on a project in Confluence I will create a space and place all of my information in it. This will be done for any new projects, designed parts, assemblies, firmware, There are a couple of templates I use depending on what I need.

I also have a space called knowledge base.  This is where I place general information on various topics.

project.JPG   knowledge.JPG

As with most projects there is information which can be reused in other developments.  This is the information I don't want to loose even thou I still have the project space available. 

How does everyone handle their information? 
Create one space or a couple?
Create a new space for that data?
Place data in a different space then use links, so data is not duplicated?
Have a lookup table for information?
Don't worry about it and just do a search?

Looking forward to hearing how everyone finds what works for them.



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events