Hello All,
I’m trying to build a dashboard for specific deliverables in eazybi. These deliverables are easily identified by their ticket type of “Deliverable”
I need to display in a Gannt chart each deliverable by epic, BUT, these epics are grouped by a custom field called “Program”. The “Deliverable” ticket type is not populated with the same “Program” as the epic.
I can likely accomplish this by listing out EVERY epic under the Issue dimension, but I’d like to display based on the “Program” custom field.
When I specify “Program” from the Dimensions, I can’t get the Deliverable type issue to display unless it too, has the same “Program” value as the parent epic.
Appreciate any help! Thanks!
Hi @janedoe2
You can inherit the custom field value from the Epic issues to the child issues by setting up a “Epic Deliverable” field in eazyBI: Epic level custom field
Use this “Epic Deliverable” dimension to filter both the Epics and the Deliverable issues.
Let me know if you need assistance setting this up!
Best regards,
Nauris
Thank you for your response. I still think I have the same issue, which is that I can’t filter the Deliverable by the value of the epic Program field. I’m going to have numerous programs, all with numerous Deliverables.
This is a much easier way for me to get a list of ALL Deliverables across ALL Programs, but still won’t let me see only the Deliverables for a certain Program value in the Parent epic.
I have the following under Rows:
Program Field (newly created per instructions)
Issue (all issues by epics)
Issue Type (Deliverable)
The moment I specify the Program I want to include, all the Deliverables go away, as they all have the Program (none).
Any advice?
Hi @janedoe2
Could you please share some more details on how exactly you have the hierarchy set up?
Do I understand correctly that you currently have this setup in Jira?
Epic > Deliverable
The Epic type issues have “Program” field with a value (the Deliverable type issues don’t have this or may have a different value than Epic).
Could you please try using the “Program Field” in the Page filters section and filter the issues by the necessary Program.
You can then have the “Issue” dimension in Rows to show you Epics and also any children of these Epics.
If you filter only by “Issue Type” = “Deliverable”, then the Epics will be filtered out and only the Deliverable type issues will show up.
The moment I specify the Program I want to include, all the Deliverables go away, as they all have the Program (none).
Please note that you need to ignore the regular “Program” dimension and only use the newly created “Program Field” dimension in the report for this to work. You can use the “Issue Program Field” property to check that the Deliverable type issues have inherited these values from the Epics.
Let me know if this works as expected!
Best regards,
Nauris
I double checked what I did, and it turns out I missed out the instruction to add “ update_from_issue_key = “epic_key””.
Now, all Deliverables are returned with the epic (with the specified Program) and can be displayed in a Gannt chart!
Thank you so much.
@nauris.malitis This was so helpful we want to do the same thing for Initiatives. I’d like the same report, but starting at the Initiative Hierarchy. The Initiative will have the custom field (Program), the epics should have them too, but instead of starting at the Epic Hierarchy, we want to start at the Initiative.
Epic
– MIlestone 1
– Milestone 2
We show
Initiative
Hi @janedoe2
Sure thing!
If you are using the Plans hierarchy, you can update the “update_from_issue_key” parameter to point at the initiative level:
update_from_issue_key = "jpoh_parent_X"
Use a parent level number 1,2,3,.. instead of X counting parent levels on top of sub_tasks. 1 for story level (jpoh_parent_1), 2 for epic level (jpoh_parent_2), 3 …;
If, however, you have define a custom Issue hierarchy, you can then reference the Initiative level defined in the hierarchy:
update_from_issue_key = "customfield_initiative"
We’ve described it here in the same page: Epic level custom field
You can also check out this Tips and Tricks post on hierarchies: How to create an additional issue hierarchy
Let me know if you have any additional questions on this!
Best regards,
Nauris