How Fields Mapping works
Fields Mapping lets you choose which Jira fields Planyway uses for Start date and End date. It is available in Calendar, Timeline, Gantt, and Workload.
Each tab has its own mapping. Start and End dates are configured separately.
When you change a mapped field, Planyway immediately reads dates from the new field. Cards may move or become unscheduled if that field contains different or empty values.
Changing the mapping does not copy dates between Jira fields.
Fields Mapping options
For Start date and End date, you can choose:
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.
Specific 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.
Let non-admins use hidden Jira fields
A mapped field may not be added to the Jira screen for some issues. Planyway can still write to such hidden fields when this setting is enabled:
Settings center → General settings → Let non-admins use hidden Jira fields
The setting:
is enabled by default;
applies to the entire Jira site;
can only be changed by Jira global administrators.
When enabled, users who can edit an issue can also update its mapped date fields even if those fields are not on the Jira screen.
When disabled, hidden fields can only be updated by:
Jira global administrators;
administrators of the corresponding space/project.
Regular users can still select a hidden field in Fields Mapping, but they will not be able to save dates to it.
Warnings and errors
An orange warning icon may appear next to a mapped field if it is not available on Jira screens for some connected spaces or work types.
This warning normally appears only when the current user cannot write to hidden fields.
To fix it, either:
add the field to the relevant Jira screen;
enable Let non-admins use hidden Jira fields;
choose another field.
If Planyway cannot save the date, you may see:
Couldn't save {field} — {field} is not on Jira screen. Ask an admin to allow writing to hidden field.
If an issue is created but its dates cannot be saved, the issue is still created without dates:
Issue created in the backlog — Dates weren't saved — {fields} are not on Jira screen. Ask an admin to allow writing to hidden fields.