How to capture the date the ticket was assigned to an individual using JQL?

[Preston]

Hi Everyone,

As the title suggest I am currently trying to pull all issues for a certain project. For each issue I want the assignee, and the date the issue was assigned to that person. At the moment assigned-date is not a custom field and is stored in the changelog. Is there a way to capture these fields in JQL for each issue for many assignees across a year of time? 

Long term goal is to use the REST API to get this data but want to get a test stub first. 

Thanks in advance. 

[Sachin · Accepted solution]

Hello @Preston , the history tab is the only way to view the 'changed the Assignee Date' of an issue. And I think it is not something you can get this from a JQL. Like you mentioned REST Api is another best way to capture this data.

Get change logs 

GET /rest/api/3/issue/{issueIdOrKey}/changelog

Returns a paginated list of all changelogs for an issue sorted by date, starting from the oldest.

Here is JQL which would get you issues that have a value that had changed for the specified field (Assignee). Changed operator has the following optional predicates: AFTER "date" BEFORE "date"BY "username"DURING ("date1","date2")ON "date"FROM "oldvalue"TO "newvalue"

assignee is not EMPTY AND assignee changed

See Advanced Search Reference JQL Operators 

[Preston]

Hi @Sachin ,  really appreciate your help with this. It seems like there really isn't a clean and easy way to get the date that an issue was assigned to someone. Even with the rest API I wonder how much server time it would required to go into the changelog for every ticket in the project...

And it looks like that GET request you tagged (thanks for that) is for v3 for Jira, and not for v2, which might be a problem for me as we are using v2. (I'm using rest/api/2/)

[Sachin]

Hello @Preston , here is the url for v2 - https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issues/#api-rest-api-2-issue-issueidorkey-changelog-get

I agree that it is not a clean way to get that info from making rest calls and it would definitely slow down your instance performance if you are making huge rest calls on regular intervals, so it is always better to make those calls outside business hours. However, I would open a support ticket with Atlassian to get any alternative solutions for your usecase and also open a feature request here https://jira.atlassian.com/browse 

It would been nice if there was a gadget of some kind which will give us the history of an issue.