Issue Changes
ISSUE CHANGES | |||||||||
---|---|---|---|---|---|---|---|---|---|
Column | ISSUEID | ID | USERNAME | FIELD | CREATED | FROMVALUE | TOVALUE | FROMSTRING | TOSTRING |
Type | BIGINT | BIGINT | VARCHAR | VARCHAR | TIMESTAMP | VARCHAR | VARCHAR | VARCHAR | VARCHAR |
Indexed | x | x | x |
It allows to access to the issue changes history for the issue tracked by JIRA. You have to know the name used by JIRA to track the attribute (FIELD column value). Unfortunately, those field names are documented nowhere as they belong to the private JIRA Java API. Â I.e: for the issue status attribute, the field name is: 'status'. You have to figure out the name to use it in the query.
To get the time spent in each workflow status transition, the ISSUESTATUSTRANSTIONS should be instead since it is specially created for that.
Example: How to get re-assigned issues in DEMO project?
select c.issueid, c.username, c.created, usernamekey(c.fromValue) as "From user", usernamekey(c.toValue) as "To user" from jql join issuechanges c on c.issueid = jql.issueid where jql.query = 'project = DEMO ' and c.field = 'assignee'
ISSUEID  | USERNAME  | CREATED  | From user  | To user  |
---|---|---|---|---|
10100 | admin | 2019-10-03 09:44:55.833 | null | admin |
10100 | admin | 2019-10-05 13:38:06.878 | admin | p |
Note that the usernameKey function is used to get the username instead of the user key.