How can I see all tasks which was Unassigned from the team?

[Mila Terzi]

How can I see all tasks which were was Unassigned from the team?

Due to the current process, when my team finishes working with a task, they make status "Unassigned" , and move to a different column, where developers from another team can work with it. I need to get the results of all my team did for the few Q3/Q4 but I can't see in filters, how to see the tasks because the current status is Unassigned. Is it possible to make the filter for these cases? When the first assignee was a specific Developer and after that the task started to be in status  "Unassigned"?

[Max Foerster - K15t]

Hey @Mila Terzi ,

Welcome to the community! 😁

The Assignee field as a system field supports different operators but also the operators WAS, WAS NOT, WAS IN etc. (find more in the docs here) for historic values. In this documentation about What is advanced searching in Jira Cloud? you can all the bits and pieces about JQL.

So I'd say querying for Assignee WAS IN and then using auto-complete to fill the parentheses () with your team members could be one solution. If you gathered your team members in a user group, you could even use WAS IN membersOf("group name") instead.

Best, Max

[Bill Sheboy]

Hi @Mila Terzi -- Welcome to the Atlassian Community!

Adding to what Max suggests...if you specifically need to find those issues changed to unassigned as part of your current process, you may add the following to your query:

assignee CHANGED TO EMPTY

Kind regards,
Bill

[Mila Terzi]

Hi guys, Thank you for your answers.
I used the request: 

project =«name and assignee was «name» and then I filtered results, so it's working fine! 

=) 

[Jack Brickey]

Hi Mila, welcome to the Community.

Based on what you have posted it seems like what you might consider creating a custom field “developer” and copy the original assignee into that field. This will allow you to have traceability to the original assignee when you move to unassigned. With this said, I might offer that you consider changing your process and allowing the original issue to be closed and simply linking a new ticket for the additional effort. Or even a task with subtasks.