Executing JIRA Workflow Tasks from within Confluence using Teamwork 3

Teamwork 3 provides much tighter integration of Confluence with JIRA Workflows using the JIRA XMLRPC API using the zAgile Teamwork plugin for JIRA.   So it is now possible to initiate and interact with JIRA Workflow-based tasks from within Confluence pages and tables.  

However, beyond this user-friendly interaction, the tasks and their states are also automatically linked with the specific entity (Requirement, Test Case, Document, Business Request, Invoice, etc.) in Confluence from where they are initiated (see example below).  

The two-way linking can now provide the users with a friendly interaction with JIRA while achieving full traceability and reporting.  Users  don't need to access JIRA unless they need to edit/update task details.  Since the integration is done using zAgile's zCALM Server, the information may be accessed anywhere in Confluence or JIRA.   For example, you can query the Review Status of a Specific Document or Requirement, or the Test Execution Status of a Test Case using simple queries in the context of the Document, Requirement or Test Case, without having to go to its corresponding JIRA Task.

 

And of course, all of this is highly configurable, since it is accomplished using templates and macros provided with Teamwork.  Visit the Teamwork sandbox to check out this and other features of Teamwork 3.  

Here is how it works:

The screenshot below shows a couple of sample Requirements for Feature (Smart Search) in Confluence.  Each Requirement may have associated Component(s), Stakeholder(s) as well as Review and Development Tasks.  Review Task here is tied to an Approval Workflow in JIRA.  The same can be done for Implementation Tasks.

Product Managers or Business Analysts defining these Requirements above can "Initiate" Review Sessions, and register the resulting outcome (Approved/Deferred, etc.) with the Requirement.  Clicking on the "Initiate Review" Button against the Requirement 2 above will result in the automatic creation of a JIRA Task for Requirement Approval and return the Task link along with its possible next states as shown below.

 

From here, it is possible to take next actions against the Task, without interacting directly with JIRA.