Field mapping connects Planyway's Start date and End date to the corresponding fields in Jira.

It allows Planyway to read dates from Jira and, where permitted, update those dates when you reschedule work.

Field mapping is available in Calendar, Timeline, Gantt, and Workload views.

Each tab has its own field mapping configuration.

You can configure each date independently.

Default

Uses the date field configured in Space settings for each connected Jira space.

Do not sync

Planyway does not read or write this date to Jira. You can still schedule and move cards in Planyway, but the date is not saved to a Jira date field.

Target Jira field

Uses the selected Jira field for all connected spaces on this tab. For this date, the corresponding Space setting is ignored.

For example, if you select Due date for End date, Planyway uses Due date for every connected space on this tab.

Planyway immediately starts reading dates from the newly selected field.

As a result, some work items may move to different dates or become unscheduled when the newly mapped field is empty.

Changing field mapping does not copy existing dates between Jira fields.

Some Jira fields may not be included on the screens used to edit work items.

Jira global administrators can manage whether non-admin users are allowed to update mapped date fields that are hidden from Jira screens.

This option is located under:

When enabled, users with permission to edit an issue can also update its mapped hidden date fields.

If dates cannot be saved, check Jira field visibility, user permissions, and the selected field mapping.