The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
× Create
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community resources
Community resources
Community resources
- Community
- Q&A
- Confluence
- Questions
- Advice on Confluence & Jira structure
Advice on Confluence & Jira structure
Rolland Vander Sluis
September 17, 2018 edited
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!
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
Copyright © 2026 Atlassian