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; } } }

Portfolio Issue Sources - Issues without parent out of scope

Zephyr_Admin

In my portfolio plan settings I explicitely excluded issues without parent from the scope. However when I add an issue, which doesn't have a parent, in one of the issue sources for this plan the issue is taken into scope. I would expect that once I configure to exclude issues without parent, it will filter out those issues forever.

When I reconfigure the issue sources after I added the issue, the issue is filtered correctly out of the scope . How can I avoid issues without parent to sneak into my plan without reconfiguring every time?

My issue hierarchy config:

1 Initiative - RFC
2 Change - Epic
3 Story - Story

RFC issues come from project 'RFC'
Epics and Stories come from projects A, B & C

The issue sources for my plan are

-RFC
-A
-B
-C

So I want only have issues in scope from A, B and C which have a parent issue RFC

Accepted answers

Thomas_rff8bi

Hi @Zephyr_Admin,

What could work is setting up a JQL filter that would look like Project = RFC OR (PROJECT IN (A, B, C) AND "Parent Link" IS NOT EMPTY) and using that JQL filter as the issue source.

This would solve most of the cases but not the case of a story belonging to an epic that does not belong to an initiative.

For that you would need an addon like scriptrunner to allow you to query in a recursive manner.

Hopefully that will point you in the right direction!

Cheers,

Thomas

All comments

Thomas_rff8bi

Hi @Zephyr_Admin,

What could work is setting up a JQL filter that would look like Project = RFC OR (PROJECT IN (A, B, C) AND "Parent Link" IS NOT EMPTY) and using that JQL filter as the issue source.

This would solve most of the cases but not the case of a story belonging to an epic that does not belong to an initiative.

For that you would need an addon like scriptrunner to allow you to query in a recursive manner.

Hopefully that will point you in the right direction!

Cheers,

Thomas

Zephyr_Admin

Thnx @Thomas. The JQL works but indeed not for the stories. I will try scriptrunner.

Keep finding it weird that portfolio plan setting is ignored once configured

Software Managers

Has there been any progress on this portfolio issue? It doesn't make sense to need an addon or use JQL filter to keep new issues and stories from entering into a project plan.

Thomas_rff8bi

Portfolio issue source boils down to a JQL filter one way or another. A JQL filter is not a one point in time issue list but a dynamic list of issue that will include anything new that comes up.

If you are interested with a non-changing list you could consider adding to the JQL filter something like "AND createdDate <= '2017-09-04'" to ensure that nothing new makes it to the list.

Bottom line, the plan issue source is not ignored once configured but it's just a filter rather than a list of issues.

Cheers,

Thomas

george gerodimos

Posted this on another thread as well:

Had the same issue where Epics have children (Story) and in various stages of completion, yet Portfolio would not pick any of that up, After much looking around, I noticed it was happening on a filter was using labels.

Anyone else?

Welcome!

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

Quick Links

Find more posts tagged with

jira

advanced-roadmaps