0
1.0.0
Zurich Patch 4, Yokohama Patch 9
- Achieve end-to-end visibility in SPM from strategy to execution with the SPW Jira Integrations. This integration synchs the following data:
- Bi‑directional sync for Epics, Features, Capabilities, and Stories
- Sprints sync one‑way from EAP → Jira and must be created in EAP
- Sprint status updates flow back; creation still originates in EAP by design
- Simplify setup of this integration with guided steps using play books and flexible mappings for tables, fields, and choice values for each Jira project(space).
- Diagnose any issues with inbuilt Diagnostics tool
- Achieve end-to-end visibility in SPM from strategy to execution with the SPW Jira Integrations. This integration synchs the following data:
- Bi‑directional sync for Epics, Features, Capabilities, and Stories
- Sprints sync one‑way from EAP → Jira and must be created in EAP
- Sprint status updates flow back; creation still originates in EAP by design
- Simplify setup of this integration with guided steps using play books and flexible mappings for tables, fields, and choice values for each Jira project(space).
- Diagnose any issues with inbuilt Diagnostics tool
- Achieve end-to-end visibility in SPM from strategy to execution with the SPW Jira Integrations. This integration syncs the following data:
- Bi‑directional sync for Epics, Features, Capabilities, and Stories
- Sprints sync one‑way from EAP to Jira and must be created in EAP
- Sprint status updates flow back from Jira; creation still originates in EAP by design
- Simplify setup of this integration with guided steps using playbooks and flexible mappings for tables, fields, and choice values for each Jira project (space).
- Diagnose any issues with inbuilt Diagnostics tool
- Required plugins and products: SPW Jira integrations
- Dependencies : Strategic Planning (sn_align_ws), Atlassian Jira Integration for Agile Development(sn_agile_jira_int)