Field name – Dependencies -> Child issues

[MA Hakeem]

Hello everyone,

Dependencies -> Parent issue - If this issue is a chlid issue, parent issue will have the JIRA ID of its parent.

In Linked issues we get two drop downs and in the second drop down we get to see select issue. When we give the child issue it should take parent id. And vice versa

The user should be able to clone this on other components but needs to be linked to this original ticket. This will list all child JIRA issues created under this ticket

Dependencies -> Parent issue
If this issue is a chlid issue, parent issue will have the JIRA ID of its parent.

Is this possible if not any alternate solution to do this?

[Nic Brough -Adaptavist-]

No, there's no way to do this.  The key/ID of an issue must be unique, it would be pointless having one that is not.

Why do you think you want to do this?  For what reason would you want an issue to have the same ID as another?

What is wrong with linking two issues together?  An issue link shows the relationship between the two issues, and their unique IDs.

[MA Hakeem]

Its a requirement given by the customer

[Nic Brough -Adaptavist-]

So why does your customer think they want to do this?