Configure Down-stream traceability columns (tasks, risk control measures)

Modified on Tue, 20 Jun 2023 at 11:01 AM

{
      "headerGroup": "Risk Control",
      "headerGroupCss": "headMitigations",
      "headerCss": "headMitigations",
      "header": "Risk Control",
      "bindings": "task.title",
      "id": "taskTitle",
      "minWidth": 170
    },

 "dataTypes": {
    "risk": {
      "type": "risk"
    },
    "task": {
      "type": "riskControl",
      "role": "mitigates",
      "name": "Risk Mit. Measure",
      "zoomColumn": "taskTitle"
    }
  },

As you can read in the What Work Items are visible on the Risksheet the risksheet can show the downstream traceability data.

By default, the mitigations section shows the tasks linked to the risk items.

Config file

Please follow this article, to learn where is the configuration file located, see: Configure risksheet columns

Configuration

The downstream objects are defined in the section:

 "dataTypes": {
    "risk": {
      "type": "risk"
    },
    "task": {
      "type": "riskControl",
      "role": "mitigates",
      "name": "Risk Mit. Measure",
      "zoomColumn": "taskTitle"
    }
  },

Then have one column that defines "taskLink" (the type should be called differently as this can be anything else, not just task.

    {
      "headerGroup": "Risk Control",
      "headerGroupCss": "headMitigations",
      "headerCss": "headMitigations",
      "header": "RC ID",
      "type": "taskLink",
      "id": "task"
    },

Important: the ID of this column is important, as you will refer to it, when adding more columns:

{
      "headerGroup": "Risk Control",
      "headerGroupCss": "headMitigations",
      "headerCss": "headMitigations",
      "header": "Risk Control",
      "bindings": "task.title",
      "id": "taskTitle",
      "minWidth": 170
    },

You see above, that the bindings use the dot notation to refer to properties of task work item, where "task" is the id of taskLink column ID.

Where to load data from?

There are additional options to be used :

1) Query

You can specify the base query (this can be combined with all other options)

    ...
      "task": {
        ...
        "query":"status:released"
      }
   ...

2) Document and/or Project

In addition to Query, or without a query, you can specify from what live document the items shall be loaded. The project can be from current document or in another specified project. Or you can omit the document, and use just project to load it from other project.

....
      "task": {
      ....
        "document":"Risks/harms" ,
        "project":"med_library",
        "query":"status:released"
      }
...

NEW!

From version 23.7.0 having multiple target projects for tasks is supported.

...
        "task": {
      ...
          "projects":"fmea_22_2,drivepilot"

Where to create new items

Create new object in current document

By default the new items are created in the same place where they are loaded from (see above). You can force the system to create a new items in current "risksheet" document using "createInCurrentDocument":true