We are working with multible Teams on one Project. Each of the Teams uses its own board and sometimes project, epics, versions. The goal is, that the teams should work seperatly without much dependecies to other teams.
This creates the situation that we have One Majaor Project and several projects releated to this one with own epics and versions. What would be the suggested JIRA setup for this so that we are able to create a Burnup/Burndown Chart over the whole Project since versions can not be shared trought multible projects.
What you are describing is a typical Project -> Program scenario where multiple teams an deliverables are involved. In JIRA standalone the highest level structure is a project and anything else is some soft of hack and won't model the exact scenario that you are presenting.
The only solution that fits your use case is to use an add-on Cycle Control - it allows you to define this Master project as a Release and then you can define the multiple team that are involved. Then the add-on will pull the data from each and every board that the teams are working on and use this as a scope of the Release.
This allows you to define metrics on the aggregated level including Burn Down and Burn up as well as metrics for each individual teams. The sample data that you can generate from the Getting started page show a similar scenario using two agile teams.
Let me know if it looks interesting and you need more information or a demo.
You can create a filter that will aggregate all Your projects including the master project.
On top of the filter You can create an agile board - kanban for example and cleanup the subfilter for kanban in the board configuration to remove released versions rules.
That will show You everything on one board and You should be able to show/generate some reports.
We've created a plugin that allows to share large program boards between teams and filter them out easily
Using it You can create set of team filters which will show items related to them.
But Your board may become super slow if You'll load 2-3k issues.
Have a look at this how to fix it
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs