Relating Jira projects to a Business Management Project - Is it Possible?

[Katherine Wolfe]

Hello Atlassian community,

we are building out a Jira prototype in which there are many different project teams that all have specific fields and entry requirements, making in essential that each team has their own board. We also want to create a project in which ALL issues can be viewed, without navigating to each separate team project page. Originally, we built out a Business Management template which used forms to create the issues, but we found that when an issue is creating within one project, it adopts it's screens and cannot be changed if shared to another project. Another issue was if an issue was create in a software project (a team specific project), the Business Management project would not show the issues. On the summary tab of the Business Management project, there is a note of Related Projects, as seen in the image shared. We cannot figure out how to relate a project back to the Business Management project or know if this is possible? 

[Dave Rosenlund _Trundl_]

Hi, @Katherine Wolfe 👋  Welcome to the community.

The simple answer is, yes. What you are describing is project portfolio management. And there are two features in Jira you are going to want to master:

• Plans (aka Advanced Roadmaps)
• List View

In addition, the Atlassian Marketplace includes several products that offer advanced capabilities in this area: PPM Add-ons for Jira. As the number of "installs" for these apps shows, there is significant interest in them.

Best of luck to you,

-dave

[Katherine Wolfe]

Hi Dave, thanks for getting back to me quickly.

We've explored Plans previously but encountered some issues. In a Plan, you can't view an issue within your current tab; opening an issue redirects you to its associated project. Additionally, Plans are time-frame dependent, which doesn't align well with different project teams' methodologies. Some teams use Sprints, while others follow a kanban SDLC, leading to issues without assigned start/due dates. Also, it seems Plans require a project to be affiliated with a team to include its issues.

Currently, we've developed a Business Management template where issues can be created and shared across projects based on a field. For instance, if the field is "ProjectX," issues with that field value are shared with the relevant project board. However, when an issue is created in a different project (like a Scrum template), we're encountering difficulties sharing it back to the Business Management template. Can issues only be shared to a Business Management template, or is it a one-way process? Are Plans the sole method to view all issues, structured around teams rather than projects?

Our goal is to provide higher-ups with visibility into all issues across various project types within a unified space.