Skip to main content
Skip table of contents

Update Jira links

Update Jira links in batch:

  • At the end of a baseline, it is possible to update all Jira issues to the next baseline,

  • When there are similar requirements in several spaces, it is now possible to redirect all Jira issues form one space to another,

  • When a space is migrated to another Confluence instance, it is now possible to redirect all Jira issues to the new instance (per space).

Scenario:

  • You have created a baseline 1 from a set of requirements.

  • Then, you used our Jira bulk creation to create Jira work items, which are linked to the requirements in baseline 1.

  • Now, you have created a baseline 2 and want to link those existing Jira work items to the new baseline — without creating new Jira items.

  1. In Requirements sidebar

  2. Click into the search page

  3. Search for the requirements you want to update links from

  4. Click search

  5. Select 1, few or all and click

  6. Actions

  7. Click on the new menu Update Jira links

ℹ️ This feature is compatible with "Show Baselines", but not with "Cross-space".

image-20250619-075908.png

The feature allows you to batch-update Jira links from selected requirements

  1. We automatically add Jira is not null to the query, since only requirements already linked to Jira are relevant

  2. Enter the new baseline number (e.g., 2)

  3. Click Update Jira links button

PS: If you select more than 10 requirements, only 10 will be shown, but all selected will be updated

image-20250619-083503.png

image-20250619-132028.png

A DONE status means data was sent to Jira — but Jira processing could still fail afterward.

To look for details, click See queue to get redirected in the other queue messages and see how it goes

image-20250619-084330.png

We provide the reason of the failure

Double-check that the target requirements exist, or adjust your input in the previous screen.


  • The space key cannot be empty,

  • The baseline must be a valid number (the baseline ID, not the name) or empty (current requirements)

  • If a requirement doesn’t exist in the target location, a warning will be shown, but others will be updated,

  • If none of the target requirements exist, the process will fail,

  • You can update Jira links across spaces, as done in Scenario 1 but changing the Space key instead (e.g., from SPACE1 to SPACE2)

    • Example: When using Scroll versions, you can update Jira links in the newly created space

  • It’s also possible to update space key and baseline simultaneously

If you need to change the Confluence applink, add this to the URL:

CODE
&applink=true

⚠️ No validation is performed on the target requirement when changing the applink — use at your own risk.

JavaScript errors detected

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

If this problem persists, please contact our support.