Step-by-Step Jira–ServiceNow Integration Process for Agile Development in SPM

[tejenderk]

Hi ServiceNow Community,

I am excited to share a complete, step-by-step process guide for automating your Jira–ServiceNow (Agile 2.0 / SPM) integration. This automation is designed to eliminate manual tracking overhead for Project Managers by syncing data models seamlessly between both platforms.

### Key Automation Benefits:
* **Auto-Creation:** Generates shadow projects in ServiceNow instantly when created in Jira.
* **Hierarchical Alignment:** Automatically maps and links Epics, Stories, and Agile Phases across instances.
* **Optimized Tracking:** Automatically streamlines timecard generation and restricts tracking only to assigned project tasks.
* **Custom Flexibilities:** Alters standard business rules to support multiple active sprints and complex multi-assignment groups per project.

---

### 🔧 1. Prerequisites & Required Plugins
Ensure the following plugins are active in your instance (check `sys_plugins.LIST` if hidden):
* **PPM Standard:** `com.snc.financial_planning_pmo`
* **Agile Development 2.0:** `com.snc.sdlc.agile.2.0`
* **Jira Spoke:** `sn_jira_spoke`
* **External Authentication Framework:** `com.glide.external.app`
* **Atlassian Jira Integration for Agile Development:** `sn_agile_jira_int`

---

### 🚀 2. Integration & Flow Architecture Summary
The configuration workflow uses **Flow Designer** to manage data population delays and conditional error-handling:

* **Flow A (New Agile Groups & Settings):** Triggers on project creation, establishes default mapping configurations, creates a shadow Agile Team, and spins up automation records seamlessly.
* **Flow B & C (Epic and Story Mapping):** Monitors incoming `rm_epic` and `rm_story` tables, queries external string matches, and rewrites the Parent field definitions.
* **Flow D (Story Project Phase Updation):** Orchestrates conditional 2-minute processing windows to map stories directly onto respective Agile Phases derived from Jira Epics.

---

### 🛠️ 3. Core Technical Customizations
Included inside the complete attachment are custom code modifications made to address common OOB performance limitations:

* **Script Include (`TimeCardGenerator`):** Overridden to force restriction safeguards, ensuring timecards only autogenerate for active `pm_project_task` assignments rather than clogging workflows with `rm_story` logs.
* **Business Rule Overrides:** Disables default validations to explicitly let Jira-flagged items (`u_jira_project`) bypass single-sprint and unique assignment group constraints.

---

 📁 Step-by-Step Guide Attached!
I have attached the full comprehensive PDF guide containing 40+ pages of visual walkthroughs, Atlassian token setups, credential creations, Flow Designer screenshots, and complete Script Include source code for you to download.

I would love to hear your feedback or answer any architectural questions in the comments below!

Best regards,
Tejender

If you found this integration guide helpful, please Bookmark this post and give it a Helpful (Thumbs Up) vote! It helps others find this resource and motivates me to keep sharing.