Linking stories from different projects into same Epic

[Sebastian Ljungberg]

Hello,

At my company we are working with Component based development team and trying to force this onto JIRA. Each component team got a project and the overall management are handled form a Project Management project that hosts all epics. Currently we have to create user stories through that epic, and then move them to correct component project to keep the link to the Epic. Is it possible somehow to add a system/custom field to stories created in a component project, in which you can connect to Epics from another project (the PM one)? We are using latest JIRA and GreenHopper.

[Peter Van de Voorde · Accepted solution]

Hey Sebastian,

It all depends on the boards you are using, you can use epics across project.

Look here for more info : https://confluence.atlassian.com/display/GH/Working+with+Epics

Best regards

Peter

[Chris McFadden]

You can update your filter so that the epics come from multiple projects. For example "(issueType=Epic and project in (AA,BB,CC)". Maybe it would be best to put your epics in a separate backlog project.

[Simon N]

This is really helpful. Epics appear on your board in the same way that any other issue does, so you you can use the board filter to include epics from other projects.

My only hurdle now is that I'm trying to assign a issue from a non-next-gen project to a next-gen project epic. The epics from the next-gen project appear on my  non-next-gen project backlog view, but when I drag a issue to an epic, it says that the epic must be of the type 'epic'. I'm guessing non-next-gen projects have a different epic type with the same name :(