JQL is for finding issues, not working with the results. All you really get from a JQL search is a list of issues.
You then push that through some reporting (the issue navigator, reports, gadgets etc), and the reporting is what determines the output.
So, you'd need to do that in the report, not JQL. So the next question is "where do you want to see this data?"
(Although, there's a 95% chance that the answer is going to be "you need a scripted field", I should ask just in case it's not)
Hi, Nic, Thank you for your reply. I know that JQL queries return issues as results. I'd like to use day number in query to get a list of issues which were for instance created on a certain day, regardless of month or year. Or updated, or something. I'm not sure if I managed to explain but I do hope it makes sense.
Found this post when having the same issue. The root problem of comparison between dueDate and resolutionDate/resolved is that dueDate is a date and resolutionDate is a dateTime. It's a bit hackish, but we overcame it with the following JQL (ScriptRunner required).
duedate is not EMPTY AND (issueFunction in dateCompare("assignee in membersOf('myTeam')", "resolved < dueDate + 1439m"))
The downside of this approach is that you lose track of issues that were closed in the 23:59:00 minute, and there is no s <seconds> datepart available in JQL.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs