Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. To set the synchronization scope, select an appropriate Project and Space.
    It's important to note that each a Space can only be used once utilised in a Workflow & Fields configurationsyncroniser just once. However, a single Project can be utilized used in multiple configurations..

  2. Next, select one of the three options in the Pages field:

    • All: This option automatically creates a Jira issue and pairs it with all pages within space, both old and new.

    • Selected manually: Users will need to manually trigger the page sync with a new Jira issue.

    • Label-based: Only pages with specifically defined labels will be synced.

  3. An Additional CQL field offers an option to narrow down the scope of the synced pages based on a CQL query.
    For example, in the screenshot above the field has a CQL query ‘type = blogpost’. That means that every page in ITKB space that is a blogpost will be synced with a Jira issue. Pages that do not match the CQL query condition will not be synced.

  4. When selecting an option in the Issue Type field, you are specifying the type of Jira issue that will be generated following the synchronization with your Confluence page.

    • When using the ‘Selected pages’ sync mode, users can opt for the 'Define per page' option, which allows them to choose the issue type while manually syncing the page with Jira.

  5. The Jira User field provides a selection of Jira users who can act as technical users for specific actions when chosen. A user with technical permissions can perform various tasks such as:

    • creating issues

    • editing issues

    • transitioning workflows

...