Optimising Workflow For Better Granularity And Visibility

[Kaladin Stormblessed]

Challenge: I need to know how many tickets each assignee has worked on and completed during a sprint to better understand individual productivity. My current workflow doesn't allow that. 

Description: The way our current workflow (photo attached below) is set up is that we have multiple statuses (one to-do, a couple of in-progress statuses, and one final done status). And Assignees for each status keep changing. For example, the ticket is worked on by person A, and then with the next status, it's assigned to person B for raising a PR.

therefore, in our current workflow, there is no way of finding out how much of the work each person did. There are time hours logged per person that you can see, but that is not a good enough estimate to judge the completion of a particular ticket or measure of individual productivity. 

Solution so far:  The only thing I can think of to better understand individual productivity is to simplify the workflows to just To do, In progress, and Done. And create separate sub-tasks within the stories for actions such as "Raising PR", "Testing", etc. So this way each assignee starts and finishes an issue, and its not transitioned between people. And I get to know how many tickets are completed per assignee per sprint. Is there a better way to do this? 

[Ivan · Accepted solution]

Hei @Kaladin Stormblessed 

I suggest you to try Jira Reports & Dashboards. For example the Control Chart --> Shows how long an issue stays in each status, indirectly reflecting individual contributions.

You can also try to use Jira Automation to log all assignees who work on a ticket. You can create a custom report showing which assigneees worked on what. 

• If you prefer granular tracking → Your sub-task method is great.
• If you want less manual effort → Use custom fields & automation to log contributions.
• If you want advanced analytics → Use reporting tools/plugins.

[Danut M _StonikByte_ · Accepted solution]

Hi @Kaladin Stormblessed,

I'm afraid that that there is no easy way to make such report by using Jira's out-of-the-box tools...  

Have you also tried looking for plugins on the Atlassian Marketplace that offer such reports or gadgets?

If you consider the idea of using a plugin, our Great Gadgets app offers a Pivot Table & Pivot chart gadget that can be used to easily determine how many tickets every person completed in past sprints. 

Hope this helps. If you need any help with the configuration, feel free to contact us at support@stonikbyte.com.

Danut.

[Ayça Erdem_OBSS_ · Accepted solution]

Hello @Kaladin Stormblessed@Kaladin Stormblessed 

Your challenge is a common one in workflows where multiple assignees contribute to the same issue at different stages. While simplifying your workflow to To Do, In Progress, and Done and using sub-tasks for individual responsibilities is one way to track ownership, it might introduce overhead in ticket creation and management.

A better approach could be leveraging Jira’s built-in reporting capabilities along with automation or marketplace apps that provide more granular insights. Since your goal is to measure how many tickets each assignee has actively worked on and completed within a sprint, here are a few options:

1. Jira Work Log & Filters: If time tracking is enabled, you can create a filter-based Sprint Report to see how many issues each person logged time on. However, as you mentioned, this might not fully reflect ownership.
2. Custom Automation Rules: You could set up Jira Automation to tag an issue with all the users who worked on it at different stages, then generate a report based on those fields.
3. Timepiece - Time in Status for Jira: If you’re looking for a clearer breakdown of individual contributions, Timepiece - Time in Status for Jira, developed by my team at OBSS, can track exactly how long each assignee has worked on an issue across different statuses. The Assignee Time Report provides insights into how much time each user has spent on specific tickets, helping you understand contributions without modifying your workflow. This way, you don’t need to simplify your board or create sub-tasks—Timepiece will automatically provide the breakdown of work done per assignee in a sprint.

Here is example of Assignee Time Report 

If you'd like to explore this solution further, feel free to check out Timepiece on the Atlassian Marketplace or schedule a demo with us for a walkthrough of the app's features.

Hope it helps

Ayça

[Kaladin Stormblessed]

Thanks, how can I create an automation which tags the previous assignee on the ticket?