Is it possible to the show spawned by issue in Jira Roadmap/Plan
Asked by Jeffrey B Peterlin:

Is it possible to show the "spawned by" issue link for an issue (if applicable) as a field in Jira Roadmaps/Plans?


Answers:
author: Walter Buggenhout
body: Hi [@Jeffrey B Peterlin](/t5/user/viewprofilepage/user-id/3543176),

That sounds like a custom link type that was configured in your Jira site. You can add additional link types to appear in plans from the overall settings (accessible from *Plans \> Settings \> Dependencies*).

You can add a link type from your instance there.

Hope this helps!


author: Lisa Forstberg
body: Hi [@Jeffrey B Peterlin](/t5/user/viewprofilepage/user-id/3543176) ,

Well almost...You can show "dependencies" as a field - that will give you information about incoming or outgoing issue links. The arrow gives you more information.

![Screenshot 2024-09-12 at 18.12.57.png](https://community.atlassian.com/t5/image/serverpage/image-id/347151i09146911B3DCADF7/image-size/large?v=v2&px=999 "Screenshot 2024-09-12 at 18.12.57.png")

br

Lisa

comments: author: Jeffrey B Peterlin
body: Hello [@Lisa Forstberg](/t5/user/viewprofilepage/user-id/5101516)

More information: We have a Jira Service Management Project (let's call it **Intake Service Desk** ) that serves as an intake for company-wide issues. Once an issue from that Project (its key name is **ISD**) is reviewed and accepted to a specific Project's backlog, it spawns an issue specifically to that Project (and that Project's key name).

For example, the Jira Service Management Project (**ISD** ) could have an issue designated as **ISD-100** : *I cannot access a certain portal* . After reviewing/accepting it to the appropriate Project's backlog (like **U** ser **A** ccess **P** roblems, it would spawn **UAP-222** : *I cannot access a certain portal*.

When I am looking at issue **UAP-222** , it will show **ISD-100** in the **Linked issues** section (under *spawned by*).

In my roadmap, I will show **UAP-222** (under an appropriate Epic) in the issue column, followed by Sprint, Release, Due Date, Status, Assignee, etc.

My ask: is there is a way to have a field (which I don't believe is a custom field) that would should another column (indicating the issue key from where it originated, in this case a column would show **ISD-100** --the issue from where **UAP-222** was spawned).

Per suggestion(s): I added both the Incoming dependencies and Outgoing dependencies fields and the only options I get for both is Blocks or Depends On (and neither are appropriate).

Thoughts?


author: Lisa Forstberg
body: Hi!

I see what you want but you can't pick and choose a specific link type and display only that key (ISD-100) in a field (column in plans) in a Plan. The standard field "Linked issues" seems not to be accepted at all in a Plan..

When looking at a filter result the "Linked issues" field will display all links

![Screenshot 2024-09-13 at 08.41.42.png](https://community.atlassian.com/t5/image/serverpage/image-id/347268iB92F3BACF6845498/image-size/large?v=v2&px=999 "Screenshot 2024-09-13 at 08.41.42.png")

When you spawn, are you using an automation? If an automation you could hack it to store the key of the original issue (ISD-100) in a custom field as an action during your automation. Add that custom field to your plan and then choose that as a column.

Also for the Plans dependencies. You configure centrally what link types should be available for Plans. if you seem to be missing "spawned by" you can add that link type to be used. See Product \> Plans \> Dependencies

br

Lisa


author: Jeffrey B Peterlin
body: Thank you [@Lisa Forstberg](/t5/user/viewprofilepage/user-id/5101516)! I implemented your suggestions above, and they worked!


Tags: advanced-roadmaps

cloud

jira-cloud

plans