Hierarchy starting from project

Questions & Answers
1

I have a simple hierarchy:
Task in PRJ0 links (contains) Bugs in PRJ1, PRJ2
image

I want to get this hierarhy in Eazy, like this
image

The only working report I was able to build is…
image

[jira.customfield_task]
name = "TASK"
inward_link = "is contained in"
issue_type = "Task"
update_from_issue_key = "customfield_bug"

[jira.customfield_bug]
name = "BUG"
outward_link = "contains"
issue_type = "Bug"

[[jira.issue_hierarchies]]
name = "PRJ-TASK-BUG"
all_member_name = "PRJ-TASK-BUG"
levels = [
    {name="Project",key_column="project_key"},
    {name="TASK",key_column="customfield_task", issue_type="Task"},
    {name="BUG",key_column="subtask_parent_key"},
    {name="Subtask",key_column="subtask_key"}
]

Is there any solution to my case?

2

Hi @cybertachikoma,

Each issue should have a place in the hierarchy, even those not Tasks or Bugs. Those issues would remain at the Parent level, where no issue types are specified, and I would advise leaving it so.

You might want to make a few changes to your hierarchy to make it work.

  1. Add a definition for the Project level so eazyBI can check on the project of the Task issue and pass the value down for creating a hierarchy

  2. Validate the link name and direction for the “TASK” definition. Please validate the link name and direction for the Bug issues.
    Note that the link name and direction should match as you see it from the Bug perspective (see the 1. troubleshooting step Additional Issue hierarchies - Troubleshooting).

  3. Remove the definition for the “BUG” as it is covered by the default Sub-task hierarchy already. It is similar to the first example described in the documentation (Additional Issue hierarchies).

The updated advanced settings might look like this:

[jira.customfield_parentproj]
name = "TASK PROJECT"
data_type = "string"
update_from_issue_key = "customfield_task"
javascript_code = '''
  if (issue.fields.project) {
    issue.fields.customfield_parentproj =  issue.fields.project.key
  }
'''

[jira.customfield_task]
name = "TASK"
inward_link = "is contained in"
issue_type = "Task"
update_from_issue_key = "parent_issue_key"

[[jira.issue_hierarchies]]
name = "PRJ-TASK-BUG"
all_member_name = "PRJ-TASK-BUG"
levels = [
    {name="TASK PROJECT",key_column="customfield_parentproj"},
    {name="TASK",key_column="customfield_task", issue_type="Task"},
    {name="BUG",key_column="subtask_parent_key"},
    {name="Subtask",key_column="subtask_key"}
]

Best,
Zane / support@eazyBI.com

3

Thank you, It works!
image

But than I’ve used it for real data, found some strange behaviour:

[jira.customfield_d_parentproj]
name = "d_PROJECT"
data_type = "string"
update_from_issue_key = "customfield_d_change"
javascript_code = '''
  if (issue.fields.project) {
    issue.fields.customfield_d_parentproj =  issue.fields.project.key
  }
'''

[jira.customfield_d_change]
name = "d_CHANGE"
inward_link = "is contained in"
issue_type = "Change"
update_from_issue_key = "parent_issue_key"


[[jira.issue_hierarchies]]
name = "d_PRJ-CHANGE-CTE-CONTAINS"
all_member_name = "d_PRJ-THEME-INIT-CHANGE-CTE-CONTAINS"
levels = [
        {name="d_PROJECT",key_column="customfield_d_parentproj"},
        {name="d_CHANGE",key_column="customfield_d_change", issue_type="Change"},
        {name="d_CONTAINS",key_column="subtask_parent_key", issue_type="Epic"},
        {name="Subtask",key_column="subtask_key"}
]

((project in (T02_PERS) AND issuetype in (Change)) OR (issueFunction in linkedIssuesOf("project in (T02_PERS)  AND issuetype in (Change)", contains) AND issuetype = Epic))

I’ve used this hierarchy an JQL to get such a report " all Epics contained in issues of issuetype ‘Change’ from project T02_PERS "
image
image

And mostly it works:
image

But what about this issues separated by comma?
image

Projects PERSPRG , T10_CLTCOM are not included in JQL but listed in report…
image

I’ve found that such cases happen then Epic “contained in” another Change
image

How can we use in report just Changes from project T02_PERS?

4

Hi @cybertachikoma,

Issue keys separated by comma shows that issue links have multiple to multiple relations between Change and Epic. And that kind of relationship is not supported for building a hierarchy. The new issues hierarchy could be built when an issue has only one parent; in your case, Epic should be linked to only one Change (its parent). If one Epic could be part of several Changes, then there is no hierarchy (Additional Issue hierarchies).

In case of multiple to multiple linking, you can import issue links as separate dimensions without building a new hierarchy. I would recommend creating two issue link dimensions so you could use one or another that suits better to the report:

  • “Linked Change” representing Change issues
  • and “Linked Epic” representing Epic issues.

In the report, you may use one of the link dimensions and the “Issue” dimension to see the relation. For example, choose the “Issue” dimension to show Change issues and group them by Projects and then select “Linked Epic” to see the list of linked Epic issues.

Here are details on how to import issue links as dimensions: Import issue links.
The advanced settings for linked Epics might look like the one below. Before using, please double-check and update the link direction and name to match your data.

[jira.customfield_containepic]
name = "Linked Epic"
inward_link = "contains"
issue_type = "Epic"
dimension = true
multiple_values = true

Best,
Zane / support@eazyBI.com

5

Thanks, that helped.
I was able to get contained epics.

image

But,

Is it possible to get this epics just in the bottom of Changes hierarchy?
hierarchy could be enriched with some more parents like this:
image

but basically, lets say about simpliest:

[jira.customfield_h2_change]
name = "h2_CHANGE"
inward_link = "is contained in"
issue_type = "Change"
update_from_issue_key = "parent_issue_key"

[[jira.issue_hierarchies]]
name = "Changes"
all_member_name = "Changes"
levels = [
        {name="h2_CHANGE",key_column="customfield_h2_change", issue_type="Change"}

]

image
image732×787 38.4 KB

6

Hi @cybertachikoma,

Making a new hierarchy pays off when there is a hierarchical structure. If you would like to group Epics by linked issues, then you might want to choose a simpler and more robust solution and import issue links as a separate dimension (Import issue links).

If you choose to make the hierarchy, remember to list also the lower hierarchy levels according to Sub-taks or Epic hierarchy. Please review the troubleshooting paragraph, point 5: Additional Issue hierarchies.

7

Hi, Zane

Let me remind you the report I’m triying to create:
image

I was able to create a hierarchy completed with customfield as a measure that returns Epics contained in Change. It was created using Scriptrunner, calculated in Jira, called “cfield_contained_epics”
image

Second field “cfield_count_contained_epics” returns the size of array of contained epics to Change.
Now I wonder - how to get the sum of epics in the bottom of report?

image
image505×588 25.1 KB

I’ve tried to use Tuples, but didn’t successed. But I believe Robert Cacus’s idea is close to Solution