Single Epic for multiple teams

[Gilad Katz]

Hi,

Current situation:

We are 3 dev teams (2 for Web, 1 for Native App), using same Jira project with separate board for each team. We use a custom field called "Team" to filter tasks for each team's board.

Most of the tasks needs to be assigned to 2 teams - one for a web team and another for the native app team. 

Usually we open an Epic per feature, then clone the stories within it for each team.

The problem we are facing:

Lots of manual work is required in cloning tasks just to keep it on all teams' boards, which also makes it easy to lose track of tasks. 

Is there a best practice to manage 1 epic for multiple teams?

Thank you,

Gilad

[Jack Brickey · Accepted solution]

Hi @Gilad Katz , I am not sure I follow you completely here. Epics do not belong to any specific team. You can have issues within an epic that are assigned to individuals across various teams. In that way the epic can be used by multiple teams to gather their issues under given epic/initiative.

[Gilad Katz]

Hi @Jack Brickey , thanks for your reply. 

Currently we are assigning an Epic to a team, although as you mentioned it doesn't really matter since the issues within it are the ones which appear in the team board. I'll try to explain what we're looking for:

When working cross platform on both Web + Native app - Is there any Jira best practice or automation to help us keep in sync between the different teams, so that when one product manager opens an Epic, all other PMs are aware of it and can prioritize the feature to their team?

For example: Web PM opens a feature for search enhancement. Web dev team picks this feature. What's the best way for native app PM + dev team to know about this feature so they can also prioritize it? 

We're aiming to solve 2 things:

1) Teams can get un-synced. For example, Web platform can do things without Native team knowing about that, causing a different feature set on each platform.

2) When we are synced, there's a lot of manual work in cloning issues within an epic

Hope that clarifies a bit

Thanks again

[Jack Brickey]

Based on what you conveyed I would suggest using automation. Something like below.

trigger = issue created

condition = type = epic

condition = anything else to help qualify before executing action

action = add other PMs at watcher

action = add comment "hey you might be interested in this new feature request"

[Gilad Katz]

Simple and does the work. Thank you @Jack Brickey !