nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to get a list of tickets an user worked on ?

Joao Borges_ch4uwn

Hi there,

I am trying to get a list of tickets an assignee worked on for the month. The problem is that the ASSIGNEE field changes once ticket moves from QA to Validation. Ticket gets assigned back to Reporter, and reporter is responsible to validate and close it.

If we run a jql query - assignee was ("user1"). Query will give me a list of tickets which user1 was assigned to it at one point, but what if user1 did not complete the ticket and assigned to user2.

Do I need to change the workflow to not change assignee field ? Do I need to create a custom field for it ? Or is there a way to get a query based on who completed the ticket, even if ticket was assigned to many users.

Thanks,

Accepted answers

All comments

Mark Segall

Hi @Joao Borges - If you need to have individual team member reporting, you'd probably be better served transitioning to use of Sub-Tasks. The story stays assigned to the product owner and sub-tasks are created for the other team members.

Trudy P Claspill

Hello @Joao Borges

but what if user1 did not complete the ticket and assigned to user2.

Looking at the information available in a ticket, including the history of activity for the ticket, how would you know that user1 completed the ticket? If multiple users have been assigned to the ticket, how do you determine which one gets credit for "completing" the ticket?

Yuliia_Borivets__SaaSJet_

Hi @Joao Borges

If I understand everything correctly, you need a report for a specific assignee and issues that person worked on + to see who else worked on the same tickets. The case you described can be solved with Issue History for Jira app from my team.

For your request, you can:

Filter issues by the assignee.
Select the specific date range (a month or any you need)
Include the assignee column in the table, so that you will see all assignee changes in one column.

assignee history jira.jpg

Also, you can use the 'Updated by' option to get all tasks a person worked on. You can try the app free for 30 days to create your custom report and find out if it works for your case.

RVS_Support

Hi @Joao Borges

We have built an app for this use case.

If you would be interested in the same, you can try out

Issue History Reports

You can view the complete change log for your filtered issues along with assignee changes as different columns.

Do Try it out.

Disclaimer : I am part of the team which developed this app

Issue History.PNG

Thanks

Joao Borges_ch4uwn

@Mark Segall yes, but what if the subtask gets assigned to a different

Joao Borges_ch4uwn

then we run into the same issue

Mark Segall

I find that when using sub-tasks in this manner, it's more of an edge case that it gets reassigned. If this would occur frequently enough to cause a dramatic impact to your reporting, then you have two options:

Establish policy that if you cannot complete a sub-task to simply close it and create a new sub-task for the person who will take over. This way you always maintain one assignee per issue.
Enforce use of worklogs - This would avoid the need for using sub-tasks, but dev teams typically aren't fans of having to track time.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

atl-gruland