Bulk import schedules using CSV
Schedules define when your agents are expected to work. Each schedule belongs to a team, is assigned to one or more agents, and specifies working hours, days, frequency, and duration.
While you can create schedules individually, the Import schedule feature lets you set up multiple agent schedules simultaneously. By uploading a single CSV file, you can bypass individual manual entries and get your teams up and running at once.
This is especially useful when:
You're setting up Workforce management for the first time and need to create many schedules quickly
You're migrating schedules from other systems
You need to set up schedules for teams across multiple shifts, regions, or time zones
Before you begin
Before importing schedules, make sure you have:
Admin access to your Jira Service Management project with Workforce Management enabled
Your agents must belong to a team already connected in Workforce management. To connect teams, go to Space settings → Workforce
Every agent email must match their Atlassian account and their team membership.
A CSV editor such as Microsoft Excel, Google Sheets, or any spreadsheet editor
Step 1: Download the CSV template
In Jira Service Management, go to Workforce → Schedules.
Select Import schedule to open the import modal
Select the CSV template link to download the formatted file
Open the file in your preferred spreadsheet application.
Step 2: Fill in the CSV template
The template includes the following columns. All columns are required unless marked as optional.
Schedule Name: A display name for the schedule. Use any text string.
Example:
APAC Morning Shift
Team/TeamID: The name or ID of the team connected in Workforce management.
Example:
Support Team APAC
Agent Email: Agent email addresses. Each agent must be a member of the specified team. Use a valid email address, or multiple addresses separated by a semicolon (;).
Example:
ryan.chen@example.com; priya.singh@example.com
Schedule Start: The date and time when the shift begins. Use ISO 8601 format:YYYY-MM-DDTHH:MM:SS.
Example:
2026-05-01T09:00:00
Schedule End: When the shift ends. This must be on the same day as the Schedule Start, and the duration must be within 24 hours. Use ISO 8601 format: YYYY-MM-DDTHH:MM:SS.
Example:
2026-05-01T17:00:00
Timezone: Standard IANA timezones for the shift. You can find a full list of timezone identifiers at IANA tz database.
Example:
Australia/Sydney
Schedule Frequency: How often this schedule repeats. Accepted values are None, Daily, Weekly, or Monthly.
Example:
Weekly
Mon – Sun: The days the schedule applies (for Weekly frequency). Use 1 for Yes or 0 for No.
Example:
1
Repeat on Date/Day: For monthly schedules, choose how the recurrence is calculated based on the Schedule Start. Accepted values are Date or Day. Leave this blank for non-monthly frequencies.
Example: If Schedule Start is
2026-05-01(the first Friday of May):Date: Repeats on the 1st of every month.Day: Repeats on the first Friday of every month.
Ends On: The end condition for the recurrence. Accepted values are Never or On Date. Leave this blank if there is no frequency.
Example:
On Date
Ends On Date: The date the recurrence stops. This is required when Ends On is set to On Date. Use the format YYYY-MM-DD.
Example:
2026-06-30
Tips for a successful import
Keep headers intact: Do not rename or remove any columns. The system needs these exact headers to map your data correctly.
Match team names exactly: Ensure team names match your Workforce management settings. If you have duplicate team names, use the Team ID to avoid errors.
Save as CSV: Always export or save your file in
.csvformat before uploading.
Step 3: Upload and import the CSV
In the Import schedule modal, select CSV file to upload your file.
Once uploaded, select Import.
Your new schedules will appear instantly on the Schedules page.
Note: The maximum file size is 5 MB. For larger datasets, split your data into multiple CSV files and import them separately.
Troubleshooting
If your import fails, don't worry. We’ll provide a downloadable CSV file with a Validation Errors column explaining exactly what went wrong in each row. You can then match the error message against the fixes below.
Agent not found: Verify the agent email addresses. Ensure they are members of the specified team connected to Workforce management or tagged to the correct team in your file.
Team not found: Check your team’s name in Space Settings > Workforce > Connect teams to ensure it is connected. Use the Team ID if multiple teams share the same name.
Invalid date or time format: Ensure all dates follow the YYYY-MM-DDTHH:MM:SS format.
Invalid timezone: Use a valid IANA timezone identifier, such as America/New_York.
Invalid frequency value: Use only None, Daily, Weekly, or Monthly.
Schedule duration exceeds 24 hours: Ensure each individual shift is 24 hours or less.
Missing required column: Download the template again and input your data without modifying any headers.
File format not supported: Export your spreadsheet as a .csv file. Formats like .xlsx or .xls are not supported.
File too large: Split your data into multiple CSV files (each under 5 MB) and import them separately.
Partial imports: If only some rows have errors, the valid rows will still be imported. The CSV with validation errors will only contain rows that failed to import. You only need to fix and re-upload the failed rows.
Frequently asked questions
Can I import schedules if I already have existing schedules?
Yes. Imported schedules are added alongside your current ones. They won't overwrite or delete any existing data.
Can the same agent appear in multiple rows?
Absolutely. You can use multiple rows to assign different shifts (like a weekday morning shift and a weekend on-call shift) to the same agent.
What if my team name is not unique?
If you have multiple teams with the same name, use the Team ID in the Team/TeamID column to ensure the schedule is assigned to the correct team. Team IDs can be found from your Workforce management settings.
Was this helpful?