Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
Hi All,
I hope someone can help here, I have 2 tables called Epic and Tasks pulled from JIRA.
Tasks contains the EPIC_PARENT_LINK, which is where you can match up the data, I have created a hierarchy in Tasks using EPIC_PARENT_LINK as the first, then ISSUE_KEY to collect the Task ID.
This provides the following
As you can see, i have chosen the values to be Status and Summary, the trouble is they have propogated up from the Task and I do not want that information on the Epic, anyone have an idea on how to stop that?
Thanks,
Jeff
Solved! Go to Solution.
@Anonymous Might help although I do not think I have included MM3TR&R yet which is kind of what you are looking for. Try something like below. Basically at the "group" level (first hierarchy level) you are going to have multiple Tasks. So, if you have only a single Task, then you are at the second level of the hierarchy, otherwise, you are at the top level of the hierarchy. This uses HASONEVALUE instead of ISINSCOPE but same concept.
Measure =
IF(
HASONEVALUE('Tasks'[ISSUE_KEY]),
MAX('Tasks'[SUMMARY]),
MAX('Epics'[SUMMARY])
)
PARENT_ISSUE_KEY | ISSUE_KEY | SUMMARY | ISSUE_STATUS | done |
CAPLO-1 | CAPLO-16 | This is just text so | New | 0 |
CAPLO-1 | CAPLO-17 | Another text field | In Progress | 0 |
CAPLO-1 | CAPLO-18 | yet another text | Done | 1 |
The above is from the Tasks table
The below is from Epics
PARENT_ISSUE_KEY | ISSUE_KEY | Summary | Status | Done |
RMPP-1 | CAPLO-1 | different text based on epic | New | 0 |
RMPP-2 | CAPLO-2 | text based on epic | In progress | 0 |
RMPP-2 | CAPLO-3 | text based on epic | done | 1 |
So, as you can see 2 different table containing different information, but with the PARENT_ISSUE_KEY being the link between Tasks and Epics
What I would like to see is:
PARENT_ISSUE_KEY | ISSUE_KEY | Summary | Status |
CAPLO-1 | Epic summary | epic status | |
CAPLO-16 | Task summary | task status | |
CAPLO-17 | Task Summary | task status |
As you can see from the pictures i shared earlier, the + sign opens the information about the tasks.
@Anonymous So, use ISINSCOPE in your measure to determine where you are in the hierarchy and then return either the Epics status or the Task status as appropriate. I assume the tables are related on ISSUE_KEY in Epics to PARENT_ISSUE_KEY in Tasks. Use the ISSUE_KEY from Epics in your table as the top of the hierarchy and the ISSUE_KEY from Tasks as the second level. ISINSCOPE('Tasks'[ISSUE_KEY) should return true for task lines and false for Epics lines.
@Greg_Deckler thanks for the reply, way beyond my level of understanding at the moment, as I have only been using powerBI since middle of January.
Would your tool MHGDQM help me here or would it be like throwing myself into a tank of piranha?
@Anonymous Might help although I do not think I have included MM3TR&R yet which is kind of what you are looking for. Try something like below. Basically at the "group" level (first hierarchy level) you are going to have multiple Tasks. So, if you have only a single Task, then you are at the second level of the hierarchy, otherwise, you are at the top level of the hierarchy. This uses HASONEVALUE instead of ISINSCOPE but same concept.
Measure =
IF(
HASONEVALUE('Tasks'[ISSUE_KEY]),
MAX('Tasks'[SUMMARY]),
MAX('Epics'[SUMMARY])
)
@Anonymous , seem like you have used them in values. You should use them in row.
or create a measure using isinscope and only display at the correct level
https://www.kasperonbi.com/use-isinscope-to-get-the-right-hierarchy-level-in-dax/
Trouble is, if i use them in row it becomes like this
which isn't what I want, i also have the same problem with status, it also propogates upwards.
@Anonymous Sorry, having trouble following, can you post sample data as text and expected output?
Not really enough information to go on, please first check if your issue is a common issue listed here: https://community.powerbi.com/t5/Community-Blog/Before-You-Post-Read-This/ba-p/1116882
Also, please see this post regarding How to Get Your Question Answered Quickly: https://community.powerbi.com/t5/Community-Blog/How-to-Get-Your-Question-Answered-Quickly/ba-p/38490
The most important parts are:
1. Sample data as text, use the table tool in the editing bar
2. Expected output from sample data
3. Explanation in words of how to get from 1. to 2.
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
94 | |
83 | |
82 | |
71 | |
49 |
User | Count |
---|---|
143 | |
129 | |
108 | |
63 | |
55 |