Hi everyone,
I’m currently managing a team where we use Jira as our primary ticketing system. Here’s how our workflow looks:
My request:
I’d like to explore ways to streamline this workflow and reduce manual effort. Specifically:
I’d love to hear your thoughts or recommendations on how to set this up effectively. Any best practices, Jira apps, or dashboard configurations that could help us manage this better would be really valuable.
Thanks in advance!
Thanks,
Hi @Asif Khan
welcome to the community!
I understand the potential cost factor, but I'm not aware of this being available as a native functionality in Jira. Customers typically rely on apps from the Atlassian Marketplace for your use case.
If an app should become an option for you, you may want to have a look at the app that my team and I are working on: JXL for Jira.
JXL is a full-fledged spreadsheet/table view for your work items (issues) that allows viewing, inline-editing, sorting, and filtering by all your work item fields, much like you’d do in e.g. Excel, Google Sheets, Smartsheet, or Airtable. It also comes with a long list of advanced features, including support for (configurable) work item hierarchies, work item grouping by any work item field(s), sum-ups, or conditional formatting.
With these, you can build simple, inline-editable dashboards like e.g. this in just a couple of clicks:
This is really just one of a virtually endless number of possible views and reports; you can also view and group by any other issue fields, configure different sum-up styles, etc. etc. I'd need to understand your use case a bit better to advise on the perfect setup, but I'm sure we could save you and your team a substantial amount of time.
Any questions just let me know,
Best,
Hannes
Thanks for all your response, I will go through it and let you know if I need any other help.
Note: We can utilize the free tool/gadget but management wouldnt allow to use any paid tool. So I will go though all the suggestions with the free tool and get back to you. Once again thanks for all your suggestions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Asif Khan
Welcome to the community !!
If you are open to try out a mktplace solution for this need, I can suggest
The app allows you to view your cross project hierarchy in a tree view. You can also view %complete progress at each parent level. It sums up the time tracking fields, story point or numeric fields at each parent level, along with a timeline view.
You can group the data by assignee and create a clear hierarchy view per assignee and track time spent at each issue level. The app can be added to a dashboard as well.
Disclaimer : I am one of the app team member
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Asif Khan
While Jira dashboards are powerful, they are often limited by the data they can display out of the box. A Marketplace app is usually the most direct solution for the kind of deep-dive reporting you're looking for.
Timepiece- Time in Status for Jira’s ‘'Assignee Duration’' report is great feature to track utilization and workload. It shows you exactly how much time each issue spends assigned to a specific user, giving you a clear report.
You can even create more advanced reports like Assignee Duration per Status to see how much time each team member is spending in specific stages of the workflow (e.g., 'In Progress' vs. 'Waiting for Review').
Crucially, any of these reports can be added to a Jira dashboard as a gadget. This directly addresses your request to create individual dashboards for your team leads, as you can configure each gadget to show the workload and efficiency for a specific team member.
And because Timepiece uses your existing Jira issue history, you can generate these reports for all past issues immediately after installation.
Hope my answer is helpful. Feel free to ask if you have any further questions. You can check Timepiece on the Atlassian Marketplace.
Disclosure: I'm on the team that makes Timepiece - Time in Status for Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Asif Khan ,
If you need time per person and where time is going (working vs waiting) without asking people to log work, this is where a reporting app helps (if you don't mind using a third-party apps).
I’m on the team that builds Time in Status. It reads work items change logs and shows:
Assignee Time – how long each person owned an issue while it was in “working” statuses (a clean proxy for effort/utilization).
Time in Status / Average Time – where work actually spends time (e.g., Waiting for Customer vs In Review).
Pivot view – roll up by Epic → Owning Team → Assignee so leads see per-client, per-team, per-person timing in one table.
Dashboard gadget & charts – surface “stuck items,” reopens, and monthly trends, etc.
You can also synchronize data from the app with Atlassian Analytics and build dashboards there based on time data in the status. In this article, I provide a more detailed explanation of how it works.
I hope it will be useful for you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Asif Khan,
Welcome to the Atlassian Community.
Creating a dashboard for each team member sounds like a good idea. But you can also create a single board, to be used by everyone.
If I understood correctly, all the work is tracked under the Epic ticket created by your customers, under various child tickets.
In this case, I think it would be useful to have on your dashboards a way visualize the epics along with their child issues and status.
Jira offers the Filter Results gadget, which can list the issues from a filter, but you could also try some of the gadgets offered by our Great Gadgets app.
Work Breakdown Structure (WBS) gadget lets you display the issues from a filer/JQL by their hierarchy: Epics > Task, Story > Sub-tasks along with their current status
Pivot Table & Pivot Chart gadget lets you display the Epic along with their tasks stats plus other fields, such as Status, Assignee, Team, etc
This gadget can also display the progress of epics, by number of tasks in each status or status category.
Team Wallboard Gadget - can display the issue from a filter / JQL in a Kanban board style - the columns being given by the status categories: To Do, In Progress and Done. It can group the issues by epics as in this example:
Regarding the efficiency of the people I would recommend the Time in Status gadget offered by the same app - it can display the total or average time in each workflow status or status category, by individual.
This app offers many other gadgets, and it accommodate many needs. Very useful can be Cumulative Flow Diagram gadget or WIP Run Chart gadget.
If you have questions or need any help, feel free to contact support@stonikbyte.com.
Danut.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Asif Khan ,
Welcome to Atlassian community.
Based on my experience, your requirements are common and I think that you can implement using Jira dashboard with standard gadgets.
You should start creating filters, and then using some gadgets inside the dashboards.
For the individual dashboard, I would recommend divide ilthe dashboard in this sections:
It's better to create a unique individual dashboard for all the team, you can use the currentUser filter for it.
For monitoring the service, there are several gadgets you can implement. Usually it is compared #tickets opened, #tickets resolved, #tickets not resolved, with a date filter (last month, last year,...)
After this, if you require advanced reporting, you should go through marketplace.
I hope it helps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.