TeamBoard ProScheduler

Importing

🔐

Permissions Required

Only App Admin and Board Admin can import project files.

If you have an existing project planned outside of Jira and want to manage it in TeamBoard ProScheduler, you can import your files directly instead of manually recreating tasks. Your Gantt chart will automatically populate with all project details and hierarchies.

Supported file formats:

  • MS Project: .mpp, .mpt

  • MS Excel / Spreadsheets: .csv, .xls, .xlsx


How to import tasks from a file

Step 1: Open the Import dialog

1 one circle blue Navigate to the Gantt option in ProScheduler

CleanShot 2025-10-13 at 23.24.47@2x-20251013-162522.jpg

2 two circle blue Click the Import icon in the top-right corner

CleanShot 2025-10-13 at 23.29.42@2x-20251013-163024.jpg

3 three circle blue In the Import modal, click Browse to upload your file.

CleanShot 2025-08-02 at 15.06.39@2x-20250802-080709.jpg

Step 2: Configure file settings

check mark Importing from MS Project (.mpp, .mpt)

  1. Select the destination Jira Project.

  2. (Optional) Check Convert parent issues to Epic if you want top-level parent tasks to be imported as Jira Epics (Hierarchy: Epic → Task).

  3. Click Import to load the data into ProScheduler.

CleanShot 2025-08-02 at 15.05.46@2x-20250802-083648.jpg

check mark Importing from Excel / CSV (.csv, .xls, .xlsx)

  1. Select the destination Jira Project.

  2. Map your file columns to ProScheduler fields:

    • Summary (Required): The task title mapped to the Jira Issue Summary.

    • Start Date & End Date (Optional): Supported formats include YYYY-MM-DD, DD/MMM/YY, DD-MM-YYYY, and MMM-DD-YYYY.

    • Parent Row (Optional): The row number representing the parent task.

    • (Optional) Check "Convert parent issues to Epic" (Hierarchy: Epic → Task).

  3. Click Import to finish.

CleanShot 2025-08-02 at 15.35.00@2x-20250802-083807.jpg

For reference, see the example .xlsx file format below: Example file.xlsx

CleanShot 2025-08-02 at 15.46.52@2x-20250802-084928.jpg
Example file
CleanShot 2025-08-02 at 15.50.30@2x-20250802-085038.jpg
The result after successfully importing a project into TeamBoard ProScheduler.

⚠️ Important: How imported tasks appear across ProScheduler

How imported tasks behave on the Gantt chart, Schedule board, Calendar, and Workload depends on your board's Date fields mapping setting:

Board setting

Where dates are stored

Gantt visibility

Schedule Board, Calendar & Workload visibility

Assignee behavior

Date fields mapping is ON

Plans use the mapped Jira date fields. Updates in ProScheduler reflect the corresponding Jira fields.

check mark Visible immediately with planned dates

check mark Visible immediately

Changing the Jira assignee automatically assigns the schedule/workload.

Date fields mapping is OFF (default)

Plans use TeamBoard date fields only. Updates in ProScheduler do not update Jira date fields.

check mark Visible immediately as unassigned plan bars

⚠️ Not visible until a Plan Assignee is set

Work item Assignee and Plan Assignee are managed separately.

💡

Note

When Date fields mapping is OFF, ProScheduler uses an independent planning layer. Dates and assignees set in the app do not overwrite Jira fields, allowing multiple assignees and custom allocations per issue.

How to display imported tasks on the Schedule board & Calendar

To assign imported plans to team members so they appear on the Schedule Board, Calendar, and Workload views, use the following method:

  1. On the Gantt, right-click the task's schedule bar

  2. Select Planning details

  3. Set the Assignee and adjust hours/day if needed, then save


Best Practices for Importing

  • Use a consistent date format across all date cells (recommended: YYYY-MM-DD).

  • Double-check that every Parent Row value references a valid row number in your file when building hierarchies.

  • Enable Date fields mapping before importing if you want automatic 1:1 syncing between Jira assignees and the Schedule Board.

  • Keep Date fields mapping turned off if you need recurring tasks, custom plan allocations, or multiple assignees per issue.

  • Keep column headers simple (e.g., Summary, Start Date, End Date, Parent Row) for seamless auto-mapping.