Setup Hierarchy with 4 layers via parent field and top layer via issue link

[alex.xm]

I have the following hierarchy setup in Jira which are :
Initiative->Epic->Story/Task/Bug/Spike->Sub-task
This was done by adding “Initiative” to the hierarchy in the jira settings MYDOMAIN.atlassian.net/jira/settings/issues/issue-hierarchy. So on an epic you simply set the parent to be the initiative

Then, we have an additional layer on top which is the issuetype “Idea”. This is from Jira Product Discovery (JPD). We link Ideas to Initiatives via this feature in JPD called “Delivery Tickets”. When I use the Jira REST API to fetch an Initiative, I can see that this relationship is actually just an issuelink:

                            'type': {'id': '10007',
                                     'inward': 'is implemented by',
                                     'name': 'Polaris issue link',
                                     'outward': 'implements',
                                     'self': 'https://MYDOMAIN.atlassian.net/rest/api/2/issueLinkType/10007'}}],

I tried following the instructions here How to create an additional issue hierarchy but I haven’t gotten it to work yet.

I first tried via the epic hierarchy, but I couldn’t even get the initiative-epic relationship to link in the eazybi report. I think it’s because it’s because initiatives & epics are linked via parent and not an issue link:

[jira.customfield_initiative2]
name = "Initiative2"
inward_link = "is child of"
issue_type = "Initiative"
dimension = true
update_from_issue_key = "epic_key"

[[jira.issue_hierarchies]]
name = "Alextest - epic"
all_member_name = "Alextest - epic"
levels = [
  {name="Initiative3",key_column="customfield_initiative2",issue_type="Initiative"},
  {name="Epic",key_column="epic_key"},
  {name="Parent",key_column="epic_parent_key"},
  {name="Sub-task",key_column="subtask_key"}
]

Then I tried the jpoh hierarchy. I was able to get Initiatives & Epics to link, but I can’t get Ideas & Initiatives to link

[jira.customfield_idea2]
name = "Idea"
inward_link = "is implemented by"
issue_type = "Idea"
dimension = true
update_from_issue_key = "jpoh_parent_3"

[[jira.issue_hierarchies]]
name = "Alextest - jpoh"
all_member_name = "Alextest - jpoh"
levels = [
  {name="Idea",key_column="customfield_idea2",issue_type="Idea"},
  {name="Initiative",key_column="jpoh_parent_3",issue_type="Initiative"},
  {name="Epic",key_column="jpoh_parent_2"},
  {name="Parent",key_column="jpoh_parent_1"},
  {name="Sub-task",key_column="subtask_key"}
]

If anyone has any ideas, please let me know

[Elita.Kalane]

Hi @alex.xm

Welcome to eazyBI Community!
I tried to recreate your scenario on my test data. If I got all the link directions correctly, starting with your JPD link direction, then the code you want to use is the one below. Once you update your site settings, make sure you select “Idea” and “Initiative” for import in the import options (you will find these fields under the “Issue links” section in Custom fields tab.

[jira.customfield_jpd]
name = "Idea"
inward_link = "is implemented by"
issue_type = "Idea"
update_from_issue_key = "customfield_initiative"

[jira.customfield_initiative]
name = "Initiative"
inward_link = "is child of"
issue_type = "Initiative"
update_from_issue_key = "epic_key"

[[jira.issue_hierarchies]]
name = "Idea"
all_member_name = "All Issues by JPD Idea"
levels = [
  {name="Idea",key_column="customfield_jpd",issue_type="Idea"},
  {name="Initiative",key_column="customfield_initiative",issue_type="Initiative"},
  {name="Epic",key_column="epic_key"},
  {name="Parent",key_column="epic_parent_key"},
  {name="Sub-task",key_column="subtask_key"}
]

I am also adding screesnshots how my fields look in Jira starting from JPD Idea perspective, so you can compare if you have the same setup

This is a link from Idea perspective (MPD-10):

These are the links from Initiative’s (ETQ-189) perspective:

This is how Epic (ETQ-190) looks, and under story ETQ-191 I have added a subtask :

When using the code I pasted above (and selecting Initiative and Idea for imports), I get the following hierarchy:

If this doesn’t work for you, please reach out to us directly at support@eazybi.com and share a specific example (with issue keys), so we can investigate further.

Best wishes,

Elita from support@eazybi.com

[alex.xm]

Thanks Elita,

It looks like in your recreation, the relationship between Initiative & Epic is via an issue link. For me, Initiative was added into the actual issue type hierarchy. So it’s the actual parent of an epic. It’s not via an issue link that happens to be named “Parent of”.

This is what my issue types settings looks like:

So how would I handle it for this situation?

Thanks again!

[Elita.Kalane]

Hi Alex,

In that case you should define the hierarchy as below:

# above parent

[jira.customfield_jpd]
name = "Idea"
inward_link = "is implemented by"
issue_type = "Idea"
update_from_issue_key = "jpoh_parent_3"


[[jira.issue_hierarchies]]
name = "Idea"
all_member_name = "All Issues by JPD Idea"
levels = [
  {name="Idea",key_column="customfield_jpd",issue_type="Idea"},
  {name="Initiative",key_column="jpoh_parent_3",issue_type="Initiative"},
  {name="Epic",key_column="epic_key"},
  {name="Parent",key_column="epic_parent_key"},
  {name="Sub-task",key_column="subtask_key"}
]

But I suggest first cleaning all your settings, do a fresh import to wipe out everything you had previously imported. Then add the new settings.
Make sure, you select “Idea” for import and also the Parent link from the import options (Plans custom fields)
I suggest also selecting your JPD project for import as well

Best wishes,

Elita from support@eazybi.com

[alex.xm]

Thanks Elita

This didn’t work for me for JPD Ideas. It’s worth noting that on an Initiative, a JPD Idea appears in it’s own section called “Ideas” and not within the set of Linked Issues. See my screenshot

Then, I tried doing a JQL search for issueLinkType = "is implemented by" and I saw my JPD ideas appear there. I clicked on one and it displayed the JPD Idea with the regular Jira UI. That’s when I noticed that direction of the issuelink is opposite of what I thought. On the JPD Idea, it shows “Linked Issues” and it shows “is implemented by” my initiatives.

So maybe it needs to be something like this:

[jira.customfield_jpd]
name = "Idea"
outward_link = "implements"
issue_type = "Idea"
update_from_issue_key = "jpoh_parent_3"

I tried that but it didn’t seem to work.

[Elita.Kalane]

Hi @alex.xm

I replicated the same scenario on my data:

And in this case, you need to adjust the settings to following. It seems that you had already tried that, but please make sure that you perform full data re-import after you update the settings (Data from Jira)

# above parent

[jira.customfield_jpd]
name = "Idea"
outward_link = "implements"
issue_type = "Idea"
update_from_issue_key = "jpoh_parent_3"


[[jira.issue_hierarchies]]
name = "Idea"
all_member_name = "All Issues by JPD Idea"
levels = [
  {name="Idea",key_column="customfield_jpd",issue_type="Idea"},
  {name="Initiative",key_column="jpoh_parent_3",issue_type="Initiative"},
  {name="Epic",key_column="epic_key"},
  {name="Parent",key_column="epic_parent_key"},
  {name="Sub-task",key_column="subtask_key"}
]

After I updated my settings and full data re-import, I was able to see the issue ETQ-55 in the hierarchy under Ideas

If this still doesn’t work, please reach out to us directly at support@eazybi.com referring to this community post and the site name

Best wishes,

Elita from support@eazybi.com

[alex.xm]

Hey Elita,

I think it’s working! I missed the instructions earlier to do a “Re-import All Data” on the data source and that solved the issue.

Thank you!