As a Jira user, I need the ability to create child issues that belong in another project. As a Jir

Question

Kroger houses their Initiatives and Program Epics into a single project.  This makes the process of tracking the work both from a delivery and financial perspective easier.

Prior to this implementation, teams would create Initiatives for their own work thus creating duplicate Initiatives that rolled up to the same Capital Write-up.  Now we are all delivering against the same corporate Initiative.

Delivery of the Initiatives and Programs can span across multiple workstreams/teams at Kroger.  These workstreams/teams are segmented in different projects within Jira.

Use Case:  I’m a Product Manager and I’m decomposing my work at the Program Epic level.  My Program Epics live in a project named KTDINT.   I need the ability to create child issues that need to be delivered by teams in another project or projects.

I need the ability to select all suggested child issues for a single project

I need the ability to designate which project my child issues will belong to.

Business Impact:  Not having the ability to suggest child issues that belong to other projects reduces the efficiency of using Atlassian Intelligence and will require the user to manually create on different projects

Karan Sachdev · Answer

Hey @Greg Hollis

Welcome to Atlassian Community!

Unfortunately, this isn't an option as of now. When you accept the child issues suggested by the Atlassian Intelligence, they're all created in the project where the Epic belongs.

This has been submitted as a suggestion ticket already. You may add your vote and feedback here: https://jira.atlassian.com/browse/JRACLOUD-85355

Thanks!

John Funk · Answer

Hi Greg - Welcome to the Atlassian Community!

There are a couple of ways to approach this, but you must have at least Browse Project permissions on all of the children projects.

One way is to create a query for the children in the advanced query area (something as simple as: Key in (ABC-123, DEF-456, FFF-234, etc.), do a Bulk change and update the Parent field with your Epic key.

Another is to go into each child and update the Parent directly.