Work Schedule Settings

The Work Schedule tab defines when work happens on this project. Configure working days, daily hours, and holidays to ensure capacity calculations, sprint planning, and time tracking reflect reality.

Schedule Hierarchy

GitScrum uses a hierarchy for work schedules:

1. Workspace default: Applies to all projects unless overridden
2. Project override: This project uses custom schedule

The toggle "Override workspace schedule" controls which applies.

Override Workspace Schedule

When Disabled (Default)

The project uses workspace-level schedule settings. An info box displays:

• Current workspace working days
• Hours per day from workspace settings

Any schedule changes require workspace admin access.

When Enabled

The project uses its own custom schedule. Full configuration options appear:

• Working days grid
• Hours per day slider
• Project-specific holidays

Working Days Configuration

Day Selection Grid

Seven buttons represent each day of the week:

Selecting Working Days

Click a day to toggle:

• Active (highlighted): Work day
• Inactive (muted): Non-work day

Most organizations use Monday-Friday. Some scenarios require different configurations:

• Weekend coverage: Include Sat/Sun
• Religious observance: Exclude specific days
• Compressed schedule: Four 10-hour days

Working Days Count

Below the grid, a summary shows: "X working days per week"

This affects:

• Weekly capacity calculations
• Sprint day counts
• Resource availability forecasting

Hours Per Day

Setting Daily Hours

A slider or input controls hours worked per day:

• Range: 1-24 hours (practical range: 4-12)
• Default: 8 hours
• Increments: 0.5 hours

Weekly Capacity

The configuration shows calculated weekly capacity:

Hours per day × Working days = Weekly capacity
8 hours × 5 days = 40 hours/week

Impact on Planning

Hours per day affects:

• Sprint capacity: Total available hours
• Effort-to-hours conversion: Story points to hours ratio
• Time tracking expectations: What counts as a "full day"
• Burndown calculations: Expected daily progress

Project Holidays

Holiday List

View and manage project-specific holidays that exclude days from working time.

Adding Holidays

1. Click "Add Holiday"
2. Select date from date picker
3. Click "Add" to confirm

Holidays appear in chronological list:

• Date displayed in locale format
• Delete button to remove

Removing Holidays

Click the remove icon next to any holiday. It's deleted immediately.

Holiday Impact

Holidays affect:

• Sprint planning: Day excluded from sprint duration
• Capacity calculations: Reduced available hours
• Calendar views: Day marked as non-working
• Deadline calculations: Account for holidays

Common Holidays to Add

Consider adding:

• National/public holidays
• Company closure days
• Team off-site events
• Extended breaks (holiday season)

Bulk Holiday Management

For many holidays, consider:

1. Manage at workspace level (applies to all projects)
2. Use project-level only for project-specific closures

Saving Changes

Save Button

Click "Save" in the header to persist changes. The button shows:

• Save Changes: Changes detected
• Saving...: Save in progress
• Successfully saved returns to normal state

When to Save

Changes require explicit save:

• Modified working days
• Changed hours per day
• Added or removed holidays
• Toggle override setting

Navigating away with unsaved changes prompts confirmation.

Schedule Source Indicator

The header shows current schedule source:

• "Using workspace schedule": Project inherits workspace settings
• "Using project schedule": Override is active

This helps quickly identify which configuration applies.

Impact Visualization

Capacity Preview

When planning sprints, the schedule affects:

Example calculation:

• Working days: Mon-Fri (5 days)
• Hours per day: 8 hours
• Sprint length: 2 weeks
• Holidays in sprint: 1 day

Available days: (5 days × 2 weeks) - 1 holiday = 9 days
Total capacity: 9 days × 8 hours = 72 hours

Time Tracking Context

Schedule affects how logged time displays:

• Daily totals compare against hours per day
• Weekly totals compare against weekly capacity
• Overtime calculated when exceeding schedule

Common Configurations

Standard Work Week

Days: Mon, Tue, Wed, Thu, Fri
Hours: 8 per day
Weekly capacity: 40 hours

Compressed Work Week

Days: Mon, Tue, Wed, Thu
Hours: 10 per day
Weekly capacity: 40 hours

Six-Day Week

Days: Mon, Tue, Wed, Thu, Fri, Sat
Hours: 7 per day
Weekly capacity: 42 hours

Part-Time Project

Days: Mon, Tue, Wed
Hours: 6 per day
Weekly capacity: 18 hours

Best Practices

Accuracy Over Optimism

Set realistic hours: If team actually works 6 productive hours, don't set 8.

Include holidays early: Add known holidays at project start.

Review periodically: Adjust as team patterns change.

Consistency

Match reality: Schedule should reflect how work actually happens.

Team awareness: Ensure team knows the configured schedule.

Update promptly: Adjust when circumstances change.

Override Wisely

Use workspace defaults when projects follow standard schedule.

Override only when needed:

• Client in different timezone/region
• Project with unique requirements
• Temporary different schedule

Permissions

Regular members see the schedule but cannot modify it.

Troubleshooting

Capacity Calculations Wrong

Check:

• Working days correctly set
• Hours per day accurate
• Holidays properly entered
• Override toggle in expected state

Schedule Not Applying

If using workspace schedule:

• Verify override is disabled
• Check workspace settings for correct values

If using project schedule:

• Confirm override is enabled
• Save after making changes

Holidays Not Excluded

• Verify holiday is in correct date format
• Check holiday falls within relevant period
• Ensure holiday was saved (not just added)

Sprint Capacity Mismatch

Sprint capacity combines:

• Work schedule settings
• Team member availability
• Individual time off

All three factor into final capacity. Check each if numbers seem wrong.

Technical Notes

Timezone Handling

Holidays and working days use project timezone. Ensure project timezone is correctly configured for accurate date handling.

Date Format

Holiday dates display in your locale's format. The system stores dates in ISO format (YYYY-MM-DD) regardless of display.

API Access

Work schedule is accessible via API:

GET /projects/{slug}/settings/schedule
PUT /projects/{slug}/settings/schedule

Useful for programmatic schedule management.

Work Schedule ensures GitScrum's planning and tracking features reflect how your team actually works. Configure accurately, maintain diligently, and your capacity planning stays grounded in reality.