Subscribe to receive blog updates

Search form



Oct 28, 2015

Getting More Out of JIRA

How to leverage your JIRA data into valuable business insights.

So... Whats JIRA?

Jira is a product management tool by Atlassian that allows you to easily track bugs, issues, and manage progress across your entire team. Management can oversee what's happening in their company on the backend and track employee accomplishments. 
With Jira, the responsibilities of each employee never gets vague. Each issue can be paired with sub-tasks that require completion ahead of the rest of the task. Apply labels and projects to subdivide your data into valuable categories. 
These productivity features can quickly increase the effectiveness of any team and provide a more stable understanding of the necessity and time-sensitivity of tasks.

Sounds Neat, What Kind of Data is Available in JIRA?

Once you have incorporated Jira into your company, you will immediately start to see the benefits; but, the advantages don’t have to stop inside the tool. Underlying each new task, each completion, each label, and each assignee is a plethora of data that is ready to be utilized to understand your company more thoroughly.
Know which of your employees has the heaviest workload, how much time tasks take depending on the label, and if employees are actually completing high-priority tasks, promptly.

How Do I to Monitor Task Completion with JIRA Data?

So let’s take a look. Here are some example subjects you can monitor with your JIRA data and what kind of insights they might provide.

Average Completion Time by Label and Assignee

Many companies separate their support teams by subjects, some developers will use their expertise to only track down certain bug types and not deal with others. A higher average completion time by Label might imply the need for more developers of that specialty.
Alternatively, a higher average completion time of an individual could be the result of many things. This employee might be slower in general, or perhaps they are just overzealous in claiming tickets. In any case, you will be able to see the trend and take steps to find out the cause. 

Task Count by Employee

Combining this chart with the one above might bring more light into issues. If an employee has longer than average task-completion times, it might be because he/she is overworked. It could signal the need for additional support staff or a more sophisticated distribution of tasks between the team. 

Task Creation by Day of Week, Month of Year, ect.

This one might be a little weird at first, why would task creation matter by Month of Year? Many business experience peaks and troughs in their use, even apps and Saas. If you can uncover these types of trends you can hire part time staff in advance to facilitate the increased workload. 

Task Creation by Time

There are many ways to measure the success of a new product launch or update. The number of bugs created is certainly one of them! Annotate the launch of your update and then measure the increase of bugs created above the average. Maybe somebody said something was ready... when it wasn’t! 


To connect Slemma to JIRA, select the Create New button, select the dashboard type and then you will be taken to the datasets page. From there scroll down and select the JIRA logo. Afterwards, you will be presented with a dialogue for your username and password to your JIRA account. Depending on how the account administrator set up the account, you may not have access to all of the data. Once this is taken care of, you will be able to create updating reports about many, many subjects. The above list is far from complete! 
Let us know if you have any questions at, we would love to know how you were able to leverage your JIRA data! 

No comments :

Post a Comment

Share a post