Date mapping

Only Jira Admins and App Admins can configure Date mapping settings.

Important note

When mapping date fields to Jira fields, ProScheduler follows Jira’s specifications. As a result, some advanced features are not supported, including:

What is date mapping? Date mapping in ProScheduler allows you to automatically sync the task’s start and end dates between Jira and ProScheduler. This ensures that when you plan the start and end dates of a task in ProScheduler, they are reflected in Jira, and vice versa, making it easier to manage project timelines across both platforms.

How it works:

Plan in ProScheduler: When you set the start and end dates in ProScheduler, they are automatically synced to the corresponding date fields in Jira.
Plan in Jira: When you set the start date or end date in Jira, those changes are reflected in ProScheduler.

ProScheduler supports mapping Date Fields in Jira.

What are Date Fields in Jira?

In Jira, Date fields are used to track dates related to issues and tasks. Jira date fields can vary depending on the project or work item type and may even be customized by users.
Date Picker: This field type captures only the date (e.g., Due date, Start date). They do not include a time component and are typically used for scheduling purposes.

What Are Date Fields in ProScheduler?

In ProScheduler, the primary date fields you will interact with are:

Start date: This is the date when the task is planned to begin.
End date: This is the date when the task is planned to be completed.

These date fields are used for scheduling and tracking task timelines within ProScheduler.

Before you map Jira date fields to ProScheduler, ensure that your desired Jira fields (e.g., Start Date or Due Date) are already available in your Jira project or work item type.

Accessing Date mapping

Click on ⚙️ Settings from the sidebar.
Select Date mapping in the app settings.

You can also configure date mapping from Board settings

Configuring Date mapping

You can configure the field mapping for each project by following the steps below:

Select the project you want to configure in the dropdown list.

Toggle “Map dates with Jira fields” button ON to enable the mapping feature.

Select the Jira fields you want to map to the Start date and End date.

Green checks (✅) indicate that these fields can be mapped and the dates will be applied successfully for that work item type.

If a red cross (❌) appears next to any field, it means that the selected field does not exist for that work item type in your project configuration. As a result, ProScheduler cannot map the fields to your Jira fields.

=> You will need to reconfigure your Jira project to make sure that your desired Jira fields are already available in your work item type.

For troubleshooting steps, read this: How to add date fields to your Jira Projects

Click to save the field mapping configuration without migrating any app data.

Once complete, all previously app data within the project will be reset and aligned with the newly mapped dates.

Use Case

Use this when Jira already contains valid planning data (Start and Due Dates), and you want to map the app to Jira fields without changing existing Jira data.
Or you want to map Jira fields for future tasks without transferring current data from ProScheduler to Jira.

If you need more details, take a look at the example:

Example

USE CASE 1 Mapping with existing Jira Data

You already have a list of work items in Jira with Start and Due Dates.

Once you enable field mapping, ProScheduler will automatically sync with this existing Jira data

USE CASE 2 Future task mapping only

Your current tasks in ProScheduler are finalized, so you don’t want to transfer any of that data to Jira.
You're starting a new sprint next week and want all upcoming tasks in the app to sync with Jira's field structure (e.g., Start and Due Dates).

Migrate existing App data to Jira fields

After saving the field mapping configuration, if you want to keep the app’s existing planning data (Start and End Dates) and apply it to Jira

=> Click . This will sync and transfer data from the app to the selected Jira fields.

If you need more details, take a look at the example:

Example

You’ve already planned your project timeline in TeamBoard ProScheduler, with defined Start Dates and End Dates for each task. Now, you want that data to be reflected in Jira so your team can see the same schedule in both platforms.

By clicking Migrate, you copy the app’s scheduling data directly into the mapped Jira fields (e.g., “Start date” and “Due date”).

⚠️ Important behavior: Task planned multiple times

If you assign the same task multiple times in ProScheduler, only the task plan with the earliest Start Date will be kept when you click Migrate.

If you need more details, take a look at the example:

Example

You assign the same task "Review Backend Code" multiple times to Anna in ProScheduler:

Assigned To	Start Date	End Date
Anna	July 15	July 15
Anna	July 17	July 17
Anna	July 18	July 18

Now you map and click Migrate.

✅ Result:

ProScheduler will keep the task with the earliest Start Date, in this case, July 15, and sync it to Jira.
The other task plans with later dates (July 17 and July 18) will be removed.

Overwrite existing data of Jira fields

This option will prioritize the data from Teamboard's app. If unchecked, the existing data from the Jira field will be kept.