Wow I didn't realize this has been a known problem for so long? I get their is complicated verbage we can use as a work around, but wouldn't just adding Business day functions with selecting what days are your Business days, would be a lot easier to manage and not have to hear us complain for so many years. 

Currently this bug is keeping me from continuing to automate my companies systems. We are drowning in work so the more ability I have to make us more efficient the better. 

Just a short comment that we are still very much looking forward to this "feature"...

10 years since my last comment....and still nothing has changed. I recognize working with dates can get complicated but I really feel like this shouldn't be that hard to do.

Literally all I want is a quick filter of "resolved >= lastBusinessDay()", without having to chain together dozens of queries and still have an unreliable result. We already configure business days in Jira, so why can't this be used to generate "what day was the last business day?", and filter on that? 

We currently have several automations in place that look at relative time periods, but it's quite often that they fall on a weekend. This is not only disturbing our workers on a weekend (which is bad and we'd like to avoid asap) but also not actionable, because people don't work on weekends. Hope you'll get this over the line soon

We are waiting for this since 2010. It would be very helpful indeed but is quite obvious that Atlassian has no interest in doing this.

It would be very helpful to get this feature. 

I am trying to create a rule that triggers when an issue has been "In Review" for more than 5 business days. However I cannot do this because this issue has not been implemented yet!!!

This would be more than helpful. I have not been waiting for 12 years^ but t think I want to even wait 6 weeks for this item it would be so useful. I need it!!

It's been 12 years. Can we please get something like this implemented? It would help a lot with automation.

@Leia Pearson's comment (quite some time ago) above is spot on. Enterprise business looks for opportunities to be proactive. Part of that journey is to bring visibility to everything that's exceeding the SLA's. Once the clean-up is completed, you put dashboards in place to allow visibility into things before they breach the SLA's. 

Currently I use "updatedDate < -4h" for hours or "updatedDate < -240m", for minutes. 
My business hours are from Sunday at 5 PM PST to Friday at 5 PM PST.

If I set my business hours I would like my query to exclude everything outside of it when calculating. I could write my query using this instead, "updatedDate < -4bh" for business hours or "updatedDate < -240bm", for business minutes.

Hope this feature makes it on the books soon. I'm sure a lot of Enterprise companies would benefit from it. 

I recently created a Quick Filter which highlights a card which has been completed since the previous workday:

resolved >= startOfDay(-1d) or (resolved < startOfWeek(-1d) and resolved >= startOfDay(-3))

…which translates to: moved to “Done” yesterday OR moved to “Done” before the current week starting Saturday and also within the last 3 days.

This is a slightly different appproach than other solutions presented. My hope is this helps other create solutions they need.

+1 the current workarounds do not seem to work for me, but still mid-troubleshoot:

https://community.atlassian.com/t5/Jira-Core-Server-questions/Exclude-weekends-in-JQL-Query/qaq-p/1030290

I went searching to see how I could filter on business days, and I was shocked to find that this has been a known deficiency in Jira for 10 YEARS and nothing has been done about it?!

I agree with the need as stated by Leila.

This issue is important to us too. We currently have filters set up to check if issues are spending too much time in various statuses and we want the time spent to only include working days. After a weekend, all of those times are misleading. Also, we have certain issue types where we want to make sure we start work on them within a certain number of days. Again the number of days should be working days but after a weekend it looks like we've exceeded our SLAs. 

Come on y'all, please build this

Any update from Atlassian ?
This functionality is important for e.g. rolling weekly Team Scrums, where I want to look at issues updated in the last 2 working days, or where time has been logged in the last 2 working days. Very hard to calculate this in JQL without a working days function, e.g.

"updated >= endOfWorkingDay(-2d)"

Hi Joe,

Yes, It supports JQL query by color (Green, Yellow, Red). You can check out the screenshots at https://akeles.jira.com/wiki/display/DAY/Usage+Guide

I presume what you want is to find out those issues with status that has been in progress for more than 1 working day.
You can do it via the following steps

• add a traffic light custom field
• set up the calendar to indicate the non working days (weekends and holidays)
• update the thresholds (e.g. Yellow for >1 working day, Red for >2 working days)
• amend the workflow
  • to trigger on the traffic light counting when issue goes into "In Progress status"
  • to trigger off the traffic light counting when the issue leaves "In Progress status"
• Then u can query for those issues with Yellow or Red traffic light

Hope it helps.

Hi Akeles,

Looks promising! Does it support JQL, e.g I have a query that looks something like:

status = "In Progress" AND status changed to "In Progress" before -5d

But that counts weekends, so what I really need is

status = "In Progress" AND status changed to "In Progress" before -1business-day

Does your plugin do this?

We have done a Days Elapsed Plugin for JIRA for the Codegeist competition.
It is able to count the number of working days and associate it with a traffic light colour.
It is also possible to do JQL search based on colours.

You can find out more details at https://akeles.jira.com/wiki/display/DAY

Just adding my voice in here. We need to be able to escalate issues that have been open longer than x business days.

+1 We need it as well for SLA purposes.

We need this as well. We want to query tickets that have not been touched for 3 business days (and then send an alert via a subscription). Very much needed!

+1 I have this requirement too. Please reconsider prioritizing and adding to the JIRA roadmap

So I have this query which seems to work for the case of yesterday and friday. And could be adjusted to work for more cases.

status CHANGED AFTER -1d OR ( status CHANGED DURING (-3d, endOfWeek(-1w) ) )

The during clause will be false most of the time since -3d will be after the -1w except for monday
-3d could be changed to startOfDay(-3d)
Doesn't handle holidays but Gets you 90% I think

I need to find tickets that have gone longer than 5 BUSINESS days without feedback. Weekends make it difficult to get this set.

I also have this requirement.

Hi Any update on this?

+1 for this. We also need to put in some automation to alert if certain issue is not updated for N business days... and its frustrating if weekends count as a business day.

We would like this feature for our Monday stand-ups as well.

Any update?

Agreed; solving the "weekend problem" takes care of the majority of cases.

Adding the ability for an admin to be able add "company holidays" would probably be useful for a number of things.

+1 to Graham's comment; our Monday stand-ups always make us feel guilty for not doing any work on Sundays...

Any news on this?

I'm hoping this can be implemented soon...

When we do stand-up, we want to highlight issues that were in progress on the previous working day. Using a AFTER -1d filter works for Tuesday-Thursday but not for Monday because it filters for things that were in progress since Sunday rather than since Friday!

Another option which would also solve my problem is to add in some more standard SQL date and time functions eg: DAYOFWEEK or DATEPART

Then I could do something like
where updated <= -3d and dayofweek(updated) between 2 and 5

while this isn't going to work for public holidays etc, it will solve 99% of the issue (issues created on Friday behave like they are 3d old on Monday) and having the extra SQL functions are probably handy in other situations.