The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Building FCR filters - Incidents that have not been reassigned

Mitchell Naylor
August 16, 2018

I need to build a filter that shows Incidents that have been completed but have not been moved to another team for action.

Example:

Ticket logged for a password reset that was completed on the call with the customer, the ticket will progress from new to in progress to complete all with the same agent in the same group.

Ive read the other suggested ways to track FCR with custom fields and so on, but the data is already in JIRA SD so there shouldn't be a need to customise the form, just filter on a set of conditions.

Thanks.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Michael Wohlgemuth
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 17, 2018

This is tricky (for me at least).

I would try something along the lines of:

status changed from "Status1" to "Status2" AND (assignee was youruser AND assignee = youruser) 
Mitchell Naylor
August 19, 2018

Perfect!

This is the working example:

project = NAME AND issuetype = Incident AND (assignee was currentUser() AND assignee = currentUser() ) AND status in (Completed,Closed)

Mitchell Naylor
August 19, 2018

Next challenge is, can you filter on any ticket that has not been moved between assignee's so you can be sure this ticket was logged and closed under the same user.

The filter above works to show tickets assigned and closed under the same person, but it doesn't care if it was assigned to 20 people, just that it was closed under the same person who it was first with.

Michael Wohlgemuth
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 20, 2018

Check if this works (add it to your stuff, exchange date or use date functions):

AND NOT assignee changed before "2018-08-20"

Note: I think this might even make the first suggestion i had obsolete, but im unsure. Try running it with just this one and see if it works.