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.
This question seems to have been asked and answered a few times, but none of the answers really solves my teams' specific situation.
Some background info:
We have the following teams:
We have a custom JIRA project called "Charters" that contains a custom issue type called "Charter" (initiative) which is essentially a request to fund a project with a particular scope and outcome in mind. The charter issue is linked to a Business Case page in Confluence. Each charter advances through a workflow along a Kanban board, essentially from To Do to Approved.
Let's take an example of a charter called "Mosaic." This project will include some work for the Salesforce teams, the BI team, and possibly Web, too.
Once the Mosaic charter is Approved, the work is decomposed into epics and issues. My question is about where those epics and issues should reside.
Right now, we have the following JIRA projects, basically aligned with teams:
Since Mosaic spans multiple teams, it does not naturally fall into one of these buckets. Maybe it makes more sense to have a JIRA project called "Mosaic" instead of having team-centric JIRA projects.
Should JIRA projects be, well, projects? Or should they be team-centric? Or should they be product-centric (i.e., cross-team)?
One of the other major challenges we have is knowing that a particular bunch of epics and issues are actually part of Mosaic. If they are the only issues in the Mosaic JIRA project, then it's easy. But if Mosaic is spread across JIRA Projects, then how do we roll the up? And how to we prioritize the work of one team that may be working on issues in multiple JIRA projects?