Table of Contents

Exclude Non Working Days from Cycle Time

Sometimes, development teams are not working, and that is expected. In fact, there are typically two days each week when development teams are not expected to be working. They're called weekends. LinearB can be configured to omit weekend hours from your team and the company's overall cycle time calculation.

Betsy Rogers
Updated by Betsy Rogers
This feature is currently in beta, please reach out to your account manager or our support team in order to enable this feature.

Sometimes, development teams are not working, and that is expected. In fact, there are typically two days each week when development teams are not expected to be working. They're called weekends. LinearB can be configured to omit weekend hours from your team and the company's overall cycle time calculation.

Note that this adjustment will take effect only on the overall cycle time calculation in your metrics reports or team dashboard. Weekend work will be flagged but still visible when viewing individual branches in your Activity tab.

How to exclude weekends from my cycle time calculation

To exclude weekend hours from your overall cycle time calculation, click on the gear icon in the top right of your LinearB application, and select Company Settings. In the General tab, check the toggle next to "Exclude Cycle Time calculation on weekends"

Select your company's typical weekend days. Don't forget to click "Save Settings"!

This change will take effect globally over all of your teams. If you have teams that observe different weekend days, each team can be configured to match their respective weekends.

Configure your individual team weekends

Once the toggle to exclude weekends is enabled, you can select any team settings and adjust your team's weekend days from the team settings page.

How does excluding weekends affect my cycle time?

Work done over the weekend

In cases where work is done over the weekend, LinearB will account for the time during working days, and omit weekend hours.

Example: 
  • A team working week is configured from Monday to Friday 
  • A Developer opened a PR on Friday 20:00 
  • The PR was picked up on Saturday at 8:00

Pickup time will be calculated as 4 hours (20:00 to 00:00) instead of 12 hours

Note that the cycle time will be updated in your team and company cycle time dashboard, and in relevant metrics reports in your Metrics tab. You will still see the full cycle time of a branch when viewing individual branches in your Activity tab.

Work carried over the weekend

In the case of a PR being carried over the weekend, LinearB will account for the time during working days when the PR was open.

Example: 
  • A teams working week is configured from Monday to Friday 
  • A Developer opens a PR on Friday 20:00 
  • The PR is picked up on Monday at 8:00

Pickup time in this instance will be calculated as 12 hours instead of 50 hours.

Note that the cycle time will be updated in your team and company cycle time dashboard, and in relevant metrics reports in your Metrics tab. You will still see the full cycle time of a branch when viewing individual branches in your Activity tab.

What will my metrics look like with weekends excluded?

Dashboard view

Individual team and the "All Teams" dashboard will reflect an updated cycle time calculation, omitting weekend days.

Metrics view

When viewing a daily breakdown of cycle time, you will notice that days marked as weekend days will show a cycle time of 0.

Activity View

The activity view will still display the full cycle time of any individual branch. This will allow you to see a full view of individual branch performance. Branches that spanned over a weekend or were worked on during a weekend will include a purple flag to highlight the segment of a branches cycle time which spanned over a weekend.

How did we do?

Configuring SSO with Okta

Favoriting Project Delivery Trackers

Contact