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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,458,472
Community Members
 
Community Events
176
Community Groups

Managing documentation within a space

Hi Everyone!

Thank you for any insight you can provide.

I'm setting up Confluence as my company's product and team knowledge base. I have spaces setup that contain general information about our product offering. Changes to these knowledge bases are managed by the documentation team and are requested in two ways:

  1. Inline Jira issue creation
  2. A link to a Jira project where a user can request additional documentation. The main reasons for this are to bypass the restrictions of the inline Jira issue creation where a user can only enter a title and description and to provide a request process for general requests that don't fit neatly into a space.

I then have another set of spaces that are team knowledge areas, like sales/marketing, design, etc. Rather than have our documentation team manage those spaces as well, I would like to setup a different workflow for the teams to manage their own team space documentation. What has been an effective method for managing creating and amending documentation within a team space? Solutions I've considered:

  1. Give every team member full access to the his/her team space such that he/she can add and alter documentation at will. The tradeoff is that this bypasses quality assurance.
  2. Assign a team space moderator where each team member has to submit requests to him/her in some manner - whether that be via email, slack or through a separate Jira project. The tradeoffs include extra steps for adding documentation and it means creating a Jira project for each team. We gain quality assurance but tradeoff friction.

Thank you,

Justin

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events