Retrieve only users that have created or edited an issue

Ashton Treadway August 5, 2013

We're looking at merging two JIRA instances, and we're using a custom authenticator on one of the instances that means we can't do a straightforward query for user logins (the way we're doing things means the JIRA DB is not storing user instances).

However, we can see user activity.

What's the best way (mySQL) to retrieve only users that have created or edited an issue, returning the username, issue, and timestamp of last creation (or last edit) in something like M/D/Y TT format?

2 answers

1 accepted

1 vote
Answer accepted
Timothy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 5, 2013

If you are looking for the create, then you are looking for the reporter column in the jiraissues table. Though, a reporter can be edited which brings us to the edit action.

You will find the change history in the changegroup and one changegroup has many changeitems.

0 votes
Boris Berenberg
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 5, 2013

Here you go for created:

WITH MAXRESULT AS (SELECT reporter, max(date(created)) as maxdate from jiraissue group by reporter)

SELECT distinct(ji.reporter), ji.pkey, Maxresult.maxdate from jiraissue ji
RIGHT JOIN MAXRESULT ON (maxresult.reporter = ji.reporter)
WHERE maxresult.maxdate = date(ji.created)

Here you go for updated:

WITH MAXRESULT AS (SELECT reporter, max(date(updated)) as maxdate from jiraissue group by reporter)

SELECT distinct(ji.reporter), ji.pkey, Maxresult.maxdate from jiraissue ji
RIGHT JOIN MAXRESULT ON (maxresult.reporter = ji.reporter)
WHERE maxresult.maxdate = date(ji.created)

*These are for PSQL not MySQL. You may need to tweak them for MySQL.

Note: What Timothy mentions above is 100% correct. This ignores the changeitem table, and it also falls prey to the field value being edited.

Suggest an answer

Log in or Sign up to answer