Hi,
I need a JQL search in JIRA which finds issues created during nighttime. Can someone tell me if it is possible?
something like "created after 1:00AM and created before 7:00AM and created after 1.1.2015 and created before 31.12.2015".
BR,
Andris.
As far as I know you can search for issues created in a specified time interval for a specific date, but you can't search for issues by time for a date range.
For example to find the issues created between 1AM and 7AM today you can use the query below:
created >=startOfDay(1h) AND created <= startOfDay(7h)
If you want to search for the same in a date range - you may try to create a custom post-function. I'm not aware of an add-on providing such functionality but you may try searching the marketplace for such an add-on.
I was able to achieve this. Here's how I did it.
For this example, assume you want to split tickets into those submitted between 9am and 5pm aka "business hours" and tickets submitted before 9am or after 5pm aka "non-business hours" tickets so you can measure how many tickets come during each time period on an ongoing basis.
NOTE: This solution will only work for future-looking tickets
If you wanted to apply this to historic data, I'd suggest downloading all of the data you care about, then using excel to split it into the right buckets, and then using the bulk update function to update the labels to match the above.
Of course if you wanted to be even more specific about this, you could create a label for each hour of the day, and then be able to modify the definition of the groups more easily (for example, if you wanted to move business hours to be 8am - 4pm, it would be more difficult with the solution proposed above)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunatelly - no, however I was able to avoid it by using Calendars of Jira Service Desk, just can't afford SLA reindex, since that will break data.
It's also possible to find such issues with excel from CSV export or from SQL database itself...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Andris Grinbergs,
Hope you are doing well.
Were you able to achieve that output ?
Suri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.