I searched through previous questions and couldn't find an answer that fit closely to what I'm trying to do, so I thought I'd ask here.
I am working on a project (Project A) that uses JIRA for bug and story tracking.
My project works alongside three other projects (Project B, Project C and Project D), all of whom are supposed to be using JIRA in the same manner.
All projects do work on epics that are similar across the projects. Meaning Projects A & C may implement Epic 'UI update', but they work on it independent of each other, and don't require one to be done before the other can begin.
All projects do work on epics that are not relevant to any other project (ex Project B working on Epic 'New B-style').
All projects on occasion must integrate work from a 3rd party, and ideally at the same time.
My question- is there a way to track all of this at a higher level? Meaning, is there a way to create 'Master Project' that monitors a) progress and issues of the epics of individual projects (A, B, C, D) and b) progress and issues of epics that are similar across the projects?
Ideally, I'd like to make some sort of dashboard that can monitor the health of the individual projects as well as the overall health of the environment that the individual projects make up together. And then track any issues blocking the progress of the common epics.
Bonus points for helping figure out how to also track the incoming/progress of integration of the 3rd party pieces.
Sorry for the convoluted question, as you can see, it's hard (for me) to wrap my head around.
I would suggest creating either a kanban or a scrum board for managing multiple projects.
The board's query may be something like:
project in (A, B, C, D) ORDER BY Rank ASC
where letters A to D represent the keys or names of the projects you would like to be able to manage from a single view.
You may create 4 board's Quick Filters for easily selecting through a mouse-click one of the projects, filtering out all issues from other projects. (ie: project = A)
For keeping track of the third party progress, you may create another Quick Filter for that, like:
assignee in membersOf("third-party")
where "third-party" would be the name of a group you have created, having added third party users to it.
Where should this Board created? Should be in one of the projects A, B, C or D or would be a better idea to have another extra project Z that can have filtered boards as described before?
I personally prefer the second option, so original projects are kept clean, but I was wondering if all issues managed in the project Z would be mirrored in the others. And I'm talking about statuses, maybe priorities...
Boards do not belong to any projects, despite of the fact that they are shown from the project view if you have access to both the project and the board.
So, there's no place to which the board belongs.
A board which is fed by issues from multiple projects will present all statuses from all workflows set in every project, so that they can be mapped to the board's columns.
In that regard, it is usually a good idea to use the same workflow in all projects.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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