[Connect 2.5] Workstreams - Config

[maxceem]

When we are creating a new project with a Project Template which supports workstreams we have the next config at the moment:

{
  "workstreamsConfig": {

    // The list of possible workstreams which project may have depend on how the project creation wizard form has been filled
    "workstreams": [
      {
        "name": "Design Workstream",
        "type": "design"
      },
      {
        "name": "Development Workstream",
        "type": "development"
      },
      {
        "name": "QA Workstream",
        "type": "qa"
      },
      {
        "name": "Deployment Workstream",
        "type": "deployment"
      }
    ],

    // the field in the project data which is used to determine which workstreams to create
    "projectFieldName": "details.appDefinition.deliverables",

    // mapping between values of the field and workstreams types to create
    "workstreamTypesToProjectValues": {
      "development": [
        "dev-qa"
      ],
      "design": [
        "design"
      ],
      "deployment": [
        "deployment"
      ],
      "qa": [
        "dev-qa"
      ]
    }
  }
}

[maxceem]

Such a config let us create only workstreams so far, without works inside. Should we also support creating works inside like this?

{
  "workstreamsConfig": {

    // The list of possible workstreams which project may have depend on how the project creation wizard form has been filled
    "workstreams": [
      {
        "name": "Design Workstream",
        "type": "design",
        "works": [
            {
               "productKey": "development-iteration-5-milestones", 
               "id": 29, 
            }, 
               "productKey": "design-iteration-3-milestones",
               "id": 26
            }
         ]
      }
    ],
    // ... rest of config ...
}

[vikasrohit]

Such a config let us create only workstreams so far, without works inside. Should we also support creating works inside like this?

Not now. We would keep it simple for now.

[maxceem]

Ok. I'm closing this issues as we are not going to implement it for now.