Is there a way to assign a story to 2 separate JIRA products?

[Jordan Trinklein]

We have a front end engineer who works on 2 teams, but some of the stories affect both teams. We'd love to find a way to have a story appear on both project boards for visibility. Is there a way to do this outside of cloning a story and migrating it to the other project?

[John Funk]

Hi Jordan,

Yes, this is easy to do. We have created a custom field with values for Shared Teams. Then we boards that use the value of the field. So in your example the board filter might say Project = A and Shared Team = Yes. Then the same card will show up on both Team A and Team B. 

Or should could use something similar to Bill's suggestion with a Component value or Label value. 

[Bill Sheboy]

Hi @Jordan Trinklein 

I have some process and Jira questions that might help the community answer your request better:

• Are you using Classic or NextGen projects in Jira?
• For the work which affects both teams, what does "affects" mean?  That is, do they just need to see progress, or are both of the teams participating in doing the work?

You probably do not want to clone a work item just so people can see it; you want to make the single work item visible.

A great way to do that is to either figure out a way to split the work so it is independent for the teams.  This reinforces an agile idea of breaking dependencies rather than enabling/mitigating them.

Otherwise (and if you are using classic projects) you could make a third board, which only shows shared work using a filter spanning both projects.  For example, based on a label or component value (e.g. SHARED).  When teams need visibility to the shared work, they go look at this board, but do not move any items on it.

Best regards,

Bill