Populating Jira Portfolio View

[Michael Czyzewski]

I have a created a filter that queries based on project in (x, y, z) and status not in (Cancelled) and issuetype = epic and labels in (A, B, C).

I have then created a Jira portfolio view using this filter.  I get the data that I expect, as far as the list of epics, into the portfolio view.

What I'm missing in the view is the Stories, Tasks, etc that are nested under the returned Epics above.  How can I get the portfolio view to include this data as well?  

**The problem is, I can't pull in data from Initiative down, as there are other Epics beneath the initiatives that I don't wish to include - I only want these specfic epics and their children.

[Florian Bonniec · Accepted solution]

Hi

What is the version of Portfolio ? It should be named Advanced Roadmap now?

In some version you can select Initiative you want to include same for Epic, but it' s not the case anymore.

So I guess you have to create a filter for each level.

What you can also do is to structured your JIRA a bit different and have a project for Initiative then having a board or a project for each Team and Import multiple issue sources.

Regards

[Michael Czyzewski]

I'm open to adding a filter, but how can I write a filter to find the children of a subset of epics as found via the first filter?  (Nested where clause, essentially)

[Florian Bonniec]

Some version allow you to pick only Initative you want when creating Source Issues, not sure why they have removed this useful feature in more recent release.

Regarding filter it's not optimal but you can achieve that using scriptrunner.

Let say you create a Filter A with id XXXX1

Project = XX and type = Initiative

Then you can create a filter to get Epics related to those Initiatives

issueFunction in linkedIssuesOf("filter=XXXX1", "is parent of")

You can save this filter and let say the id is XXXX2

Then do the same things for Tasks under Epic

issueFunction in issuesInEpics("filter=XXXX2'")

You can save this filter as XXXX3 and do a last one for SubTask

issueFunction in subtasksOf("filter = XXXX3")

Finally you add all of them as Issue Source.

Regards

[Michael Czyzewski]

This seems to be EXACTLY what I'm needing, except we seem to have some funky set up - I'm getting error "More than one link type with description: is parent of, this is not currently supported"

If I remove the "is parent of", it gets me anything that is linked, which tells me that it should work for what I need - but I don't know how to de-dup our duplicate link types.  :-/

[Florian Bonniec]

You may have to rename the one you have in Issue Linking Menu.

You have created a custom link type with a name that already exist, the one created by Advanced Roadmap. This link is not in the UI but exist (listed in issuelinktype database table).

Below links that come from JSM and JIRA Software by default.

Links with pstyle different from null are links that jira use internaly.

I don't know how to go around that

Regards

[Michael Czyzewski]

#NotAJiraAdmin - :-/

[Florian Bonniec]

I've updated my previours post with more information.

But it would be a good idea to ask your admin to have a look to it.

You can try to not use the link type in the JQL but add AND type in (EXPECTED TYPES)

ex: issueFunction in linkedIssuesOf("filter=XXXX1") and type in (Epic)

[Michael Czyzewski]

Thanks much.  I'll keep looking.  This is a great help!  

I knew we had an add-on for some of these features, but didn't know what it was or what the functions included are.  Now that I know it's script runner, I'll look for docs for that as well. 

[Michael Czyzewski]

Your help was perfect!  I found another function that worked beautifully.

issueFunction in issuesInEpics("filter=xxxx1")

[Florian Bonniec]

issuesInEpics is the second one, it should return what is under the Epic not above.

[Kugie Daguiso]

The second one

[Kugie Daguiso]

Sorry unsufecient  in inglish, I'm here to watch and learn.