JQL story/bug to idea (product discovery) link

[Andy]

We use jira product discovery to manage our high level product strategy, and two separate jira software projects to manage the delivery of this strategy. We link the ideas in the product discovery project A to issues in jira software projects B and C for the purposes of tracking idea delivery. We want to run a report from project B and C detailing the issues currently being worked on by the engineering team, but maintain a link back to the strategic view by including the idea in project A for which a given issue in B or C is a delivery task.

things i've already tried:

Parent field returns epic in B or C

Parent link doesn't seem to contain any data

report from project A on delivery status of issues in B or C doesn't give sufficient granularity; all that I can see is a progress bar without any information about the issues being worked on.

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Yes, the parent link really is just a pointer to another issue.

Jira doesn't embed data into links or references, it just points to the target issue.  It's actually up to the report (or screen, or display) to extract data from the target at the other end of a link if it needs it.

Which report(s) are you looking at at the moment?

I'm not familiar with JPD enough to know if there are any reports that can do this sort of thing.  

[Andy]

Hi Nic,

We aren't using an inbuilt Jira software report, we're trying to use JQL to get a list of delivery tasks fulfilling certain criteria, and then send these as email via the Automated Release Notes plugin. We can do this easily enough for issues where we aren't concerned with the parent idea in JPD, but as soon as we try to find all the delivery tasks which have a particular parent idea, it all comes unstuck.

I would also be happy with a way to show the parent JPD idea in jira search results, because if we can do this, we can at least maintain visibility of the high level objectives satisfied by delivery tasks rather than having to refer back to the JPD board.

Many thanks,

Andy

[Anand Inamdar_Amoeboids]

Hi @Andy ,

Anand here from Team Amoeboids (developers of Automated release notes app, you mentioned above). This is an interesting scenario you mention here.

Have you checked the possibility of using Jira's native automation to pull may be summary/title of the issue from JPD into JSW issue custom field? Then this custom field can be used within ARN templates.

Please forgive my lack of knowledge around JPD. Above suggestion is based on the assumption that ideas in JPD are fundamentally Jira issues. 

Best,
Anand

[Nic Brough -Adaptavist-]

Yes, this is an interesting one. 

Ameboids release notes is really good for development projects, and also works well when people do releases from support or simple "get stuff done" non-development projects. 

But I've not tried it with JPD.  Like Anand, I understand JPD issues to be Jira issues with stuff added on top (like the way Software and Service-Management layer things over a core issue), so I would expect it to work in a similar way.