I need help creating a JQL query to find all the tickets that were marked as resolved by my user account. I want to track my work progress and see which issues I have successfully closed over time. I tried looking through the documentation but couldn’t find the right field or syntax to use. I remember seeing some discussions about this not being supported in older versions, but I’m hoping there’s a way to do this now. Can anyone share the correct JQL syntax to filter issues based on who resolved them? I’m specifically looking for tickets where I was the person who changed the status to resolved.
Manual JQL works but gets messy for regular reporting or combining with other systems.
I built automated dashboards that pull JIRA resolution data and send weekly Slack summaries. Key is setting up workflows that capture this consistently without running manual queries constantly.
Latenode makes this dead simple. Create automations that run scheduled JQL queries like status changed to "Resolved" by currentUser(), then format however you want. Mine pulls resolved tickets weekly and creates summaries with ticket counts, resolution times, and project breakdowns.
Best part? You can combine with other data - GitHub commits, calendar data - for a complete work picture. Beats remembering to run manual queries.
Set notifications for milestones or track resolution patterns over time. Once automated, you’re done tracking forever.
try using resolved = currentUser() in your JQL. it really helps in seeing tickets you’ve marked as resolved. just check that you have the right permissions! it works for me when tracking my closed issues.
honestly the status changed to "Resolved" by currentUser() syntax mentioned above is your best bet. just tested it on our instance and it pulls exactly what you’re looking for. make sure to check if your team uses “Done” or “Closed” instead of resolved tho - depends on workflow setup.
You’ll want to use resolutiondate with assignee. Most JIRA setups don’t track who actually resolved an issue - just who was assigned when it got resolved. Try assignee = currentUser() AND resolutiondate >= -30d to pull tickets assigned to you that were resolved in the last 30 days. If your workflow’s different, check for a custom field like “Resolver.” You could also try updater = currentUser() AND status changed to Resolved - this shows tickets where you changed the status to resolved, though it might catch other updates too.
The history approach works, but here’s another angle. Some JIRA setups only let certain users resolve tickets. If that’s your case, try assignee = currentUser() AND resolution is not EMPTY with date ranges - it’s more accurate. This assumes you were assigned when you resolved it, which most teams do anyway. You can also check your profile’s activity tab - it sometimes shows resolution actions when JQL gets weird. I’ve seen custom workflows track resolver info differently, so ask your JIRA admin what fields they’ve configured for your setup.
JIRA doesn’t have a built-in “resolver” field, but I’ve found a workaround that works well. Use status changed to "Resolved" by currentUser() - this tracks status transitions you actually made. It’s way more accurate than checking assignees since you might resolve someone else’s ticket or they might resolve yours. If your setup uses “Closed” instead of “Resolved,” just swap it out. Also worth checking if your org set up any custom resolver fields in the configurations. I’ve used this history-based method across different JIRA versions and it’s been solid.