Integrated issue management with Jira

K platform offers you the flexibility to raise and manage data issues with integration to JIRA.

The benefits of the Jira integration include:

• Issues can be triaged by a Data Steward.

• Once an issues is confirmed to be a legitimate issue, the issue can be moved into Jira with a single click.

• As the Jira ticket is progressed through its lifecycle, updates are synced back to K in real time.

• Issues can also be imported into K where the issue was created first in Jira.

This page will walk through a workflow example of how to raise and link an issue to a Jira ticket.

Step 1) Business user raises an issue about a report

• Business user logs into K

• Business user search for the report they are having an issue with.

  • Alternatively the user can create an unlinked issue from the home page if they are not sure where the issue is.
    

    

• They go to the report profile and Add an issue by either clicking on the top right ADD button from the data profile page or clicking on the + icon from the Issues Tab

• The user populates the issue details

  • Issue title

  • Issue description

  • Status

  • Priority

  • Assignee

  • DQ Dimension

  • Linked asset

    • Note: If the issue has been created from a Data Profile page, the asset will be automatically linked. If the issue is created from the homepage or Issue Board it will be left blank.

      

Step 2) Data Steward reviews and links issue

• Once the issue is created, the relevant data steward will receive a notification.

• The data steward goes to the issue and reviews the issue and decides it is a legitimate issue that needs to be resolved by a Product / System team.

• The data steward clicks on the Action button
  

  

• Data Steward can choose to either:

  • Create a new Jira ticket and synchronise with K issue

  • Link to an existing Jira ticket. If an existing Jira ticket is linked, then the issue details will be over written with the existing external Jira ticket details.

  • When an issue is created/linked to a Jira ticket, a new section for the Jira ticket details is added to the Details tab

    

  • Properties that are now synchronised from Jira are locked

    • Title

    • Description

    • Priority

    • Status

    • Assignee

• As the Jira ticket is updated by the Product / System team, the Issue in K is also updated in real time
  

  

There are two scenarios where Data Stewards will not be notified of a new issue:

• Scenario 1: Data Asset does not have an assigned Data Steward therefore there is no Data Steward to notify

• Scenario 2: Issue has been created via Homepage or Issue Board and the user did not manually link a data asset and consequently, no Data Steward linked.

We recommend Creating an alert for new issues that will regularly send updates about newly raised issues that have not be assigned correctly and do not have a Data Steward tagged.