You can search for all issues you have transitioned in the last to days with this JQL
status changed BY username AFTER -2d
But this does not work for "updated" or "updateDate". For the current versions of JIRA the history operators can only be used with the Assignee, Fix Version, Priority, Reporter, Resolution and Status fields.
The closest I could come to the requirement is:
1) Status changed by user within last x days
2) Created by user within last x days
3) Assignee changed by user within last x days
(status changed BY currentuser() after -8d) or (created >= -8d and creator = currentuser() ) or (assignee changed by currentuser() after -8d)
Still not covered: Commented without change of status or assignee
Note: At least the "assignee changed" part of the query seems to work weird with the dates, you might want to increase the required number of days by 1 to really catch all issues
There is a JIRA suggestion for this feature: https://jira.atlassian.com/browse/JRA-15235 you may vote for it, but it is an old request.
As for now, and what I see, the nearest you can get to this is using the JQL Mykola Novik posted.
In analogy to the Activity Stream Gadget, it queries the item-history, but you've got more options for filtering, grouping, etc.
The result looks like:
select ji.issuekey, ji.issuetype, cg.author, cg.created changedate, ci.field, ci.oldvalue, ci.oldstring, ci.newvalue, ci.newstring from changegroup cg join changeitem ci on (cg.id = ci.GROUPID) join (select ji.id, p.pkey||'-'||ji.issuenum issuekey, ji.summary, it.pname issuetype, ji.created from jiraissue ji join project p on (ji.project = p.id) join issuetype it on (ji.issuetype = it.id) ) ji on (cg.issueid = ji.id) ------------------------------ where author = 'your.user.name' -- modify user and cg.created > to_date('08.08.2016','dd.mm.yyyy') -- modify date and cg.created < to_date('10.08.2016','dd.mm.yyyy') and issuetype in ('Bug','Story','Epic') -- modify issuetype ------------------------------ order by cg.created
I don't think you can do this directly, other than by reading your activity stream in your profile.
Chaithra's answers are close, but the problem is that Jira searches by issue, not by person, so "all changes made by X" queries are rather hard to construct.
I think this needs some JQL coding...
Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot