Configuring LQE with Jira's data sources

When IBM Jazz Reporting Service or IBM Engineering Lifecycle Optimization - Engineering Insights (ENI) are required, they need to be feed by IBM Lifecycle Query Engine (LQE) which in turn needs to be feed by Jira through two data sources. Jira's Change Management data source is responsible to inform all Jira issues that are created, updated or modified; this way LQE can feed IBM Engineering Lifecycle Management reporting tools with Jira data. Jira's Process data source is responsible to inform changes in Jira's projects structure in a way you can define rights access in LQE. If LQE is not installed, there is no way to get reporting services, try to install it before continue.

Having LQE installed:

  1. Follow the steps defined in this procedure to add Jira's Change Management data source in LQE using the following data:
    Field Value Required in Jazz Procedure Step
    Root Services URL Jira's root services URL (ask it to Jira's server administrator) 3
    Data Source URL http[s]://<host_name>:<port>[/jira]/rest/oslc/1.0/cm/trs 3
    Label TRS 2.0 for OSLC Connect for Jira CM Resources 4
    OAuth Consumer Key Jira's LDX consumer key (ask it to Jira's server administrator) 7
    OAuth Consumer Secret Jira's LDX consumer secret (ask it to Jira's server administrator) 7
  2. Repeat the same steps to register Jira's Process data source using following data:
    Field Value Required in Jazz Procedure Step
    Root Services URL Jira's root services URL (ask it to Jira's server administrator) 3
    Data Source URL http[s]://<host_name>:<port>[/jira]/rest/oslc/1.0/process/trs 3
    Label TRS 2.0 for OSLC Connect for Jira Process Resources 4
    OAuth Consumer Key Jira's LDX consumer key (ask it to Jira's server administrator) 7
    OAuth Consumer Secret Jira's LDX consumer secret (ask it to Jira's server administrator) 7
  3. Follow the steps defined in the Specifying user permissions procedure to make sure you define a user group to each Jira project listed below the TRS 2.0 for OSLC Connect for Jira Process Resources data group; otherwise IBM Report Builder and other reporting tools users won't be able to see data from those projects. If your company has not defined a policy for restricting access you can assign the built-in Everyone user group to them.