Jira Epic as an issue type in Issue Filter #38
-
In my implementation of flowviz I can see various issue types including story & custom issue types, but I cannot see jira epics & I cannot find where this is configured in the powerbi scripts. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
Hi there, If you go into Power Query and you check the source, you will see for each table it specifies a 'hierarchylevel' - Jira's documentation explains how "By default, Jira is set up with 3 levels of issue type hierarchy: Epic (level 1), Story (level 0) and Sub-Task (level -1)" You would need to change the source for every table to account for multiple hierarchy levels. So, for example, if you wanted to include Epics, in addition to Stories, you would need to change from this: To: You MUST also ensure you change this for any StartAt functions too :) |
Beta Was this translation helpful? Give feedback.
-
Yup that's correct - I'd also double check the tables don't have any
'Filtered Rows' steps that look at hierarchy level :)
…On Mon, Jun 3, 2024 at 3:20 PM MaximumTrainer ***@***.***> wrote:
Thanks. so to modify flowviz to get epics & stories I need to change the
jql queries to get hierarchyLevel in (0,1) for workitems completed,
inprogress, history/2/5 & WIP 1/2 correct?
—
Reply to this email directly, view it on GitHub
<#38 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHACM2RJH6GG7ET3TC4LZFDZFR3STAVCNFSM6AAAAABIWJLJLWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TMNBZGM4DK>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Thanks. Interestingly when I change this the I'm still getting some hierarchy level 0 data in the datasets so will figure out why. |
Beta Was this translation helpful? Give feedback.
-
It should update all tables yes :) Sent from my iPhoneOn 5 Jun 2024, at 18:39, MaximumTrainer ***@***.***> wrote:
Thanks. Interestingly when I change this the I'm still getting some hierarchy level 0 data in the datasets so will figure out why.
Related to this when the data refresh is triggered does this also update the Jira status table (which looks like its stored serialised data)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
Hi there,
If you go into Power Query and you check the source, you will see for each table it specifies a 'hierarchylevel' -
Jira's documentation explains how "By default, Jira is set up with 3 levels of issue type hierarchy: Epic (level 1), Story (level 0) and Sub-Task (level -1)"
You would need to change the source for every table to account for multiple hierarchy levels.
So, for example, if you wanted to include Epics, in addition to Stories, you would need to change from this:
AND%20hierarchyLevel%20%3D%200%20
To:
AND%20hierarchyLevel%20%21%3D%20-1%20
You MUST also ensure you change this for any StartAt functions too :)