JIRA tasks that have transitioned in last 30 days

[John Steenson]

I would like to present activity by showing the number of tasks that have transitioned over the past XX days.

Ideally, this could be captured in a filter that could then be displayed in a gadget on the dashboard in a variety of ways.  Would be good to know what status the task is currently in, and when it transitioned to that state (and where from would be nice, not necessary)

[Jobin Kuruvilla [Adaptavist]]

status changed after -Xd

where X is the number of days. You can change it to hours weeks etc. You can also add FROM, TO, BY clauses and other JQL functions to narrow the result set.

If you need to see the old status, you will have to check the change history, unless you capture it in some custom field.

[Sten Sundelin]

Note that the 'status changed after -Xd' solution (which will indeed give you what you asked for) only captures that the status was changed, not if it was changed multiple times and if so, how it transitioned. You need to look at the history for each ticket, either on the screen or build something using the REST API (or more complex solutions).

Also, if you have a transition that has the same start and end status (in effect going back to itself), it won't be tracked this way. Not sure how to do that (or if that was even part of the original question :o) .

[Jobin Kuruvilla [Adaptavist]]

Interesting comment about the same status transition. Haven't checked that scenario before!

[Sten Sundelin]

As an example, I can see this being used as a rudimentary form of approval process, have a 'loopback' transition "Approve" available to a special 'approvers' group or role of users (setting a somewhat - but not completely - hidden field 'approved by' to currentuser in a post-function) and open the transition out of the status once the 'approved by' has been populated.

If someone edits the field manually, you have the History as proof. Not bulletproof, but good enough for most, I believe.

Other variations than approval would be if a certain group has to decide on a specific field value before the issue is allowed to proceed in the workflow. Maybe Product Managers have to populate a Business Value or Priority.