Skip to main content
Skip table of contents

Freeze Jira Issue Statuses in Versions

Would you like to ensure that the statuses of your Jira issues remain unchanged in the saved versions of your Scroll Document? You can do this in combination with the third-party app Snapshots of Jira Data into Confluence, managed by the app vendor RadBee Ltd.

How to Freeze a Jira Issue in a Version

To freeze the status of a Jira issue in a Scroll Document version, you need to tell Scroll Documents to copy the Jira issue snapshot. This is done by specifying a special property key used by Snapshots of Jira Data into Confluence.

To learn how, follow the steps below.

  1. Capture a snapshot: Use Snapshots of Jira Data into Confluence to take a snapshot of your Jira issue(s) in the Working version of your document. This captures their current status and prevents them from changing when you create a new version of your Scroll Document. Learn how to do this in RadBee’s documentation: User guide

  2. Locate and specify the property key: Tell Scroll Documents to copy the Jira snapshot by specifying the property key radbee_snapshot_macro. You can learn how to do this here: Copy Properties When Saving Versions

  3. Save a version of your Scroll Document: This creates a copy of the pages in the Working version, including the Jira issue snapshot. To save a version, see: Save a Version

  4. Check your new version: Navigate to the page with the Jira snapshot within the saved version. The Jira issue in the new version will be "frozen" in its captured state, even if its status changes in Jira.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.