Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Resource reporting via fix version or epic, based on assignee at points in time?

Teresa Chera
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!
September 28, 2018

We would like a way to retrospectively look back and see what resources worked on a given project and in what timeframe based on their assignment to a story/task/etc.  I imagine we should be able to do this by fix version or epic but the challenge is understanding who the assignees were at different points of the ticket lifecycle.  Does anyone know of a report or how to customize one to be able to reflect resources who worked on a ticket throughout the life of the ticket then roll that up at the epic or fix version level?

1 answer

0 votes
Troy Spetz
Contributor
October 1, 2018

We use JIRA 7.12 server version.

 

You could use JQL like the following:

 

1. Resource Working on Epic

project = <Project Name> and "Epic Link" = <Epic JIRA Issue Nbr> and resolution = fixed and status was resolved by <JIRA Username>

 

2. Resource Working on FixVersion

project = <Project Name> and fixversion = <Release> and resolution = fixed and status was resolved by <JIRA Username>

 

Note: The above JQLs are very limited, as you have to identify the specific user you wish to report about (i.e. has resolved an issue within an Epic or Release).

Teresa Chera
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!
October 1, 2018

Thanks for the response.  I somehow need to capture the assignees at points in time so I need to identify the state changes and get the assignees at each point.  That's the part I'm getting a bit tripped up on.

Suggest an answer

Log in or Sign up to answer