Portfolio Issue Sources - Issues without parent out of scope

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

1 answer

1 accepted

0 vote

Hi @Jasper Uyttebroek,

 

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

Thnx @Thomas Barthelemy. 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

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. 

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

Where can we modify this JQL? When I go to issue sources, I don't see this option.

Thanks

@François Eric

Not possible to directly input JQL in portfolio issue sources.

You need to write your JQL in  'Issues > search for issues' and save it as a filter.

Then you can select this filter in portfolio issue sources

@Thomas Barthelemy

If issue source boils down to a JQL filter why having then 'Include issues without parent' option?
This looks like a subfilter, but only applied once.
Makes no sense. Either the choice to include issues without parent should persist otherwise drop the feature, it's useless and misleading
I favor the first option, because keeping a plan's scope clean and stable is a must for all projects.

Thanks!

PS: I haven't yet encountered your issue but that will definitely be a problem for me too. 

@Jasper Uyttebroek

"If issue source boils down to a JQL filter why having then 'Include issues without parent' option?"

I think there is a misunderstanding here and I will follow up with the Portfolio for JIRA Server tech writter to clarify the documentation if necessary.

There is no such option in the first place, but thanks not giving up on what you believe does not make sense, as I finally understood where the confusion happened.

When confirming what's in Scope when creating a Portfolio plan or editing its issue sources you have the possibility to Exclude some specific issues from the plan.

If you are at the Epic level and some stories do not belong to an epic then they are categorized under "Issues without parent Epic". Unselecting this would mean excluding all the issues in that list, alternatively you can un-check all those stories one by one to acheive the same result.

scope_exclude_sample.png

 

Hopefully this clarifies the situation, thanks for the feedback!

 

Cheers,

Thomas

@Thomas Barthelemy

Thx for clarifying. I had indeed another understanding of the concept.

Nevertheless the requirement to exclude orphan issues remains. I ll go with scriptrunner plugin. But a pity I have to use and pay for a 3th party plugin. Would be nice if this kind of JQL function would ship with Portfolio. Current Portfolio JQL functions are a bit poor I find. 

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Monday in Jira Software

How large do you think Jira Software can grow?

Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...

708 views 6 13
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you