How to define a hierarchy based on Portfolio

Questions & Answers
1

Hi eazyBI Team

I am currently evaluating eazyBI for JIRA server in order to provide advanced reporting.
Among of them, we are targeting to provide report for a SAFe implementation done with JIRA Software and JIRA Portfolio.

A current implemented hierarchy is our Portfolio is as follow :

  • Epic Business
    • Capability
      • Feature
        • User Story
          • Sub-Task

The hierarchy is managed witth the Parent Link customfield
Since the fields return Issue Key + Name, I have implemented different calculated fields, based on :

  • a Scriptfield “Parent Link Key” (id=25752) able to return the Issue key of “Parent Link”.

[jira.customfield_25752]
data_type = “string”
update_from_issue_key = “epic_key”

[[jira.issue_hierarchies]]
name = “Epic Business”
all_member_name = “All Issues by Epic Business”
levels = [
{name=“Epic Business”,key_column=“customfield_25752”,issue_type=“Epic Business”},
{name=“Capability”,key_column=“customfield_25752”,issue_type=“Capability”},
{name=“Feature”,key_column=“epic_key”,issue_type=“Feature”},
{name=“User Story”,key_column=“epic_parent_key”,issue_type=[“User Story”,“User Story Technique”]},
{name=“Sub-task”,key_column=“subtask_key”}
]

The hierachy was not consistent.

  • Javascript field directly in

[jira.customfield_epicBusiness]
name = “Epic Business”
data_type = “string”
dimension = true
separate_table = true
javascript_code = ‘’’
if (issue.fields.customfield_25752) {
issue.fields.customfield_epicBusiness= issue.fields.customfield_25752;
}
‘’’

[jira.customfield_capability]
name = “Capability”
data_type = “string”
dimension = true
separate_table = true
javascript_code = ‘’’
if (issue.fields.customfield_25752) {
issue.fields.customfield_capability = issue.fields.customfield_25752;
}
‘’’

[jira.customfield_feature]
name = “Feature”
data_type = “string”
dimension = true
separate_table = true
javascript_code = ‘’’
if (issue.fields.customfield_25752) {
issue.fields.customfield_feature= issue.fields.customfield_25752;
}
‘’’

[[jira.issue_hierarchies]]
name = “Epic Business”
all_member_name = “All Issues by Epic Business”
levels = [
{name=“Epic Business”,key_column=“customfield_epicBusiness”,issue_type=“Epic Business”},
{name=“Capability”,key_column=“customfield_capability”,issue_type=“Capability”},
{name=“Feature”,key_column=“customfield_feature”,issue_type=“Feature”},
{name=“User Story”,key_column=“epic_parent_key”,issue_type=[“User Story”,“User Story Technique”]},
{name=“Sub-task”,key_column=“subtask_key”}
]

I did not have also the expected result.

  • ScriptField “Parent Issue key” (id=25753), where the field returns the key of the Parent Issue using the correct link mode (Customfield “Parent Link” or “Epic Link” or “Parent Sub Task” Issue Link)

[jira.customfield_25753]
name = “Parent Issue”
data_type = “string”
dimension = true

[[jira.issue_hierarchies]]
name = “Epic Business”
all_member_name = “All Issues by Epic Business”
levels = [
{name=“Epic Business”,key_column=“customfield_25753”,issue_type=“Epic Business”},
{name=“Capability”,key_column=“customfield_25753”,issue_type=“Capability”},
{name=“Feature”,key_column=“customfield_25753”,issue_type=“Feature”},
{name=“User Story”,key_column=“customfield_25753”,issue_type=[“User Story”,“User Story Technique”]},
{name=“Sub-task”,key_column=“customfield_25753”}
]

In this latest test also, I do not have the expected result.

image
image1064×534 22.1 KB

In the screenshot, you see the hierarchy I have.
Normally, we have :

  • PP2-34 as Epic Business
  • PP2-37 as Capability
  • PP2-40 as Feature

As you see, the proposed hierarchy gives :

  • PP2-34 > PP2-37 > PP2-34 > PP2-34 > PP2-34
  • PP2-37 > PP2-37 > PP2-40 > PP2-37 > PP2-37

Please, let me know how to process ?
Where is my error ?
Is the root cause related the fact that Customfield Link between different levels of Issue in Portfolio are defined by the same Customfield “Parent Link” ? Must I created a dedicated one of each level ?

Thanks by adavance
Vincent