Creating Dashboard to track hours spent on sprint tickets.

[Sanobar Basha]

Hello, I am trying to create a dashboard to see a velocity of the following items:
I haven't been very successful in pulling all the following info on dashboard to view with my team, can anyone help me with it? 

• Time spent on tickets for design.
• How many days team went over in design phase per ticket. 
• Time spent on tickets during implementation.
• How many days or hours team went over original estimate during implementation.
• ## of Bugs identified in QA env.
•  ## of bugs found in UAT env. 
• Total time spent on tickets. 
• ## of times ticket scope changed. 

Problem statement: 

Currently, teams at our company are spending too much time in ticket design like weeks before they start implementation. when they do start implementation, no matter how generous the estimates are they still go over original estimate. I want to be able to pull all the information on a dashboard so i can talk to the team through it on RETRO and come up with a game plan to do better as a team. 

I am unable to share screenshots or i would have shared a pic of fields I'm talking about. 

[Adaeze_Jude_HEROCODERS]

Hi @Sanobar Basha ,

You may want to explore a third-party App like Clockwork Free or PRO to manage your team's time spent.

For the data you would like to pull, below are ways to achieve this using native JIra JQL and Clockwork Timesheets:

• Time spent on tickets for design/ Time spent on tickets during implementation.

Using different Issue Types for design or implementation Tickets. If you already have a setup and would not like to change this, users can log design time by adding a worklog with a Worklog attribute to identify the time spent here.

You can pull this report on the timesheet by filtering for Time spent on a particular issue type or a worklog attribute as below:

• How many days team went over in design phase per ticket. 

Utilizing Original estimates, you can view a comparison report on the Timesheet, as below:

• How many days or hours team went over original estimate during implementation.

Still using the Original estimate vs. the Remaining estimate comparison on the Timesheet.

• ## of Bugs identified in QA env/ ## of bugs found in UAT env. 

This can be retrieved using a JQL query

• Total time spent on tickets. 

The time sheets provide the total time logged on tickets as below:

 

• ## of times ticket scope changed. 

Using automation and a custom field to save the count, you can get the number of times the ticket scope changed.

You can also view a summary of this report using the Clockwork gadget on the PRO version, filtering by the period, issue type and project; you can see the summary of time spent on the different issue types:

Let me know if you would like to explore these options; please reach out here.