Portfolio dimension / get key from issue

[MaxL]

Hello,
I have a problem that I simply cannot solve.
We have a hierarchy using portfolio parent links: request> epic > story
“Requests” are in a special jira-project (REQ), the underlying issues (and hours logged) are in different jira projects (one per team). A typical scenario is: build a report that shows the information of the REQ-issue that can be filtered via pages but show the aggregated hours and estimated from the various issues and different teams/jira projects.

Usually to get the amount of hours spent per “request” and team I simply use the built-in portfolio dimensions which works great. However using this dimension I cannot use the pages-filters anymore because for example the “status” of the main REQ-issue is different than the status of the issues further down the hierarchy, but the pages-filter is applied to all issues, not just the main ones.

My idea is to use the issue-dimension and then have a calculated measure with a tuple that looks up the current issue key in the portfolio dimension returning that number using “getMemberbyKey”.

Now if create a static tuple for one “request” it seems to be working fine, the hours are correct:

(
[Portfolio Request].[REQ-123],
[Issue].DefaultMember,
[Measures].[Hours spent]
)

However I simply cannot get the GetMemberbykey working:

(
[Portfolio Request].GetMemberByKey(
[Issue].CurrentMember.Key
),
[Issue].DefaultMember,
[Measures].[Hours spent]
)

is just throwing me an error:

#ERR: mondrian.olap.fun.MondrianEvaluationException: Expected value of type MEMBER; got value 'mondrian.olap.fun.MondrianEvaluationException: Exception while executing function getMemberByKey: java.lang.ClassCastException ’ (class mondrian.olap.fun.MondrianEvaluationException)

even though

[Issue].CurrentMember.Key

is showing me the key of the issue of the line in question.

I spent hours looking for an answer on your forums but every time I try to adapt a solution it’s not working. I would very much appreciate your help and advice. Apologies if the answer has already been given elsewhere.

Thank you and best regards
Max

[MaxL]

Any help would be appreciated

[gerda.grantina]

Hi @MaxL ,
If you want to filter issues by “parent” issue status, you can try to create an issue linked field dimension.
In eazyBI community you can check similar answers about this type of use case:

Issue link field dimensions don't include parent issue

Hi @Stuart, You are very close to the solution, the line you need to change is issue_key_column = "customfield_16400" to this one issue_key_column = “jpoh_parent_3”. [[jira.issue_link_field_dimensions]] name = "Feature Release" source_dimension = "Fix Version" issue_key_column = "jpoh_parent_3" group = "Linked issue dimensions" There is also the possibility to use different levels from Portfolio with this line - jpoh_parent_3, the number at the end is counted like this: [Issues_-Jira_Portfo…

Report based on inherited attribute across hierarchy

In eazyBI, you can import an issue linked field dimensions for issues in Sub-task, Epic, and Portfolio hierarchies. This option works for standard dimensions, like Label, Priority, Fix version, and other: Issue link field dimensions - eazyBI for Jira. You can also create a similar dimension on another issue field from the Portfolio hierarchy as long as it is a single-select custom field. In that case, you may define a new JavaScript calculated custom field that would return custom field value a…

best,
Gerda

[MaxL]

Hi @gerda.grantina , Thank you so much, I’ll give it a try!
with best regards
Max