You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Could you please help me in creating the report form for my team? We started using Kanban not long ago and do not track time or execution period, but I need to be able to create the following report:
* it should contain the names of team members and the tasks on them and their statuses, like histogram I think.
* Hand-made variant would look like a table:
user name/tasks statuses
to do in progress on hold done
user 1 1 5 0 1
user 2 4 2 1 3
something like that.
There's no report like this in Jira off-the-shelf, but I can get you the table.
Run a search for "issues I want to report on" ( maybe "project = X and resolution is empty"). Save it as a filter with a good name.
Go to a (new) dashboard and add a "two dimensional statistics" gadget. Set the inputs to be
Save that, and you'll get the table you're looking for, all with clickable links.
I created the filter as you said, but now stuck with adding a "two dimensional statistics" gadget. I created the new dashboard, managed to find the gadget but it cannot find my newly created filter.
I think the issue is with the filter as it is not displayed in Manage filters - My or in Manage filters-Favorite as well cannot be searched.
@Мария Харченко our free addon does calculate Kanban metrics where you can find a workload report (work in progress) as well as time in status reports to spot bottlenecks. It should do the job for you.
Another simple solution for you is to use swimlanes by assignee so that your board will look exactly like your table. Please remember that in Kanban you manage the flow of work and while resource capacity is important it is not the primary goal.
Finally, there is a cumulative flow diagram in Jira that is another way to get around it. I find it hard to use, but it is sort of a standard.