Default mapping configuration for SPW Jira Integrations
Learn about the default mapping configuration of Epic, Story, and Sprint work types between Strategic Planning and Jira.
Epic mapping configuration
Epic [sn_align_core_scrum_epic] in Strategic Planning is mapped to Epic in Jira. The field mapping between these two tables is as follows.
| Field in Strategic Planning | Field in Jira |
|---|---|
| approved_start_date | Start date |
| state | Status |
| short_description | Summary |
| approved_end_date | Due date |
Story mapping configuration
Story [rm_story] in Strategic Planning is mapped to Story in Jira. The field mapping between these two tables is as follows.
| Field in Strategic Planning | Field in Jira |
|---|---|
| assigned_to | Assignee |
| description | Description |
| iteration | Sprint |
| parent_work_item | Parent |
| priority | Priority |
| short_description | Summary |
| state | Status |
Sprint mapping configuration
Enterprise agile iteration [sn_apw_advanced_eap_iteration] in Strategic Planning is mapped to Sprint in Jira. The field mapping between these two tables is as follows.
| Field in Strategic Planning | Field in Jira |
|---|---|
| state | state |
| start_date | startDate |
| name | name |
| end_date | endDate |
Parent Topic:SPW Jira Integrations reference
Related topics
Review default mapping configuration for Jira projects in SPW