Jira and Confluence integration on steroids: time-stamped static Jira data in Confluence, including traceability reports.

Jira is in constant move- your busy team is changing it each minute. What if you need to capture these blissful moments where the current state of the data matters?

This App provides a new Confluence macro, Jira snapshot. Use this macro to fetch Jira data into Confluence. The data is a copy of Jira data at the point of time, and remains unchanged even if Jira changes.

Open

Jira Snapshots generates tables of Jira data on the page

Is this App for me?

Jira Snapshots is indispensable for the following situations:

1. Transparency beyond the Jira silo (without increasing your Jira user tier): when not all stakeholders are on Jira, Jira Snapshots provide visibility to the software development team’s progress. With Jira Snapshots, all Confluence users see Jira data, even if they do not have a Jira license.

2. Finally, prepare for status meetings without exporting to excels from Jira. Jira snapshots captures Jira data at the time of reporting, and you’ll can come back to this snapshot anytime. Moreover- comparing the status now and a week ago becomes a breeze.

3. Using Jira Service Management? Jira Snapshots is an easy way to give customers visibility to the status of all their issues. You can control exactly the fields that exist in the snapshot, so its giving them all the data you need without overwhelming them.

4. Release documentation: from the list of known bugs to traceability reports. Jira snapshots allows you to capture Jira data at the time of each release. If you are using Xray, then Jira Snapshots (extended with Snapshots Traceability Extensions app)

5. For Xray Test Management for Jira users: Jira Snapshot (extended with Snapshots Traceability Extensions app) is a no-code way to configure test reports and traceability matrices.

6. Retrospectives: a one-click option to compare ambitions at the start of the sprint with reality at the end of the sprint.

7. Audit reports: Compare a predefined list of to-dos, with what was actually done. For example: demonstrate the quarterly performance of control tasks.

8. Any other situations where you need a reliable capture of how Jira is now.

Key features

1. Jira data is accessible to Confluence users who do not have Jira License: When a user retrieves a snapshot, Jira data is exported and stored in Confluence. This means that all users with view access to the Confluence page will see the complete data. This feature is often leveraged to promote more transparency across the organization. Many stakeholders that are not Jira users now have an easy window into what's going on.

2. Captures static Jira data: Jira snapshot tables are a static reflection of Jira data at a point of time. The macro configuration gives full control over the scope of the data and the columns of the table (Jira fields). Each time you get a snapshot, you create a baseline of this data. The timestamp is part of each snapshot.

3. Shows the hierarchy of Jira data. Like Epic→ Stories → subtasks: Jira data often has a hierarchical meaning. Either through the native constructs of Epic/Stories, or issue links. However you construct the hierarchy in Jira, you can expose it with a snapshot. Snapshots can be configured to retrieve Jira data along the hierarchical levels you defined. When the snapshot is exported from Jira, the app traverses through the levels and surfaces the relations in the snapshot table. In Jira Snapshots, the number of levels of hierarchy is not limited.

4. Supports Jira custom fields and Jira Service Management fields: Any custom fields that is defined in Jira, is picked up by Jira Snapshots and can be included in the snapshot capture. Including JSMs Request Type fields and SLA data. In the rare case that your Jira custom field is not formatted correctly in the snapshot- contact RadBees' support. We will quickly add support to the new custom field type.

5. Supports any JQL that your Jira supports: The scope of a snapshots is driven by JQL. If your Jira has an app that extends JQL, Jira Snapshots supports that too,

6. Find what changed in Jira over time: Need to see what changed in Jira? Jira Snapshots has an easy way to compare the most recent snapshot with the previous one. This is available right on the regular view. No need to jump through Confluence menus. The DIFF view is a time saver when reviewing Jira data. It helps users focus on the data that requires their attention.

7. Aligns with the Confluence page history: Jira Snapshots is designed from its core to be consistent with how Confluence pages work: The retrieval of a new snapshot, also triggers a new Confluence page version. A comment for this version indicates that this version was created by a snapshot. On Confluence's "page history" view, when viewing an old version of the page, you'll see the corresponding old snapshot table.

8. No data residency issues because snapshots are stored on Confluence. Jira Snapshots stores the Jira data as an attachment to the Confluence page. Hence, any data residency needs are solved on the Confluence level.

9. Integration with 3rd party apps, including XRay Test Management:

   1. XRay Test Management for Jira: Snapshots support the fields in the "Test" issue type. The app even supports the Test Run level. You can control which Test Runs are included in the Snapshots and the specific Test Run fields. Note regarding the Cloud version: XRay Test Management integration requires the installation of the extension app: Snapshots Traceability Extensions.

   2. ScriptRunner scripted field: Scripted fields integration is a particular feat of Cloud (where ScriptRunner scripted fields are not native Jira fields).

   3. Project Balm’s Risk Register specific fields

   4. Need support for additional 3rd party Apps? Contact us via our support.

Open

Jira snapshot with a 2 levels report