Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • How to report on the assignee of a Jira story while it was in "In Testing" status, using history

How to report on the assignee of a Jira story while it was in "In Testing" status, using history

Svetlana Mandrosova
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 14, 2026

I need to be able to pull the report to see who was assigned to a story when a story was In Testing status. The goal: I need to know, who executed the Testing. I cannot rely on the Assignee field, as it gives me the name of the current person assignee to a story. In many cases it would be the person who moved the story from AP status to RTR or Closed. That is why I need a way to query the history

1 answer

1 vote
Cristian Quiroz
Contributor
August 14, 2026

Hi @Svetlana Mandrosova !

Unfortunately, there's no native way in JQL to query "who was the assignee WHEN the status was X", status WAS and assignee WAS exist independently but you can't combine them temporally.

Workaround for the future (Automation)

You can capture the tester automatically going forward with a simple rule:

  • Trigger: Issue transitioned → status = "In Testing"
  • Action: Edit issue → set a custom field (e.g., "Tester") = {{assignee.displayName}}

This will store the person who was assigned at the moment the issue entered "In Testing". From there, you can filter/report on that field normally.

Limitation

This only works prospectively (for new transitions going forward). For historical data, Automation can't help, even if you call the REST API via "Send web request" to get the changelog, the JSON response requires correlating timestamps between status changes and assignee changes, and Automation smart values don't support that kind of conditional logic over nested arrays.

For historical data: ScriptRunner

If you have ScriptRunner installed, this becomes much easier. You can write a Groovy script that:

  1. Iterates through the issue's changelog
  2. Finds the entry where status changed to "In Testing"
  3. Gets the timestamp of that transition
  4. Finds who was the assignee at that point in time
  5. Optionally populates a custom field with that value (for bulk backfill)

This gives you full control to backfill the historical data and also run it as a scheduled job or listener going forward.

Hope that helps! 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events