Connecting Opsera to Jira

Owned by Rajeswar Rajendran
Last updated: Aug 31, 2021 by Todd Barczak
4 min read

This tutorial will walk you through how to create and configure the Opsera JIRA Connect App in Opsera Platform and to have communication between JIRA and Opsera using Opsera pipeline workflow.

 

Tool Registry:
Below are the steps to save JIRA Tool Details and install JIRA Connect App using Opsera.

  1. Go to Tool Registry. Click on New Tool.

     

  2. Select Tool Identifier as 'Jira Issue Tracking' and enter Tool Name and Description. Click on Create Tool to create Tool Registry details.

     

  3. Go to Connection Tab and enter the JIRA credentials. Click on Create Jira API Configuration. Once the JIRA credentials are saved, click on Install Jira App to proceed with JIRA Connect App installation.

     

Pipeline :
Below are the steps to configure and trigger Opsera pipeline to test the Opsera JIRA Connect App functionality.

  1. Go to Pipelines. Select My Pipelines tab. Click on the Sample Jira Test Pipeline View button.

  2. Go to Workflow tab. Click on the notification(highlighted mail) icon against the Approval Step.

     

  3. Click on the JIRA Notifications button to enable adding notification configurations.
    Select the Jira Tool which was created in the Tool Registry.
    Select other mandatory fields (Jira Priority, Project, Board, Sprint, Primary & Secondary Approvers) under which the JIRA ticket will be created when the pipeline is triggered.
    Click on the cross icon next to each field in case the field needs to be cleared.
    Click on Save button to save the notification configuration details.
    Please note that only Primary and Secondary Approvers can see the Connect App related views and buttons (explained in later section).

     

  4. Click on Start Pipeline to trigger the pipeline.

     

  5. Once the pipeline execution reaches the Approval Step, a JIRA ticket will be created under the configured JIRA Project and Sprint.

     

  6. Go to JIRA ticket which got created. Click on the Approve/Reject Opsera Pipeline (highlighted icon) to open the Approve / Reject buttons.
    Only Users selected under Primary and Secondary Approvers will be able to view the Approve/Reject Buttons. Primary Approver will be the Assignee of the JIRA ticket and all Secondary Approvers will be added as JIRA Watchers.

     

  7. Click on Reject to stop the pipeline execution from proceeding.
    Click on Approve to proceed with the pipeline execution.

     

  8. Based on above step selection, the Jira ticket will be updated with appropriate status and the Opsera Pipeline will be approved/rejected and corresponding status will be updated against the pipeline. The App Button(View) will be hidden once the Approve/Reject button is clicked.


    The Pipeline status can be viewed in the Summary tab under the Pipeline Activity Logs. For the current pipeline run count since the execution was Rejected, the approval step status is marked as Rejected (Failed).



  9. The same JIRA ticket will be used for tracking any further execution of the above pipeline step (Approval Step) for the configured JIRA Project and Sprint. Jira ticket will be updated with comments for every pipeline run count and the approve/reject actions.