Field mapping
In this step, you decide how Microsoft Planner fields map to Jira fields.
Issue Type (required)
You must select the Jira issue type to use for newly created issues.
All new tasks from Planner will be created as this issue type.
Date Fields
Start Date and Due Date from Planner can be mapped to Jira date or custom date fields.
Make sure your selected Jira project has the necessary custom fields available.
Planner Premium: dates and the project calendar
Planner Premium uses a Monday–Friday project calendar. This affects how dates are handled:
If a Jira due date falls on a Saturday or Sunday, Planner Premium automatically adjusts it to the previous Friday.
If a Jira start date falls on a weekend, Planner Premium adjusts it to the next Monday.
The connector detects these calendar adjustments and does not sync them back to Jira — your original Jira dates are preserved.
When a weekend date is sent to Planner Premium, a
[MS-SYNC]comment is posted on the Jira issue to let you know the date was adjusted on the Planner side.
Planner Premium: clearing dates
Planner Premium does not support clearing start or due dates once they are set. If you remove a date in Jira:
The Planner task keeps its original date (Planner Premium silently ignores the change).
A
[MS-SYNC]comment is posted on the Jira issue explaining that the date could not be cleared.
Bucket
Planner buckets can be mapped to Jira select list custom fields.
Tip: Create a custom select field in Jira (e.g. “Planner Bucket”) if you want to keep bucket info in sync.
Status Mapping
There are two ways to sync status between Planner and Jira:
Option 1: Progress-based (Default)
Planner has only three progress values: Not Started (0%), In Progress (50%), and Completed (100%).
You select which Jira status should be set when syncing from Planner.
When syncing back to Planner, the app uses Jira status categories to decide progress:
Gray (To Do category) → Not Started
Blue (In Progress category) → In Progress
Green (Done category) → Completed
This means multiple Jira statuses can map into the same Planner progress value.
Option 2: Bucket-based
If your Jira workflow has more than three statuses and you need finer control, you can map Jira statuses directly to Planner buckets instead of using progress percentages.
Each Jira status maps to a specific Planner bucket (and vice versa).
When a task moves to a different bucket in Planner, the corresponding Jira status is set.
When a Jira issue changes status, the task moves to the mapped bucket in Planner.
This approach works well when your Planner buckets represent workflow stages (e.g., "To Do", "In Review", "QA", "Done") that align with your Jira statuses.
Assignee
You can sync assignees between Planner and Jira using one of the following methods:
Option 1: Automatic matching by name
Enable user mapping and select "Match by full name".
The app will automatically match users across systems based on their display names (case-insensitive).
Works well when users have the same name in both Planner and Jira.
Option 2: Manual user mapping
For users with different names across systems, you can create explicit mappings between Planner users and Jira accounts.
These direct mappings take priority over automatic name matching.
Option 3: Description embedding
If you prefer not to map users directly, assignee information can be included in the description instead.
Example: A Planner task synced into Jira will have its original assignee listed in the issue description.
Labels
Labels can be synced, but only from the set of labels defined in Planner.
Planner supports up to 25 labels. Jira supports unlimited labels, so:
Only labels that exist in Planner are eligible for sync.
Jira labels outside this set will be ignored.
To sync labels, Planner users must rename default colored labels (e.g. “Red”, “Yellow”) into meaningful names. These renamed labels will then appear as available for sync.
Sub-tasks and hierarchy
The connector syncs tasks as flat items:
Jira sub-tasks are synced as regular tasks in Planner — the parent-child relationship is not preserved.
Planner Premium indent/outdent: Planner Premium supports indenting tasks to create sub-tasks. These relationships are not synced — indented sub-tasks are treated as independent tasks, the same as top-level tasks.
Cross-links
Cross-links create clickable URLs between synced Planner tasks and Jira issues, so you can quickly jump from one system to the other.
Enable cross-links in the field mapping step when setting up your sync.
Where the link appears — Jira side
You choose one of two modes:
Description — the Planner task URL is appended to the Jira issue description.
Custom field — the Planner task URL is written into a Jira custom field of your choice (text, textarea, or URL field types are supported).
Where the link appears — Planner side
The Jira issue URL is always added to the Planner task description (Planner does not support custom fields).
Notes
Cross-links are written once and are idempotent — if the link is already present, it won’t be duplicated.
If you enable cross-links on an existing sync, links will be added to all previously synced items on the next sync cycle.
✅ Once you’ve mapped the fields you need, click Next to review and launch your sync.
Last updated