This is quite a unique scenario.
The company decide to create boards to display all epics for multiple JIRA team projects with the same Product Owner/"Manager". The intent was to create grid block of teams where dependencies can be managed easier and makes it easier to track what work is in progress across all teams. This is a great idea to scale agile, however this broke every plan in portfolio.
The epics that are displaying on these newly created board, shared across teams disappeared from the portfolio plan. I tried to import the newly created board into portfolio hoping that the epics can be pulled back into the plan.
This Error occured :
java.lang.IllegalArgumentException: (no message)
Stack trace removed due to detial constraint - exceeds 20000 characters
more detailed description :
This got me thinking if there's a workaround to create grid KANBAN boards that mirror multiple JIRA Team projects and not "remove" the epics from Team Boards ?
Hi @Johann Batt,
First and foremost, I would strongly suggest opening a support ticket to try to understand why this error is happening. It obviously does not seem expected.
On your question, would creating a JQL filter including the desired issues (e.g. Only epic issue type) and basing a board and plan out of that filter work for you?
Thank you for the prompt reply. will log the ticket asap with some more detial - thanks for the suggestion.
more detailed description :
This got me thinking if there's a workaround to create these grid KANBAN boards that mirror multiple JIRA Team projects and not "remove" the epics from Team Boards ?
Let me try to visualize that to be sure I'm understanding correctly.
If this is the case then epics shouldn't disappear from any team board.
You can then use one Portfolio Plan per Grid with all the grid team's board as issue sources.
And a Portfolio Program (Still in beta currently) to aggregate all the grids together.
Finally, and this is more of a "Portfolio point of view": you can consider using a new hierarchy level above epic to better track work across multiple projects (as epics tend to be too low level to be "cross plan"). For that, see How to add the initiative level cross-project
Hope that helps and/or give you some ideas!
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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