Skip to main content
Kinetic Community

Jira Adapter

Overview

The Jira Adapter is an adapter that is installed into Kinetic Bridgehub that allows access to data contained in a Jira instance.

Installation

Note: Check to ensure that this adapter isn't already installed into your bridgehub as part of the base installation before undertaking the installation tasks.

  • Download the kinetic-bridges-adapter-jira.jar file and it's dependencies here
  • Put all of the downloaded files into the WEB-INF/lib folder for you kinetic-bridgehub installation
  • Restart the tomcat that your kinetic-bridgehub installation is located in

Setup

Configuration Values

Name Description
Username Jira login id
Password Jira username
Base Site The Url or IP Address of the Jira instance

Example Configuration

Name Value
Username user
Password secret-password
Base Site https://localhost:8080

Structures, Fields, and Queries

Structures

  • Group
  • Issue
  • Project
  • User

Fields

  • Group
    • name, html
  • Project
    • id, key, name
  • User
    • key, name, emailAddress, displayName, active, timeZone
  • Issue
    • The issue structure is unique because many of the possible fields are returned as JSON objects that contain more information about the field. For example, when returning the progress field, it returns as {"progress" : 0, "total" : 0}. This bridge supports returning fields that are buried in these JSON objects as well as having the possibility to return the whole JSON object. To return one of these sub-fields, just separate the field names with a period. For example, it you wanted to return the total progress of an issue, you would input progress.total as a field to return. As long as correct capitalization is used, this will work for getting through multiple levels of JSON. Useful second levels of JSON values are indented under the initial value in this list.
    • Single fields

      • id, key, summary, resolutiondate, timespent, updated, created, description, environment, timeestimate, lastViewed

    • Complex fields (2 fields with the same parent, parentField.subfield1 and parentField.subfield2 would be displayed in the form of parentField : subfield1, subfield2.)

      • progress: progress, total

      • issuetype: id, description, name, subtask

      • resolution: id, description, name

      • fixVersions: id, description, name

      • creator: name, emailAddress, displayName​

      • reporter: name, emailAddress, displayName

      • watches: watchCount

      • status: description, name, id

      • status.statusCategory: id, key, colorName, name

      • project: id, key, name

Queries

  • Group
    • groupname
    • expand
      • List of fields to expand. Currently only available expand is "users".
  • Project​
    • No parameters can be passed. Either retrieve a singular project based on the Id/Key or return all of the projects.
  • User
    • username
      • finds matching users to any part of the query string value found in the username, name, or e-mail address of a user.
  • Issue
    • All the returnable possible returnable fields can be used to narrow down the issue search. The query that should be passed is a JQL Query, and more specifics can be found here.