Content Comparison

...

• By default, we display the title and description of the matrix. If you do not want to see them in the Confluence page, you can remove them with the toggle.

...

Sharing permissions of traceability matrices

Matrices need to be shared to the whole space to be displayed in the Report macro. If you have not made them public before hand, you can edit the permissions directly when selecting a matrix (c.f : Step 2.)

The regular way to edit the permissions of your matrices is in the Saved Matrices tab → Edit → And select either the “With view only permissions” or “With view and edit permissions” radio button.

...

🎉 Tada

...

Sharing permissions

Note that you can share your traceability matrices either :

. There are three types of permissions:

• View and edit permissions: to allow other users to update it using the “With view and edit permissions”see and update them.

• With view only permissions: to allow others to only see the result of your matrices without being able to update your template using “With view only permissions”. However other will be able to clone your matrices if they went to use yours as template.

...

• . By activating the toggle in the RY Report screen, you will put this permission on your matrix.

🎉 Tada

...

Use the report

Once the report is embedded and the page published, you can interact with the report like you would in the Traceability tab: Move/Add/Remove columns, click on requirement keys to show their details, etc..

Changes to the traceability matrix report made in the Confluence page are not saved and will be lost when you refresh the page, and are not viewable by your colleagues.

To make permanent changes to a traceability macro, go to the Saved queries tab, select the macro you wish to change, make your changes, and don’t forget to save.

Take it up a notch with the advanced options

Edit external properties

On macro creation, you can decide to allow users to edit the external properties directly in the Confluence page by checking “Enable the edition of external properties in the report macro”

...

• SYSTEM_PAGE_ID : will be replaced by the page where the report is inserted in

  • e.g. key ~ ‘BR%' AND page = ${SYSTEM_PAGE_ID} will show all the requirements having a key starting by “BR” and being defined in the page where the report is inserted in. key ~ 'BR%’ AND page = ${SYSTEM_PAGE_ID} key ~ 'BR%' and page = ${SYSTEM_PAGE_ID}

• SYSTEM_VARIANT_NAME and SYSTEM_VARIANT_ID :

  • e.g. key ~ ‘BR%' AND variant = '${SYSTEM_VARIANT_NAME}’ will show all the requirements having a key starting by “BR” and being in the variant of the current page where the report is inserted in.

• Status
  colour Blue title IN DEVELOPMENT

  SYSTEM_SPACE_KEY

  • e.g. key ~ ‘BR%' AND space = '${SYSTEM_SPACE_KEY}’ will show all the requirements having a key starting by “BR” and being in the space of the current page where the report is inserted in.

...