You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We are looking at consolidating 4 Jira Software cloud instances - but some groups use a separate Jira Project for each real-world project - and other groups have 1 Project per Program Group/Platform and use either "Component" or "Fix Version" fields to record the name of the "Real-World Project" that issue relates to. This lets everyone work out of their one Platform while doing work across multiple "projects" - also we can relate one issue to multiple "Real-world projects" this way - as some digital development work impact multiple "real-world projects" - since Epic link cannot do that many Epics related on any 1 issue/
What are your thoughts? Do you spin up a separate Jira Project for each real-world effort?
Trying to understand the various Advantages/Disadvantages and possible future repercussions.
Thanks, Mike - appreciate you weighing-in.
That aligns with one camp - and where they need a multi-relationship for Issues - I think Component makes the most sense since an issue can only link to 1 Epic.
I see that natively Components exist in 1 project and Epic-Link spans across - so that makes sense structurally.