How to structure Jira projects for multiple teams working on a single product?

[Paul Henman]

We have 3 teams developing (and supporting) a single product; the teams want to see their own work, but product managers want a view across all work relating to particular features.
Currently we have a Jira project per team, which includes product dev work, bugs, technical improvements (tech debt), etc.  The product managers create an epic in a separate project, and then each team create stories (in their own projects) as children of those epics.
This works well for the dev teams but the product managers can't use the Epic Report or a board showing the epic's stories (for example) to see progress.
The push is to move everything into a single Jira project, but this introduces other problems e.g. how do teams view just their work? We've tried (in a sandbox project) using labels but they're not inherited, so frequently new sub-tasks get filtered out because they forget to add the label.
Surely there's other people working in a similar fashion - how do you organise your Jira project(s)?

[Warren · Accepted solution]

Hi Paul

The standard way of doing this is to use either Labels, or as @Alexey Dorofeyev said, Components. This does rely on "someone" adding the correct Component (or label) to each parent and sub-task. You could also add a custom field which does the same job.

You could then have a board per team, filtering on their Component, and PMs can have their own board as well.

Alternatively, you could use one board and implement a swimlane per team

[Paul Henman]

Is there any field which is inherited? Relying on people to remember to do this is tedious and error-prone. (I think there are paid add-ons to do this, but aren't there any out-of-the-box fields?)

The board per team is how I'm picturing it too; aside from the inheritance challenge, I think this is the simplest way forward.

[Alexey Dorofeyev · Accepted solution]

Components?

[Paul Henman]

I thought Components were limited to a project, so are you suggesting that's how we could filter within a single project?
Are Components inherited by sub-tasks? (I thought not but I've not tried it in a while)

[Warren]

Yes, you should always only have 1 backlog for a product.

No, unfortunately Components aren't inherited, which is why I said (below) that any of these methods are dependent on someone remembering to add the Component in

[Paul Henman]

Thanks

(Sorry, I replied below before I saw this)