Linked issue does not inherit the content of Parent field
Asked by Pejk? S?ndor:

Hi,

my problem is that the linked issue does not inherit the content of Parent field.

Thanks in advance for the answers


Answers:
author: Rebekka Heilmann _viadee_
body: Hi [@Pejk? S?ndor](/t5/user/viewprofilepage/user-id/4170704)

are you speaking of a Parent/child relationship or actual Issue links?

There is a difference between linking issues (hierarchy independent) and linking Epics to tasks or tasks to Subtasks (Parent-Child relationship).

However, none of it copies content other than a link to either issues by default. You would need an Automation rule for it. If you can give a little more info on what you are trying to achieve, we can probably help you with that.

comments: author: Pejk? S?ndor
body: Hi [@Rebekka Heilmann _viadee_](/t5/user/viewprofilepage/user-id/5182395) I am talking about Issue link. I have an Issue with proper data in the Parent field. Then I have created under that a linked (sub)issue and this (sub)issue does not inherit the content of Parent field.


author: Rebekka Heilmann _viadee_
body: Could you maybe just provide screenshots of where your Issue Link? I am struggling to understand which structure you currently have. Is it:

*Parent-Issue* is Parent of *Issue* ; Issue is parent of Sub-Issue (Sub-task) OR

*Parent-Issue* is Parent of *Issue ; Issue*is Linked to Sub-Issue (other Issue)

If you go into the "Sub-Issue" as you call it. Does your issue look something like this above the summary / name?

![Screenshot 2024-01-18 164411.png](https://community.atlassian.com/t5/image/serverpage/image-id/301262i3C4B1A18D263ABE4/image-size/large?v=v2&px=999 "Screenshot 2024-01-18 164411.png")

or is it a Link like this:

![Screenshot 2024-01-18 164855.png](https://community.atlassian.com/t5/image/serverpage/image-id/301266i3CC5DFA1F44A3E76/image-size/large?v=v2&px=999 "Screenshot 2024-01-18 164855.png")


author: Pejk? S?ndor
body: ![Pic1.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/301268i9D1A18B93FA7658E/image-size/large?v=v2&px=999 "Pic1.JPG")

![Pic2.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/301269i9ADE9BACFF2012D1/image-size/large?v=v2&px=999 "Pic2.JPG")


author: Pejk? S?ndor
body: Actually I try to use Sz?l? (Parent) field the same way as before Epic Link.

Anyway I am an ERP consultant and beside that I try to act as an jira administrator :-).


author: Nic Brough -Adaptavist-
body: Issue links are a totally different thing to parent links. They don't even hold compatible data.


author: Rebekka Heilmann _viadee_
body: Right.

The Link between SUPPF-709 and ECOSUPP-2214 is an "Issue link".

"Issue links" can be established between any Issue Type from any Project (as long as you have permissions in both) and is described by the Link names than can be set for the whole Jira site. This type of link is NOT hierarchical.

The Link between ECOPROJECT-25 and ECOSUPP-2214 is a "Parent-Child" Relationship. Those can be established between Epics and "normal" Issue Types as well as "normal" Issue Types and Sub-Tasks.

If you want SUPPF-709 to have the same "Parent" as ECOSUPP-2214 you either have to set the Parent to ECOPROJECT-25 manually for exisiting issues OR create the new Issue from within the ECOPROJECT-25 Epic. That way, the Parent gets set automatically.

If you want ECOSUPP-2214 to be the parent of SUPPF-709 you would have to create a Sub-Task rather than a normal task from within ECOSUPP-2214.

[Create an issue and a subtask \| Jira Software Cloud \| Atlassian Support](https://support.atlassian.com/jira-software-cloud/docs/create-an-issue-and-a-sub-task/)


author: Pejk? S?ndor
body: [@Rebekka Heilmann _viadee_](/t5/user/viewprofilepage/user-id/5182395) Thanks for your answers.


Tags: cloud

jira-service-management

jira-service-management-cloud