I have a project configuration where multiple projects (~25) are managed with JIRA, and collaboration between projects is to be done. What is the best way to model issues that define collaboration between different projects in JIRA?
At first, the idea was to use epics with unique names that name the cooperation between projects (Cooperation PnPm, where n and m are project IDs and n != m). In order to see the cooperation issues of project "n", we tried adding all the projects "m" (the ones n collaborates with) to the kanban board, filtered with the Epic Name "Cooperation", so that we only get epics and linked issues that have something to do with cooperation. Otherwise we would have boards with all the issues coming from any "m" project that "n" collaborates with.
This solution turns out to involve a lot of manual work for 25 projects and is not working completely, so hence the question here. I am aware of JIRA Portfolio, but our problem is really in modeling inter-project collaboration. What would be the best way to do that within JIRA?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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