Is it possible to create a board across multiple projects?

[Zeph Wong]

My scenario:

• I have a client-specific project that contains our high level user stories
• These user stories break down into multiple issues/tasks that are assigned to various teams (i.e., a product feature specific team)
• Even though those tasks may be completed, I don't have a clear view of when my project user story is "done"

Does anybody have recommendations on how to best achieve this?

[Peter DeWitt]

@Zeph Wong, Have you thought about using Epics to coral all your stories and tasks?  You could use the Epic as a release/version and then it would act like a container for all related issues.  

You could then create an Agile board and use Swimlanes by Epic.  This would help you track all the issues in each Epic and you would easily know where they are at in status.

pjd

[Jack Brickey]

So trying to understand your specific situation here considering your question and the underlying details. Are you saying you have a story that encompasses tasks across multiple Jira projects?

in any event you can certainly create a board that spans multiple projects. Simply by creating a filter that captures all issues you are interested in and then assign to a board. 

[Zeph Wong]

That's correct - we have our Stories under one "master" project, and the tasks span multiple Jira projects. each of those Jira projects is an individual team that is responsible for a specific component of our product. 

[Jack Brickey]

so how are your "tasks" connected to the stories, just linked? how far along and how committed to the multi-project approach are you. Without really understanding your situation I would offer that a single project leveraging Components for teams might be a better option. But I realize that might not be desirable for whatever reason.

[Zeph Wong]

Our engineering team is structured by product (I'm on the PMO side), so unfortunately we're likely stuck in the multi-project approach.

I would have liked to be able to have the tasks created under the user stories in my master project, but have those assigned to the various team's projects. It seems like that's not possible, so what some of the engineering teams have done is create their own stories with subtasks (essentially using stories as tasks in their own projects), and then linking those stories into our 'master' user stories. However when this happens, I'm not able to tell the status or progress of my master stories, since it's just a "relates to" relationship. I hope that makes some more sense?

[Jack Brickey]

In this environment the only thing I can suggest is to create your PMO board that displays all stories and tasks from the collective projects. In effect your PMO stories really won’t provide any value that I can see.

i keep thinking of ideas that you could try but every scenario ends up in a dead end or messy situation. Others may have some ideas and chime in here.