Creating JIRA Tasks from within Confluence Requirements Pages

One of the recent features delivered in zAgile Teamwork is the ability to create a JIRA Task from within a Confluence page and have the Task automatically inherit the context of the Requirement that is driving it.  The use case description below explains this 'context inheritance'.

This is also a great examples of the interoperability that can be achieved between heterogeneous applications (JIRA, Confluence in example but almost any app) using semantic technologies.  In this case, it is our zCALM semantic application server, that is enabling this seemingly simple scenario.

The use case is as follows:

1. Using one of the example semantic templates in Teamwork, you define a list of Requirements in a Confluence page 

2. Each Requirement on that page may be linked to one or many Design Goals that is the motivation for it, as well as a specific JIRA Project in which it is planned for delivery. 

Note: It is also possible to modify the template to associate all of the requirements on the page to a single project and map the individual requirement to a specific version. 

3. Once a certain number of requirements have been assigned to corresponding JIRA projects, you can use the Create Issue link to launch a JIRA Issue Creation page.  Assuming you also have a JIRA account and issue creation privilege for the project, you will notice a number of things:

1. The JIRA Issue Creation page is automatically associated with the project to which the Requirement was linked.
2. The issue is of type Task
3. The Issue Creation page is pre-filled with Summary and Description fields from the Requirement itself
4. The Issue Reporter is initialized to the person logged in
5. And more significantly, a custom field in JIRA showing links to "Related Requirements" has the originating requirement flagged. 

At this point, all you have to do after clicking on the Create Issue link is to press the Create button on the issue creation page.  The saved Task in JIRA will be automatically linked to the Requirement for which it was created.

And finally, the Requirements Document from where all this began will also automatically show the created JIRA Tasks,  their corresponding Requirements, status, etc.

A simple use case but a very powerful paradigm for Enterprise Application Interoperability.  All of this integration is driven by an underlying semantic infrastructure that maintains the relationship across the concepts that various tools represent.

You can Test-Drive this functionality in the sandbox for Teamwork.

-Sanjiva

PS - To test drive this feature, visit our sandbox

The screenshots below show the flow from Confluence Requirements Document page to JIRA Issue Creation page and back, reflecting the context that carries across the two applications automatically.

CAPTURE REQUIREMENTS AND ASSOCIATE WITH JIRA PROJECT(S)

 

AUTO-GENERATE PRE-FILLED JIRA ISSUE CREATION PAGE (WITH LINK TO INITIATING REQUIREMENT)

 

SAVE JIRA TASK (LINK TO INITIATING REQUIREMENT AUTOMATICALLY CAPTURED)

THE ORIGINATING REQUIREMENTS "DOCUMENT" IN CONFLUENCE AUTOMATICALLY UPDATES WITH NEWLY ASSIGNED TASKS

Comments

[Reddy]

hi,

i want to test this feature. kindly point me to the plug-in location available.

Thanks in advance.

[Sanjiva Nath]

Hi Reddy,

Thank you for your interest in zAgile Teamwork. you can try this capability in our sandbox here : http://zteamwork.zagile.org/confluence/display/TMPLSND/Semantic+Search+Requirements+Document+with+Issue+Creation

This demonstrates a simple Requirements document with line item requirements that may be mapped to a specific JIRA project and for each Requirement Item, a corresponding JIRA Task may be created. This feature is also available for initiating Requirement acceptance workflow as well as for Test Case execution (also in the sandbox).

-Sanjiva