Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

How to remove non-working days?

Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
March 12, 2024

Teams that use Jira to track their work must clearly understand where time is spent. This knowledge allows to improve processes and estimates. And often companies don’t know how to set JIRA Instance according to our office working time. Unfortunately, standard reports do not consider non-working time such as weekends, holidays, nights, and vacations.
In this article, we will learn how to set up non-working days calendar and obtain accurate metrics for actual throughput and cycle time.


How to exclude non-working time in Jira?

The Time in Status for Jira solves this problem by allowing you to set calendars and exclude non-working hours, breaks, holidays from your analytics and forecasting.

Знімок екрана 2024-03-13 о 00.34.31.png

Why Time in Status for Jira?

 -  💡 Accurate Cycle Time: Measure active working days/hours instead of just total elapsed time for a true gauge of throughput

 -  💡 Customize Calendars: Define working days/hours and sync company holidays to automate non-working time calculation

 -  💡 Burndown Visibility: Watch effective burndown of issues over working time instead of weekends/holidays skewing the view

 -  💡 Time in Status Reports: The core report shows median and other percentiles of working time for any status or issue.

How calendars work in Jira?

For a typical dev team working regular business hours, there can be a significant difference between calendar and actively working time for an issue. 

A bug is picked up on Friday and completed the following Thursday. From a 24/7 calendar perspective, that's six elapsed days.Знімок екрана 2024-03-13 о 00.33.35.png

However, looking at working days tells a different story. If the team only works Monday through Friday, then there were only four working days between the start and completion of that bug. 

By integrating the team's working calendar, Time in Status accounts for this. 

Знімок екрана 2024-03-13 о 00.31.45.png

The reports would time spent working on issue in this status and cycle is four days instead of six calendar days. This prevents weekends from skewing the metrics and provides a more accurate representation of actual throughput and cycle time.

By having visibility into accurate working time, the team can:

  • Make accurate estimates and forecasts in working days/hours.
  • Provide management with a clearer view of the team's active bandwidth and capacity.
  • Set service levels based on realistic working time expectations.
  • Motivate better performance by removing artificial weekend drags.


By integrating calendars, the dev team gets precise data on where their active time is going instead of looking at the total elapsed clock time. This leads to better calculations, estimates, visibility, and higher productivity. For any team using Jira, setting work calendars with Time in Status for Jira is a critical step toward more meaningful metrics and higher productivity.

That is why I am pleased to offer you a 30-day trial of Time in Status for Jira. Furthermore, our add-on is free for up to 10 users, allowing you to evaluate its effectiveness in your processes.

See you in Time in Status for Jira 👋 😊



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events