Multiple Downstream Work Item Types

Modified on Mon, 3 Mar at 5:00 PM

TABLE OF CONTENTS

Setup:
WI type-specific custom fields:

You may wish to track more than just one downstream work item type, e.g. Task and Issue:

Setup:

1) setup multiple types in risksheet.json so that you use comma separated list in "type" property

  "dataTypes": {
    "risk": {
      "type": "risk"
    },
    "task": {
      "type": "task,issue",
      "role": "mitigates",
      "name": "Task",
      "zoomColumn": "taskTitle"
    }
  },

2) add a column that shows the "type" column, i.e. the binging is set to DOWNSTREAMID.type

Note: please make the column readonly, you would still be able to set the type for new objects.

It is not possible to change type for existing objects.

      {
        "headerGroup":"Mitigations",
        "headerGroupCss":"headMitigations",
        "headerCss":"headMitigations",
        "header": "Type",
        "bindings": "task.type",
        "readOnly":true,
        "minWidth": 170		
      },

WI type-specific custom fields:

In addition, you may wish to show some extra columns that get value only from specific WI custom fields.
This is possible and works properly;
In case the field doesn't exist for a specific WI type, but you add some value in the column, the value will be stored in a 'string' field on Polarion.

There was an issue with handling multiEnum field if it was defined for a specific WI type only. That issue was fixed in the version 25.2.1
If you have issues with linking items that do not have a multiEnum field, make sure to update the Risksheet to that version or newer.

In case of questions, please contact us via support@nextedy.com