nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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.

Accepted answers

Florian Bonniec

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

All comments

Florian Bonniec

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. :-/

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server

advanced-roadmaps