Work Schedule Settings

The Work Schedule tab configures default working hours and days for your entire workspace. These settings affect time tracking calculations, capacity planning, and availability indicators across all projects.

Working Days Configuration

The working days grid shows all seven days of the week. Click any day to toggle it as a working day or non-working day. Working days appear highlighted, while non-working days remain dimmed.

The default configuration includes Monday through Friday as working days. Many teams keep this traditional schedule, but you can customize it to match your organization's reality:

• Select Saturday and Sunday for teams with weekend schedules
• Deselect specific weekdays if your organization observes different rest days
• Create four-day work week configurations by deselecting one weekday

The counter below the grid shows how many working days per week you have configured. This number affects weekly capacity calculations throughout GitScrum Studio.

Hours Per Day

The hours per day slider sets the standard workday duration for your workspace. This value is used for:

• Converting between hours and days in time estimates
• Calculating weekly and monthly capacity
• Determining over-allocation warnings in workload views
• Time tracking reports and analytics

Most teams use 8 hours per day, matching a standard full-time schedule. Adjust this value if your organization uses different standard hours (for example, 7.5 hours or 6 hours for compressed schedules).

The interface shows weekly capacity based on your configuration (hours per day multiplied by working days). This helps you verify the settings match your expectations.

Holiday Management

The holidays section lets you define non-working days that fall on otherwise working days. Adding holidays ensures accurate capacity planning by excluding these dates from availability calculations.

Adding Holidays

To add a holiday:

1. Click "Add Holiday" to reveal the date picker
2. Select the holiday date
3. Click "Add" to save

Holidays are displayed in chronological order. Each entry shows the formatted date with a remove button that appears on hover.

Holiday Considerations

When adding holidays:

• Add recurring holidays annually (the list does not auto-repeat year to year)
• Include company-specific holidays and observances
• Consider regional holidays if you have distributed teams
• Remember that individual team members may have additional personal time off not reflected here

How These Settings Apply

Work schedule settings establish workspace-wide defaults. Here is how they interact with other parts of GitScrum Studio:

Project-level overrides: Individual projects can have their own work schedules that override workspace defaults. This is useful for projects with different requirements or client expectations.

Team member availability: Work schedules affect how available hours are calculated when viewing team workload or assigning tasks. A team member with 20 hours of tasks in a 40-hour week shows as 50% allocated.

Time tracking calculations: When converting time entries to reports, the system uses work schedule settings to determine working days in a period, expected hours, and utilization percentages.

Calendar views: Non-working days appear differently in calendar views, helping you visualize when work is expected to happen.

Pro Tips (Once You Are Comfortable)

• Time-saver: Add all known holidays for the year at once. This prevents capacity planning surprises later.

• Did you know? Hours per day affects burndown charts and velocity calculations. If your team consistently works fewer hours, adjusting this setting makes metrics more accurate.

• Common mistake: Forgetting to add regional holidays when working with international teams. Team members in different locations may have different holidays.

• Power move: Review and update work schedules quarterly to catch any changes in organizational policies or upcoming holiday schedules.

Permissions

Only Agency Owners can modify Work Schedule settings. These settings apply workspace-wide, so changes affect all projects and team members.

How to Report a Problem or Request a Feature

If you encounter issues with work schedule settings or have suggestions for improvements, submit feedback through GitScrum Studio. In the Sidebar, click on Support Tickets and open a ticket describing your request.