ability to create Work Item Types other than Task

[o-o00o-o]

The one major thing preventing us from being able to use this extension is that we have a number of Custom Work Item Types setup in our Process in Azure Dev Ops and in many cases patterns that require creating work items other than tasks

We would love to switch to this extension as it seems much better than 1-click child tasks, so It would be great if

• we could indicate in the json the work item type for each child item.
• we could restrict what kind of work item types are allowed to have each profile. This would help our users to only be able to use profiles that were intended to be used on a Feature for Features and those for Bugs/PBIs

e.g. the following "example" profile would only be available when clicking on "Add tasks" on either a Bug or Product Backlog Item and it would create two standard child items, one Task and one Release Instruction (a custom Work Item Type that we have created in Azure Devops)

{
    "name": "example",
    "onlyFor": ["Bug","Product Backlog Item"]
    "tasks": [
        {
            "name": "Design Task",
            "type": "Task"
            "fields": [
                {
                    "name": "System.Title",
                    "value": "{System.Title} AF:{id}"
                },
                {
                    "name": "System.IterationPath",
                    "value": "{System.IterationPath}"
                },
                {
                    "name": "System.AreaPath",
                    "value": "{System.AreaPath}"
                },
                {
                    "name": "Microsoft.VSTS.Common.Priority",
                    "value": "{Microsoft.VSTS.Common.Priority}"
                },
                {
                    "name": "Microsoft.VSTS.Common.Activity",
                    "value": "Design"
                },
                {
                    "name": "Release has MDS",
                    "type": "Release Instruction",
                    "fields": [
                        {
                            "name": "System.Title",
                            "value": "{System.Title} AF:{id}"
                        }
                    ]
                }
            ]
        }
    ]
}

Perhaps the "tasks" node should be renamed for this as child items may no longer be tasks (perhaps "children" would be the appropriate term) and perhaps this could be combined with the idea from #12

[o-o00o-o]

Until we have this, we will unfortunately continue to need to rely on the 1-click child item extension

[mathieu-ferry]

would be great

[MTIE2022]

Any updates on this request? Would be nice to automaticly create Tasks of a custom type.

[MarkGTI]

I would like this too