Linking to tickets (non-delivery) problem
Asked by Erin Mihalik:

I have a Jira Software ticket that is not the delivery work. It is a JS project that we use for new feature intake. I linked it via the "Added to Idea" link.

It shows correctly on the JS ticket as linked BUT it is not showing as linked on the JPD project.

Am I doing something wrong?

![2023-07-21_13-35-44.png](https://community.atlassian.com/t5/image/serverpage/image-id/270472iB243DDAE003D856B/image-size/large?v=v2&px=999 "2023-07-21_13-35-44.png")![2023-07-21_13-35-58.png](https://community.atlassian.com/t5/image/serverpage/image-id/270473iECA9E577B5D4ED73/image-size/large?v=v2&px=999 "2023-07-21_13-35-58.png")![2023-07-21_13-36-13.png](https://community.atlassian.com/t5/image/serverpage/image-id/270474iBB6271D19C55B768/image-size/large?v=v2&px=999 "2023-07-21_13-36-13.png")


Answers:
author: Tanguy Crusson
body: HI [@Erin Mihalik](/t5/user/viewprofilepage/user-id/4743833) , [@Chris Timms](/t5/user/viewprofilepage/user-id/1260719) was close: it's a reserved link type, and we need to find a way to hide it from the selection.

This one ("is idea for/is insight for") is used if you add an issue as an insight to an idea (but adding this link type is not sufficient for that: you need to either add the issue from the insights tab, or use the chrome extension or API).

The other reserved link type is for "implements/is implemented by" which is used for the delivery tab.

I suggest you use another link type (e.g. "relates to")

comments: author: Erin Mihalik
body: Thanks! That helps. The difficulty there is that it is not "reserved" on the other side. So if coming from software project in, it is still selectable. Also when doing it that way, there is no "linked issue" which I know has been brought up before. The linked issues list can be a very important view.

What are the reasons for putting it behind "reserved"? Could it still not be available to all but also used when an Insight is added?

I hope you all consider this. Filtering through Insights to see linked issues is not ideal. A quick access list to all linked issues that is easy to read is better. Also having a link type that is still more unique to the project like "Is Idea For" makes it much easier to do automation.

Options:

1. Switch to Relates to get Linked Issues list but no Insight or Insight rating.
2. Use Relates linked issue BUT also add Insight to get Insight rating
3. Add insight so you can use Insight rating but you lose the Linked Issue list

Ideally, if one chooses to use the Insights logic for linked issues, then both the Insight and Link should display. If one chooses to only use linked issues, then the Idea link types should be available on both sides or not available on one side.


author: Chris Timms
body: Hi [@Erin Mihalik](/t5/user/viewprofilepage/user-id/4743833) ,

"Is Idea For" and "Added to Idea" will add the link to the **Delivery** tab in the issue. In you're screenshot, if you click on the Delivery tab you should see it there.

All other link types will add a link to the issue under the issue description in the way you expect.

Regards,

- C


author: Stacy Smith
body: [@Erin Mihalik](/t5/user/viewprofilepage/user-id/4743833) - I'm not ?sure due as a better screen shot could help me better understand.

You should be able to use the Link feature in JPD or in JS and select "relates to" or similar. This will create a linked relationship between the JPD \<--\> JS issue without adding the JS issues to the JPD Delivery.

Another observation from me is that you might need to refresh the JPD as if you just liked the JS issue the JPD might not yet have refreshed.

comments: author: Erin Mihalik
body: [@Stacy Smith](/t5/user/viewprofilepage/user-id/4669576) yes related to does show correctly. I am able to use all other links correctly.

The "Is Idea For" and "Added to Idea" are specific to Jira Product Discovery and links created for the use of this tool so I was hoping to use them. That way if we set up automation, I can tie it to the specific link type.