Power BI Challenge 8 - Jira IT Service Desk Analysis

Challenge 8- Data From Jira IT service Desk Analysis

So here we are for another instalment of the Enterprise DNA challenge.

It’s been an awesome few weeks and we’ve have had some amazing submissions across the board. We are covering some serious ground in terms of scenarios and industries not to mention the sharing of ideas, tips, tricks and approaches.

So here it is all the 8th instalment of the EDNA challenge.

Remember its open to everyone so don’t be afraid to get stuck in.

To learn more about the challenge and how it works be sure to check out the forum below!

If you’re not sure of anything just reach out to me.

Remember: The weekly winner will receive a complimentary membership to the platform that they can share with anyone and the opportunity for your work to be showcased across our channels. There is also a newcomer category with some great prizes on offer so be sure to get involved.


So this week’s challenge is around a system that I’m sure many of us use and have heard of, Jira.

Jira is a major player and a core tool used by many organisations whether it’s to support agile development or manage service desk tickets.

This challenge is covering of two major components that you are likely to need in your armoury as an all-round analyst;

  • Working with data from Jira
  • Building a report around IT tickets

It’s a common ask to design and implement a report that can help manage tickets being received, managing workloads and planning interventions.

Data has been extracted into a flat file and is ready for you to build out in Power BI.

The ask is to produce a report that gives us the below insight into our business.

  • Patterns related to; ticket status, ticket composition, ticket technician

  • Types of issues

  • Timings around different issues (time to resolve etc)

  • Identify areas/issues we could further train users

  • Identify patterns for reoccurring issues so we can identify areas which may need management intervention

                               **UPDATE PLEASE READ**

After some great data profiling from our contestants a few questions were posed to the business to help us produce a report that is beneficial.

1)How to handle records where the create date is after the due date?

The business were surprised at this, and the only business reason behind this is staff creating tickets after the event (Wink, wink, nudge, nudge this is great information. There are likely issues with the business process or data capture. We should highlight these records to the business in the report.)
It could also highlight implementation issues so present these records as such.

2)How to handle records without due date?

In general there should be no tickets without due dates and any that are should be marked as incomplete as there should be no tickets without a time frame.

I hope these questions help you structure your thought process and also in terms of handling the data.

SUBMISSION DUE DATE - Sunday, 25th October 2020 (PST)

Please can you all submit your PBIX files to powerbichallenge@enterprisedna.co

The data set can be downloaded below.

jira cleaned.xlsx (196.4 KB)

Best of luck!

Any issues or questions please reach out.


Enterprise DNA


And we’re off…!!!



unnamed (1)


@haroonali1000 - can you clarify what the “Last Viewed” column represents?



1 Like


I found the following helpful guide to standard JIRA fields:


I think that field typically indicates when the issue was last viewed by a system user, but it looks like it got reset to the same date for every record when the data was bulk exported to Excel.

  • Brian

@BrianJ - thanks. This was helpful.


Would it be possible to clarify my understanding on the Created date column?

I am assuming that this is intended to mean the date an issue was entered in to the system?

That being said, there are a number of Due date entries that are before the Created date?

I am not aware of this kind of system so any pointers on this would be helpful.

One could use the issue above as an identification of potential types of issues or further training as per the brief, but just wanted to be sure this is or is not something specific to the scenario before diving in with both feet!


1 Like

:rofl: :rofl: Hahahahaha!

Is it just me or is it really painful to work with Text Boxes after Sep 2020 update?


Oh, man that’s good to hear – I thought I was just getting really uncoordinated…


Hi All,

I have updated the post above with some more information that should hopefully clarify any questions.

If there is anything further do not hesitate to reach out.


It’s the Smart Narratives preview feature … just disable the option, restart PBI, and the “old” experience is back … I’m only enabling the preview feature when I want to use it.


@Greg Thank you so much :+1:


Is it ok to switch all of the Date/Time columns to just Date, or just keep it they way it is?


Either is good. No preference or penalisation.


1 Like

What does the Watchers column mean and why are there multiple Watcher_ columns.

Hi @YusufGillani,

Watchers column is people interested in the ticket raised.

They would possibly also receive notifications with regards to this particular ticket.

There can be multiple watchers interested in a ticket.



haha that’s a good one. Is that you out in front Brian


I really love the employee names in this dataset. Well done!



This was an odd behaviour - Used Date Only for Created column calls AddColumn but when I do the same for Last Viewed & Resolved, it calls TransformColumn.