How to map the following organization structure in JIRA

[pawelbah]

Hi, our company works in such a way that we have specialized IT teams that work on multiple projects/tables at the same time, e.g. iOS Team performs tasks from multiple projects on their board.

We would like to put a project/table next to it where you can see on large tasks what is happening in the project. It would be a project owner's board, where, for example, the iOS Team's work would be represented by a single task connected by relations to the iOS Team's tasks.

This is the concept - do you have ideas on how to do it better?

In addition, we would need some kind of tool that would export from the project owner's board the progress of the work to a structured document (in some established form), so that this could be plugged into, for example, a pdf of a meeting report.

Thanks in advance for any hints. 

[J. Caldwell]

What you are describing to me, which is a "can I/how do I  - allow individual projects to function as is, but provide visibility to the overall things going on with this team and their work who are spread over multiple projects?"

Jira Plans (formerly Advanced Roadmaps) is a way to do this (included in Premium and Enterprise levels): https://support.atlassian.com/jira-software-cloud/docs/get-started-with-advanced-roadmaps/ 

You'll also probably want to leverage the Team Field in Jira as well (should make some of this easier): https://support.atlassian.com/jira-software-cloud/docs/manage-teams-in-your-advanced-roadmaps-plan/

https://www.youtube.com/watch?v=mfjH79FtjiM

[J. Caldwell]

Additionally - you might also want to look into the hierarchy of your overall issues. You can introduce additional issue types in a hierarchy as well that may give you that 1 issue kind of drill in relationship: 

https://support.atlassian.com/jira-cloud-administration/docs/configure-the-issue-type-hierarchy/

[Dave Rosenlund _Trundl_]

Welcome back, @pawelbah 👋

Jira has changed a lot since 2022 (when you last posted), and I see that you were using Big Picture then. I assume that didn't solve this problem for you? Or maybe you've changed jobs or roles and are looking at things differently now?

In any case. I have a suggestion.

Instead of trying to make Jira conform to these specific ways of working, what if, instead, you think first about the problem you are trying to solve and how Jira can best solve that problem?

That's a rhetorical question/suggestion—something for you to ponder—and you don't need to answer it here.

I suggest it because if you leverage Jira's strengths through its working methods, you might reach the optimum solution much faster and easier. I've seen this in practice over the years. Generally speaking, companies that take this approach are happier working with Jira.

I suggest starting with the Atlassian Team Playbook and focusing on the plays that are most relevant to your interests.

I bet you'll discover ways to achieve your goals (meet the organization's needs) that work well, even if they differ from what you describe above.

~~~~~~~~~~~~~~~~

That said, if it's an absolute requirement that you do things exactly as described above, you were on the right track two years ago. Look closely at what the Jira "Plans"(formerly known as Advanced Roadmaps) feature and the new List view feature can do for you.

If upgrading to Jira Cloud Premium is not an option, you may want to explore the Atlassian Marketplace once again and look at products similar to BigPicture (like Structure and JXL, to name two). One of those three will most likely give you what you describe or very close to it. 

Hope this helps,

-dave

[Dave Rosenlund _Trundl_]

Haha. Great minds think alike (see @J_ Caldwell 's answer)