Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,560,165
Community Members
 
Community Events
185
Community Groups

Advice on Confluence & Jira structure

Edited
Rolland Vander Sluis
Rolland Vander Sluis Sep 17, 2018

We're just rolling out Confluence and Jira. Our company has lots of product families that comprise software, hardware, and firmware.  Right now we have Project XYZ that involves an update to a software app that multiple instruments use, a new instrument, and an update to an existing instrument. Project XYZ deals with the latest rendition of enhancements and additions to Product Family ABC. So this is what I'm considering for my structure:

  • One Jira project for Project XYZ
  • One Confluence Space for product Family ABC: with a top-level node for Project XYZ  to track the project-related planning/development/release info, meeting notes, epic-related discussions, etc. The next ABC-related project will get its own node. I'll probably create another node that is relevant across project nodes.

Does this make sense to you seasoned Atlassian users?    Thanks!

Comment
Watch
Like Be the first to like this
383 views

0 comments

Comment

Log in or Sign up to comment
Confluence
Confluence
TAGS
AUG Leaders

Atlassian Community Events

See all events