You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi JPD team,
I noticed that the link type "added to idea" and "is idea for" are available in Jira Cloud to link issue types to a JPD project, but not vice versa in JPD.
(1) In our Jira Cloud project, I link an Epic with "added to idea" to an issue in JPD.
(2) Then I would expect this linked issue to pop up with the "is idea for" link type on the JPD side, but it does not have any linked issues:
(3) If I then try to configure a linked issue from the JPD side to Jira Cloud, no link types such as "added to idea" or "is idea for" are options to select from.
Any reason for this? What is the purpose of these link types?
Hi @Mart Postma ,
Below I'll try to discuss the difference between the Polaris link types - but I think it's important to preface the Polaris link types are specific to JPD.
Polaris issue link:
This issue link relates to creating a delivery from a JPD idea. When a JPD idea creates a delivery, the idea "is implemented by" the delivery, and the delivery "implements" the idea. Here is an example of a delivery linked to an idea:
Polaris datapoint issue link:
This issue link relates to adding a JPD idea as an insight to another JPD idea. If idea A is added as an insight to idea B, idea A is the "added to idea" for B - while idea A is then an "is idea for" idea B:
Polaris merge issue link:
This issue link relates to merging ideas. One or more ideas can be selected, and merged into another idea:
If ideas are merged into another, they would be shown as "merged from" on the "merged into" idea. For example, ideas A and B were merged into idea Z:
So I hope that explains a bit more the purpose of these. I also understand these link types can be selected under a Jira issue - but again they are tailored for JPD specifically.
Hi @Nick H
Thanks for your elaborate answer.
Whereas I understand the purpose of the link types now, I still think that it should not be possible to have links from Jira to JPD without seeing the link on the other side show up.
What are your thoughts about this usecase to link Jira Epics/Stories/Bugs to JPD as "is idea for" an idea rather than it only being the ticket for delivery status?
I believe that already existing issues in Jira could contribute to an idea in JPD and that the workflow should not just be (1) we have an idea in JPD, (2) we want to ship that idea so we create new delivery tickets in Jira.
Assuming that companies/users have a backlog in Jira that they want to organise by using JPD, it should be possible to follow these steps vice-versa.
Just my train of thought here.