Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I am trying to visualize Jira issues count over time by status.
Jira issues can be in three status category:
1. new / to do
2. In Progress
3. Done
I want to visualize it in such a way that it shows distinct count of jira issues over time like in line chart over time.
Demo Table
Issue key | Issue id | Issue Type | Project name | Priority | Created | Status Category | Status Category change Date |
HD-1014 | 13340 | Task | helpdesk | Medium | 9/14/2020 12:29 | new | 9/14/20 12:29 PM |
HD-1015 | 13320 | Task | helpdesk | Medium | 8/27/20 3:33 PM | new | 8/7/20 3:33 PM |
HD-1014 | 13340 | Task | helpdesk | Medium | 9/14/20 12:29 PM | in progress | 9/19/2020 12:29 |
HD-1015 | 13320 | Task | helpdesk | Medium | 8/27/20 3:33 PM | in progress | 8/20/20 3:33 PM |
HD-1014 | 13340 | Task | helpdesk | Medium | 9/14/2020 12:29 | done | 9/24/2020 12:29 |
HD-1015 | 13320 | Task | helpdesk | Medium | 8/27/20 3:33 PM | done | 8/27/20 3:33 PM |
SMS-1014 | 2340 | EPIC | Sec Comm | high | 9/14/2020 12:29 | new | 9/14/2020 12:29 |
SMS-1015 | 2320 | EPIC | Sec Comm | high | 8/27/20 3:33 PM | new | 8/7/20 3:33 PM |
SMS-1014 | 2340 | EPIC | Sec Comm | high | 9/14/2020 12:29 | in progress | 9/19/2020 12:29 |
SMS-1015 | 2320 | EPIC | Sec Comm | high | 8/27/20 3:33 PM | in progress | 8/20/20 3:33 PM |
SMS-1014 | 2340 | EPIC | Sec Comm | high | 9/14/2020 12:29 | done | 9/24/2020 12:29 |
SMS-1015 | 2320 | EPIC | Sec Comm | high | 8/27/20 3:33 PM | done | 8/27/20 3:33 PM |
SMS-1024 | 9140 | EPIC | Sec Comm | high | 10/14/20 12:09 PM | new | 10/14/20 12:29 PM |
SMS-1025 | 9120 | EPIC | Sec Comm | high | 9/27/20 3:33 PM | new | 9/7/20 3:33 PM |
SMS-1024 | 9140 | EPIC | Sec Comm | high | 10/14/2020 12:29 | in progress | 10/19/2020 12:29 |
SMS-1025 | 9120 | EPIC | Sec Comm | high | 9/27/20 3:33 PM | in progress | 9/20/20 3:33 PM |
SMS-1024 | 9140 | EPIC | Sec Comm | high | 10/14/2020 12:29 | done | 10/24/2020 12:29 |
SMS-1025 | 9120 | EPIC | Sec Comm | high | 9/27/20 3:33 PM | done | 9/27/20 3:33 PM |
HD-1014 | 13340 | Task | helpdesk | Medium | 9/14/2020 12:29 | in progress | 10/19/2020 12:29 |
HD-1015 | 13320 | Task | helpdesk | Medium | 8/27/20 3:33 PM | in progress | 9/20/20 3:33 PM |
HD-1014 | 13340 | Task | helpdesk | Medium | 9/14/2020 12:29 | done | 10/24/2020 12:29 |
HD-1015 | 13320 | Task | helpdesk | Medium | 8/27/20 3:33 PM | done | 9/27/20 3:33 PM |
Sounds good. What have you tried and where are you stuck?
I have created a calculated column which contains the date at which the issue was moved to next status and for the current status it contains now() . I was trying to create a measure which will return distinct issues where selectedvalue of x axis i.e., a date is between those two columns which contains the date at which the issue entered a status category and at which it left. I'm not sure if it's a correct approach and measure was giving a straight horizontal line.
I was trying to create a measure which will return distinct issues
Measures can only return a scalar value.
ok, that is possible with a disconnected dates table.
By the way, here's a graphical representation of your sample data. Not very useful
There are also typos where the timestamps for new status entries don't match.