Adding the Jira Snapshots Macro to a Confluence Page
Navigate to the page and click the Edit icon, or just type E to open the editor. (Alternatively, you can create a new page.)
In the Confluence editor, click the '+' icon and choose View more from the drop down menu.
Find the item to be inserted and select it.
Click Insert.
Configure the macro and Save. Further down on this page you’ll find more information about configuration.
You can also type '/' (forward slash symbol) while editing the page, to bring up the same list you'd see by in the View more menu.
Publishing and Generating the First Snapshot
Once the macro is configured, continue editing the rest of of the page, and click Publish when finished.
After the page is published, click Update to generate the first snapshot.
What are Levels?
By default, each Jira snapshot report includes a “Level 1.” This is a list of Jira issues retrieved using a JQL clause.
Sometimes you’ll need to include other issues, which are dependent or related to the issues in Level 1. These will be retrieved by adding a Level 2 to the report.
Examples of Level 1 - Level 2 issues:
Epics and their stories
Issues and their subtasks
Stories and their related bugs
Issues and their “blocker” issues
Jira Snapshots supports additional levels; you could go as far as three or four levels, if needed.
Parameters (for Each Level)
Parameters are options that you can set to control the content or format of the macro output.
JQL is Jira Query Language. This is the native query language for Jira, and these macros use it directly when retrieving data from Jira.
New to JQL? We have put here Jira JQL cheat sheet some information to help you get started
Parameter name | Required | Default | Parameter description and accepted values |
|---|---|---|---|
Level title | No | Empty | A title for this level will be displayed above the column titles. |
Search JQL | Yes | - | In Level 1: Any valid JQL, applicable for the Jira from which the snapshot data is retrieved. This may include any JQL extensions by apps, as long as they are valid inside that Jira instance.
In Level 2 (or higher): The JQL clause for Level 2 needs to include a reference to Level 1, in order to achieve the dependency/cascading effect. Therefore, the search clause must reference fields in the previous level. For example:
|
Add fields to display | Yes | Key, Summary | The list of Jira fields to display. Use the widget just below the field to drag and reorganize the order of the columns in the level.
|
It's a good practice to test the JQL first in Jira. Refer to the Jira manual for more information: Key Features
Any legitimate JQL clause can be used to retrieve data from Jira.
The list of columns is configurable.
Retrieving fresh data from Jira into Confluence is done from Page View mode, by clicking Update.
Each time fresh data is imported, a new Confluence page version is generated. This can be seen in the Page History view.
The DIFF tool enables you to compare the current Jira data with any previous snapshot.
A single Confluence page may include multiple instance of snapshot macros, each retrieving a different set of data.
Known Limitations
The snapshot macros cannot retrieve files (ie- images) from Jira. So, if a 'description' field contain a screenshot image, this image will not be included in the Confluence data. Note: You might still see this image ij Confluence if it is cached in your browser, but this is just a coincidence. The image will no longer display if you clear you browser cache.
Jira fields may have many different formats, and some Apps may even have their own custom field types with their special formats. This may lead to situations that some fields do not display correctly. Please contact RadBee if you run into this situation: and we'll try to adjust.