Introducing Issues Progress: A Comprehensive View of Your Team’s Workload

We are always on the lookout for ways to empower engineering teams with visibility. Keeping in line with this, we are thrilled to introduce our latest feature in the development insights suite: Issues Progress. Let’s take a closer look at what it does and why we think it is beneficial for your team.

Issues Progress view

How It Works

Issues Progress is a dynamic visualization tool that pulls data from Jira, offering a snapshot of where each developer stands with their tasks.

Please note that this feature requires Jira integration. To learn how to connect with Jira, please see this article

With Issues Progress, you can view the workload, or assigned issues/tickets, of your engineers in the form of a stacked bar. You will be able to see the number and status of all assigned tickets, which are denoted by 3 different colors:

  • Purple: To Do
  • Green: In Progress
  • Yellow: Done

To choose the team member(s), navigate to the dropdown menu on top of the dashboard. You can also update the timeframe by navigating to the calendar toolbar on the top right and updating the dates.

Designed to give you full visibility into the development process, Issues Progress also offers a more granular view of your team’s assignments. At the bottom of the chart, you will find the specifics of each developer’s workload, including the number of active/total issues, the number of active epics, and the name of all assigned tickets, in all statuses. 

Note that tickets are categorized and sorted based on their status, and you can also easily filter them using the top bar.

Track progress of active issues

View Work in Progress to Capacity Plan

  • Issues Progress provides a detailed picture of each developer’s workload and the status of their assigned tickets. Managers can get a visual overview of their team’s capacity, allowing for better resource allocation and prioritization.
  • The display and percentage distribution of epics can help engineering managers understand how work is divided among developers, how each developer is contributing to each project, or where their effort is going.
  • The change in issue count between different periods can also help you track developer performance trends or ticket completion rates.

Answering Critical Questions

With the Issue Progress page, engineering managers will be able to answer questions such as:

  • Who is blocked right now, with too many issues?
  • How many tickets does Developer A have at the moment? Will they be able to handle more tickets as needs arise?
  • What’s the current status of the tickets owned by Developer B? Can they lend their expertise to additional epics?
  • Have there been any significant changes in the number of tickets for Developer C over the past month?
  • Who owns this specific epic? If there has been no major progress with this epic, is it because the owner is blocked by too many assigned tickets?

Final Words

Take a look at the Issues Progress page and let us know your thoughts. We’re excited to hear how it makes your Jira workflows more efficient and easy to maintain.