There seems to be no way to simply specify a date. What I want is something like
project = XYZ AND status not in (backlog, cancelled) AND date = 2021/04/14 GROUP BY status.
I can only find createdDate or updatedDate but those obviously can't help.
JQL is for finding issues, not reporting on them, it's not SQL.
For your "group by", you need to be looking at the reporting method, not the question of what issues to fetch.
Jira has a very simple gadget that does this, which you can import into Confluence.
Run a search for the issues you want (project = XYZ and status not in (backlog, cancelled) should work fine, but "date =" makes no sense. What date?), then use the saved search in a "filter statistics"gadget that has "status" as the field to group by.
Well, what I actually want is to find a set of issues that are in a given set of statuses (ie. not in the backlog, and not resolved) on a given day. It does seem that such an apparently simple thing is indeed a bit beyond the pale for JQL, which is why people use things like scriptRunner. I would suggest that "date" makes perfect sense, given I could have "updatedDate" or "createdDate" ... and I've seen some examples with the "on" predicate or "endOfDay" function which are close to what I want. And I don't want to use gadgets - due to JIRA's very limited reporting capabilities, I do in fact want to export the data to a spreadsheet :) ... for reporting!
No problem finding "issues in status X", but "date" is still not defined.
Created, updated, commented, goes through a specific transition, and, and, and
JQL has some useful functions around dates, but they can't work with "on a given date", they need to know what date you are looking at.
Hi @phil_brown ,
Please define the "date function". If the problem is that you need to work with different kinds of dates (created, updated, etc.) but you are tired of going to the page edit mode and changing the JQL inside your Jira Issues macro, we can suggest using additional apps from the Marketplace.
Here we filter issues only with the "In Progress" status and created later than 01/Jan/20.
The screenshot was taken in the page view mode, so you don't need to change any JQLs and can filter you issues (create pivots) on the fly.
I get that Atlassian's business model effectively forces you to buy add-ons to cover functionality that the product does not provide OOTB. But any answer that does not meet all 3 of the above criteria does not answer the question. It does seem to be that the answer is "this is not possible OOTB".
As I understand, you want to see the historical changes of your issues. Like, for example, two days ago you had 5 issues to do/0 done, yesterday 3/2, today 2/3.
If to talk about Confluence, the Jira Issues macro and the Jira Chart macro reflect the current state of your issues without any historical memory.
Hello Confluence Community! What if i told you that you could have a healthier life and be 100% meet-less? This month, we're promoting a healthy, balanced work diet with Confluence. We la...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events