14.1 Atlassian Jira Two-way Integration

Building a bridge between BAs, Dev, QA and UAT with EPC and Atlassian Jira.

Collaboration between business and development can be challenging, the EPC data sync manager breaks down that communication gap. Development and QA (jira users) lack visibility into the end-to-end process (epic) and understanding which requirements are associated with which task (story) depending on the path (scenario). As requirements / stories evolve during the development process business does have the transparency into the delivered product vs. the requested original requirement.

As business analysts map out the workflows, rules, roles and requirements, the EPC automatically creates and syncs the EPICs and related Stories within Jira. The story details include the full rich text formatting (tables, bullets, fonts) and associated images (screenshots & diagrams). As changes are made within either application, the other application is automatically updated with the most recent updates ensuring consistency on both ends. A URL and Jira Issue # is also automatically added so users can open the associated map or jira issue directly from the other application with ease.

• The creation of a process or tasks in EPC creates a corresponding epic or stories in Jira
• The creation of a story in Jira creates a corresponding document of type URL linked to Jira in EPC
• An update of an epic or story in Jira updates corresponding EPC objects
• An update of process or task in EPC updates corresponding epic or story in Jira