Cloud Services

DevOps Intelligence

Atlassian Jira configuration
Published On Jun 05, 2024 - 11:21 AM

Atlassian Jira configuration

DevOps Intelligence supports your use of Jira. For DevOps Intelligence to pull data from Jira, you must configure a Jira account.
Jira Software is part of a family of products designed to help teams of all types manage work. Originally, Jira was designed as a bug and issue tracker. But today, Jira has evolved into a powerful work management tool for all kinds of use cases, from requirements and test case management to agile software development.
To configure a Jira connection you will need to have access rights and follow the configuration listed below:
Access Rights
: The account should have read rights (Browse projects) on the projects we intend to sync.
The DevOps Intelligence requires the following fields to be selected for account addition:
  • Connections Name
    : peer connection name. This could be any string and is used only for reference.
  • Host
    : Jira Host.
  • Auth Type
    : This refers to the authentication to be used for a given Jira client. It presents values as
    token
    or
    oauth.token
    , where
    token
    can be used for API token-based authentication and
    oauth
    can be used for OAuth based Authentication.
For adding a Jira connection:
  1. Navigate to the top left overflow menu and select
    Admin
    .
  2. Select
    IAM
    and then
    Connections
    .
  3. Select the
    +Add New
    button. Then  Add Connection.
In addition to common fields, the following fields are necessary for basic password-based authentication. Jira Cloud does not allow basic authentication, hence it is only available for On-Premise Jira Server.
  • Username
    : Username for Jira. Generally, the email ID with which you logged in to Jira.
  • Password
    : Password for Jira. Generally, the password with which you logged in to Jira.
  • Proxy ID
    : UUID for Proxy Adapter. Please follow the steps given in (https://pages.github.kyndryl.net/multicloud/mcmp-devops-architecture/onpremtool) to get Proxy Adapter connected to On-Premise Jira.
For API token-based authentication, the following authentication fields are required in addition to common fields:
  • User:
    Username for Jira. This is generally the email ID with which you logged in to Jira.
  • Username:
    Username for Jira. This is generally the email ID with which you logged in to Jira.
  • APIKey:
    Personal access token.
For OAuth based Authentication, provide the required information as follows:
  • ConsumerKey
    : Provided on Jira Application Link Page
  • PrivateKey
    : Refers to the Private key (.pem format) of Public key generated while configuring Jira Application Link Page
  • Secret
    : This is generated after User confirmation from a Dialog box
  • AccessToken
    : This is a value generated using Secret

Configuration

The user needs to select the Project that needs to be tracked through the DevOps Intelligence and its respective Components. Then, tracking can be done at two levels:
  • Project Level
    : This will track all the entities of a given project if no components selected
  • Components Level
    : This will track issues only for those selected Components

Project Level tracking

For this type of tracking, certain selections have to be made in the system, as follows:
  • Tool engine
    : Jira
  • Technical service name
    : It could be any string and is used only for reference.
  • Project
    : Here, the user must select
    Project
    Name from the dropdown. The already configured project will be omitted from the list.
  • Component
    : At project-level tracking, this field should be empty.
The following is an image of the Project Level Tracking configuration screen:

Component Level Tracking

For this type of tracking, certain selections have to be made in the system, as follows:
  • Tool engine
    : Jira
  • Technical service name
    : It could be any string and is used only for reference.
  • Project
    : Here, the user must select
    Project
    Name from the dropdown. The already configured project will be omitted from the list.
  • Component
    : At project-level tracking, this field should be empty.
APIKey:
Personal access token, generated from the following menu selection: your profile and settings → personal settings → app passwords. If the configuration is successful, then a window will appear that shows a table with the configuration details.
The Sync Feature scans current data for visibility after configuring credentials at periodic intervals. The intervals are set as follows:
  • The account Sync Interval is set to 5 mins: Refresh current data
  • The account Delete Interval is set to 7 mins: All deleted accounts updated
  • The history pulled Interval is set to 180 days: Data history
For more details, see your Delivery representative.
Do you have two minutes for a quick survey?
Take Survey