Hello - I am trying to get a drill down view of all issues by initiative. I see in the Issue -> Select Member that there is an option for "Issues by Epic". This works great, but it only goes Epic to Story to Sub-Task. Is there a way to see the code for this so that I can create a calculated value that starts at the initiative or even Theme level?
I am looking to build a bar chart for each initiative that shows issues in progress, done, grooming, etc. I can only do this from the Epic down at this point, but need to see all epics under their linked initiatives. I can not figure out how to do this.
Thanks for the help!
eazyBI has an option to build new hierarchies in Issue dimension. You can build new Issue hierarchy over basic levels Parent>Sub-task or Epic>Parent>Sub-task. You would like to pick one and then build some more levels above.
eazyBI requires a separate custom field with Issue key for any level above default levels. In your case, you should create new custom fields for Theme and Initiative. You could create those custom fields with issue link import.
For hierarchy: Theme>Initiative>Epic>Parent>Sub-task, you should define new link custom fields for Initiative and Theme. You could use any JIRA custom field for them, if you do have one. For example, JIRA Portfolio has a Parent link, you can use for one additional level.
Here are several tips how to define link custom fields for issue hierarchy with eazyBI option Issue link import:
- each issue should have only one issue key on any level above (no multiple values)
- import any level issue key for issues one level below
- Issues could be linked with either Inward or Outward links. Please check issue link direction in JIRA Administration section Issue linking. Use correct directions and namings.
- Issue type in link configuration filters linked issues by Issue type
For our example,
You should import one issue key of Initiative for Epic issues
You should import one issue key of Theme for Initiative issues
Please use correct code and sequence for update_from_issue_key parameter for each link custom fields used in hierarchy. This parameter is the key for building hierarchy. For each level update_from_issue_key should address custom field or default field of the next (below) level.
Let's define new link custom fields and hierarchy for our example:
Any Initiative issue has a link to one Theme issue with outward issue link "has Theme". You should see this link in any Initiative issue. This definition describes linked Theme issue:
name = "Theme"
outward_link = "has Theme"
issue_type = "Theme"
update_from_issue_key = "customfield_initiative"
Any Epic issue has a link to one Initiative issue with outward issue link "has Initiative". You should see this link in any Epic issue. This definition describes linked Initiative issue:
name = "Initiative"
outward_link = "has Initiative"
issue_type = "Initiative"
update_from_issue_key = "epic_key"
Please use your issue link names and directions in definitions above.
You do not need to define default levels as custom fields. You can address new levels and default levels in Issue hierarchy:
name = "Theme"
all_member_name = "All Issues by themes"
levels = [
Hello Atlassian Community! Each month, we run a series of Spotlights to highlight Marketplace vendors and apps that our team thinks this Community would find valuable. In last month's Spotlig...
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!
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