Example: Creating report on Jira issues

Common

In this article we will show how to create a report with the list of Jira issues.

Step 1: Adding Reporting Table View macro to a page

In the following step we will add and configure a Reporting Table View macro. This macro is used as a container for a single reporting data provider and one to many reporting table items. The data is retrieved according to the data provider parameters and then formed to a table according to the reporting table items parameters.

Open the macro browser, locate the Reporting Table View macro and place it to the page. The faster way is to open the Insert macro menu, enter the beginning of the macro name (all Reporting macro names start with ‘Reporting’) and click on the Reporting Table View macro.

 

The Reporting Table view macro will appear on the page. You may leave all the parameter values in default state. If you need to show some special text when no items are returned from the data provider, change the Empty response text content parameter value. If you need to show HTML instead of plain text, specify your html in the Empty response text content parameter and change the Empty response text output type parameter value to HTML. We will leave all parameters by default here.

 

After all parameters are set, close the macro parameters window.

 

Step 2: Adding Reporting Jira Data Provider to the Reporting Table View macro body

In the following report we will add and configure the Reporting Jira Data Provider. Reporting Jira Data Provider as well as Reporting Confluence Data Provider macros read data from the appropriate sources and provide it to the view macro. In this example we will add the Reporting Jira Data Provider macro for it to read the list of issues from the specified Jira.

Click on the Reporting Table View macro body to put the focus on it.

Open Insert macro menu, enter “Reporting” and click on Reporting Confluence Data Provider macro.

 

Ensure that the macro has been added into the Reporting Table View macro body. Otherwise drag and drop it there.

Specify the following parameter values:

  • Source = https://{yourSiteName}.atlassian.net/jira/
    • In the case of Cloud the URL of your favorite Jira should be specified.
    • In the case of Server/Datacenter you should specify the Application link name. If it is not specified, a primary link will be used.
    • In the case of Cloud you should also install CelesteCS Reporting for Confluence Cloud - Jira Integration plug-in on your favorite Jira instance. As Reporting operates on behalf of the current user, it needs to be acknowledged on the appropriate Jira instance – that’s the goal of the integration plug-in.
  • Query = project=REP ORDER BY id
    • This JQL query specifies all the issues of the REP project. “REP” is a project key.
    • Any other correct JQL query may be specified here.
  • Fields = Empty value (default)
    • This value may be left by default, as the standard set of fields, returned by the Jira Data Provider will be enough for this example.
  • Max results = 7
    • We are making a “Top 7 issues” report here, so we limit the number of issues being returned.
    • Max number cannot be higher than 1000 anyways.

  

Step 3: Adding Reporting Table Item macros to the Reporting Table View macro body

In the following step we will add and then configure the Reporting Table Item macros, which contain all the needed information about the report columns.

Reporting Table Item macro holds the parameters for a single reporting table column. You need to add one Reporting Table Item macro for each column, so for our 6-column report we will add 6 macros.

Click on the Reporting Table View macro body to put the focus on it. Open the Insert macro menu, enter “Reporting” and click on the Reporting Table Item macro.

 

Do it seven (not six!) times. One Reporting Table Item is an extra one, which will help us to configure a report. If the Reporting Table Item macro is added not to the Reporting Table View body, just drag and drop it there.

Note that the order of Reporting Table Item macros makes sense – the columns will be created in the same order.