Create Child Work Items
Overview • What's New? • How-To • Filter Examples • Troubleshooting • FAQ • Security • Changelog • Support • Credits
Overview
Every parent work item needs the same set of children — and someone has to create them by hand, one field at a time, every single time.
Create Child Work Items eliminates that. Define the children you want once as Azure DevOps team templates, then create the whole set — correctly typed, pre-populated, and linked to the parent — from a single menu action on the work item form, backlog, or board. Select several parents in a backlog and it works through all of them in one pass, with live progress you can cancel.
Common uses: standing up a definition-of-done checklist on every story, breaking features into consistent delivery steps, or generating the same triage and verification items on every bug.
👋 Coming from 1‑Click Child‑Links? This extension is its actively maintained evolution — your existing team templates and filter rules work as-is, with nothing to recreate or reconfigure. See Compatibility for the two-step switch.

Key Features
- One click, many children. Create a full set of child work items from a parent in a single action, each linked into the parent hierarchy automatically.
- Bulk creation. Select multiple parents in a backlog and run once — with live progress and a cancel button for long runs.
- Any child type your process allows. Tasks, Bugs, Features, and custom types, based on your backlog levels.
- Templates you already have. Uses native Azure DevOps team templates — no separate configuration store, nothing new for teams to learn.
- Precise matching. Decide when each template applies with simple or advanced filters on type, state, board column and lane, title wildcards, tags, area, and iteration.
- Reuse parent values. Inherit or compose field values with dynamic field values and special tokens, or insert just part of a parent value.
- Works within your permissions. Runs under your Azure DevOps user context and never asks for personal access tokens or passwords.
Compatibility
Azure DevOps: Works with Azure DevOps Services (cloud) and Azure DevOps Server 2020 Update 2 or later. Not compatible with Azure DevOps Server 2019 or any earlier TFS versions — for those, use the 1‑Click Child‑Links extension.
Migrating from 1‑Click Child‑Links: Disable or uninstall 1‑Click Child‑Links, then install this extension. Your existing team templates and filter rules keep working unchanged — there is nothing to recreate or reconfigure.
Formerly "Create Child Tasks": Same extension, same templates, same functionality — renamed to reflect that it creates child work items of any type, not just Tasks.
↑ Back to top
What's New?
Latest — 1.5.0, released 2026-10-30. Child work items can now pick up just part of a parent field value, like the feature name from a parent's title or just the person's name from Assigned To. We also gave the Terms of Use a little love, because fine print has feelings too.
Recent releases:
- 1.4.2 · 2026-08-14 — Renamed the extension to Create Child Work Items and added an organization-level admin page.
- 1.4.1 · 2026-07-19 — Fixed child type resolution for Basic process projects without a Requirement backlog level.
- 1.4.0 · 2026-06-28 — Added Terms of Use, Privacy Policy, and Security documentation.
See the full details in the Changelog.
↑ Back to top
How-To Guide
How-To Shortcuts
Quick Start
- Install: Install the extension at your Azure DevOps organization. Once installed, it is available to all projects in that organization / collection.
- Define Templates: Define one or more Templates for your team (Project Settings → Boards → Team Configuration → Templates).
- Create Child Work Items: Open a parent work item (User Story / PBI / Bug) and choose "Create child work items" from the toolbar, or from the parent's menu on a backlog or board — child work items will be created from matching templates.
Defining Work Item Templates
Create work item Templates via Project Settings → Boards → Team Configuration → Templates.
Templates have two parts: how they match, and what they set. Use filters (in the template Description) to control when a template applies to a parent work item, and set field values (in the template fields) to define what values the created child work item receives.

Ordering
By default, child work items are created in alphabetical order based on the Template Name. To control the creation order, prefix template names with numbers (for example, 01-, 02-).

The child work items will be created in the same alphabetical order of the Template Name fields. Keep in mind that the title of the child work item comes from the System.Title field in the work item template – it is not derived from the Template Name. See Setting Field Values.

Creating Filter Rules
The template's Description is used for filtering rules. Two formats are supported:
- Simple Filter – Square-bracket list of parent work item types. Example:
[Product Backlog Item, Bug]
- Advanced Filter – JSON with an
applywhen array (see below)

Simple Filter (Square Brackets)
Place a square bracketed list of parent types in the template Description. This will apply the template for those parent types.
[Product Backlog Item, Bug]
Advanced Filter (JSON)
Put a JSON object containing an applywhen array into the template Description. Each entry in applywhen is evaluated as OR; fields inside an entry are combined as AND. You can paste the examples as they're shown. Azure DevOps removes the line breaks when it saves the Description.
Example
{
"applywhen": [
{
"System.WorkItemType": "Product Backlog Item",
"System.State": [ "New", "Approved" ],
"System.BoardColumn": "Development",
"System.BoardLane": "Expedite",
"System.Title": "*Mobile*",
"System.Tags": [ "Tag1", "Tag2" ],
"System.AreaPath": "Project\\Area 1",
"System.IterationPath": "Project\\Iteration\\Sprint 1"
}
]
}
The above JSON filter rule will match any parent work item when: (WorkItemType = "Product Backlog Item") AND (State = "New" OR "Approved") AND (BoardColumn = "Development")...
See the Filter Examples section below for a more extensive set of filter examples.
Supported Filter Fields
System.WorkItemType (Work Item Type)
System.State (State)
System.BoardColumn (Board Column)
System.BoardLane (Board Lane)
System.Title (Title)
System.Tags (Tags)
System.AreaPath (Area Path)
System.IterationPath (Iteration Path)
Notes
- Matching is case-insensitive:
"active" matches Active.
- A list of values matches any one of them. Tags are the exception: the parent must have every listed tag.
- Title takes one value: the exact title, or a pattern with
* wildcards. See Wildcards for Title.
- Area and iteration paths must be the full path. In JSON, escape each backslash, as in
"Project\\Area 1".
- Several
applywhen entries combine as OR: the template applies if any entry matches.
- To match either of two tags, or one of several titles, add a separate
applywhen entry for each.
Wildcards for Title
You might want to apply child work items to a parent work item if the parent work item title matches exactly or only partially. It's possible to match the parent work item title by using a wildcard filter rule which uses the asterisk character (*).
{
"applywhen": [
{
"System.WorkItemType": "Product Backlog Item",
"System.Title": "*WildcardString*"
}]
}
The following are examples of how the wildcard matching can be used:
- "a*b" Everything that starts with "a" and ends with "b"
- "a*" Everything that starts with "a"
- "*b" Everything that ends with "b"
- "*a*" Everything that has an "a" in it
- "*a*b*" Everything that has an "a" in it, followed by anything, followed by a "b", followed by anything
Note: Wildcard filter rules currently only work for the System.Title field.
Setting Field Values
Templates can set field values on the child work item when it is created in the following ways:
- Static Values – Set explicit field values in the template to apply fixed values on the child.
- Dynamic Parent Field Values – Inherit parent values or compose strings with tokens.
- Special Tokens – Resolve runtime values like the current user (
@me) or current iteration (@currentiteration).
If the template doesn't set System.Title, System.AreaPath or System.IterationPath, the child copies the parent's value. The child's title always comes from System.Title, never from the template's name.

Dynamic Parent Field Values
In addition to simple constant values, child templates can dynamically pull values from the parent work item when the child is created.
There are three complementary methods:
- Field Tokens – Copy a parent field into a string field on the child using
{FieldName} syntax.
- Part of a Field – Insert just part of a parent field, using a token with
before, after or between.
- Blank Values – Inherit a parent field value for any field type by leaving the template field value empty.
Using field tokens in string fields
You can include tokens in any string field defined on the template (for example, System.Title, System.Description, or custom string fields).
- Syntax:
{System.Title}, {System.Description}, {Custom.MyTextField}
- Always use the field reference name in tokens, not the display name.
- You can combine plain text and one or more tokens in the same value (for example,
Dev Task: {System.Title} [{System.State}]).
- The token text itself is case-sensitive and must match the field reference name exactly (for example,
System.Title, not system.title).
- Braces only form a token when they contain a field reference name: letters, numbers,
_ or -, with at least one period (for example, System.Title or Custom.MyTextField). Any other text in braces, such as {TBD}, code or JSON, is left exactly as you wrote it.
- Text in double braces, such as
{{ item.name }} or ${{ secrets.TOKEN }}, is never treated as a token.
- A token that's missing its period, such as
{Title} instead of {System.Title}, appears in the child exactly as typed. On a number, date or identity field, that child work item won't be created and the console logs an error.
Some common and popular field tokens:
System.Title
System.Description
System.AreaPath
System.IterationPath
System.AssignedTo
System.Tags
For a complete list of available work item fields and their reference names, see the official Microsoft documentation: Work item field reference.
Examples
- Child title that prefixes the parent title:
- Template field
System.Title = Dev Task: {System.Title}
- Child title that uses multiple tokens:
- Template field
System.Title = Dev Task: {System.Title} [{System.State}]
- Child description that copies the parent acceptance criteria:
- Template field
System.Description = {Microsoft.VSTS.Common.AcceptanceCriteria}
[Deprecated] Using field tokens in 'non-string' fields: Using {FieldName} tokens for non-string fields (e.g. integer, boolean, date, or complex identity objects) is considered an advanced, unsupported scenario and is now deprecated. For the time being, the extension will still attempt to send such values, but if used incorrectly, it will log an error and the work item won't be created. The recommended pattern for non-string fields is to use blank-value inheritance.
Using part of a parent field value
To insert only part of a parent field's value, add a transform to the token: write it after the field's reference name, separated by a colon, as in {System.Title:before(": ")}.
before("text") – Everything before the first text
after("text") – Everything after the first text
between("start", "end") – Everything between the first start and the next end after it
Example: part of a title
A plain {System.Title} token inserts the whole title. A transform inserts just part of it. With the parent titled Mobile: Login page - Phase 2:
| Token |
Inserts |
{System.Title} |
Mobile: Login page - Phase 2 |
{System.Title:before(": ")} |
Mobile |
{System.Title:after(" - ")} |
Phase 2 |
{System.Title:between(": ", " - ")} |
Login page |
- Template field
System.Title = Test {System.Title:between(": ", " - ")} → child title Test Login page
- Template field
System.Title = {System.Title:before(": ")} release notes → child title Mobile release notes
Example: a person's name from Assigned To
A plain {System.AssignedTo} token inserts the person's name followed by their sign-in address, usually their email, in angle brackets. A transform inserts just one of the two. With the parent assigned to Jane Doe:
| Token |
Inserts |
{System.AssignedTo} |
Jane Doe <jane@contoso.com> |
{System.AssignedTo:before(" <")} |
Jane Doe |
{System.AssignedTo:between("<", ">")} |
jane@contoso.com |
- Template field
System.Title = Review with {System.AssignedTo:before(" <")} → child title Review with Jane Doe
Example: the date from a date and time field
A plain {System.CreatedDate} token inserts the date and time together, in UTC. A transform inserts just the part you need. With a parent created on 18 February 2026 at 16:36 UTC:
| Token |
Inserts |
{System.CreatedDate} |
2026-02-18T16:36:09.693Z |
{System.CreatedDate:before("T")} |
2026-02-18 |
{System.CreatedDate:before("-")} |
2026 |
- Template field
System.Title = Review, raised {System.CreatedDate:before("T")} → child title Review, raised 2026-02-18
Dates are inserted in UTC. Azure DevOps shows them in the time zone from your profile, so the inserted date can differ by a day from the one you see on the work item.
Rules
- The search text matches regardless of case (
"phase " finds Phase ), and the inserted text keeps the parent's original casing. The first occurrence is used.
- If the search text isn't found in a parent's value, the whole value is inserted instead.
- Put each piece of search text in straight double quotes. To include a double quote or a backslash in it, write
\" or \\. For example, {System.AreaPath:after("\\")} inserts the part of an area path after the first backslash.
- Search text can't contain
{ or }.
- Transforms work the same way in rich-text fields such as Description as in plain-text fields such as Title.
- Transforms work on any parent field, using the same text a plain token would insert, as in the Assigned To and date examples above.
- If a transform is written incorrectly, such as a misspelt function name (
betwen), the wrong number of search texts or a missing quote, the token appears in the child exactly as typed and the browser console logs a warning.
Using blank values to inherit parent fields
For any field you add to the template (string, number, date, identity, etc.):
- If the template field value is left blank (empty), the extension will:
- Check the parent work item for a value for that field.
- If the parent has a value, copy it to the child.
- If the parent does not have a value, the field is simply not set on the child.
This blank-value inheritance is the recommended way to reuse parent values for all non-string fields, and also works well for string fields when you just want an exact copy.
Special Tokens
In addition to {FieldName} tokens, the extension supports special values in templates:
@me – Assign the work item to the current user (used with System.AssignedTo).
@currentiteration – Use the team's current iteration (used with System.IterationPath and team settings).
These special values are resolved at creation time based on the current user and team configuration.
Applying Child Work Items
- Open a parent work item and select "Create child work items" from the toolbar, or choose it from the parent's menu on a backlog or board.
- To run it for several parents at once, select them in a backlog and choose "Create child work items" from the menu. Large selections ask you to confirm first.
- The extension finds the matching Work Item Templates for each parent and creates them as child work items. A progress dialog shows each parent as it's processed, and you can cancel a long run.


↑ Back to top
Filter Examples
Simple filter — applies to User Story and Bug parents:
[User Story, Bug]
Minimal JSON — applies to User Stories whose title contains "integration":
{
"applywhen": [
{
"System.WorkItemType": "User Story",
"System.Title": "*integration*"
}
]
}
Several rules (OR across rules, AND within each rule) — applies to a User Story in Approved or Committed, or to a Bug tagged Security or Privacy:
{
"applywhen": [
{
"System.WorkItemType": "User Story",
"System.State": ["Approved", "Committed"]
},
{
"System.WorkItemType": "Bug",
"System.Tags": ["Security"]
},
{
"System.WorkItemType": "Bug",
"System.Tags": ["Privacy"]
}
]
}
Exact title or a title pattern — applies to a Feature titled exactly "Release checklist", or whose title contains "hotfix":
{
"applywhen": [
{
"System.WorkItemType": "Feature",
"System.Title": "Release checklist"
},
{
"System.WorkItemType": "Feature",
"System.Title": "*hotfix*"
}
]
}
One rule, several values per field (AND across fields, OR within each field list, except Tags) — applies to a Product Backlog Item or User Story in any of the listed states, columns, lanes, areas and iterations, that has both the Overdue and Urgent tags:
{
"applywhen": [
{
"System.WorkItemType": ["Product Backlog Item", "User Story"],
"System.State": ["New", "Approved", "Committed"],
"System.BoardColumn": ["Backlog", "Ready"],
"System.BoardLane": ["Default", "Expedite"],
"System.Tags": ["Overdue", "Urgent"],
"System.AreaPath": ["Project\\Area 1", "Project\\Area 2"],
"System.IterationPath": ["Project\\Iteration\\Sprint 1", "Project\\Iteration\\Sprint 2"]
}
]
}
↑ Back to top
Troubleshooting
"No templates found" error
- Verify templates exist for the project team (Project Settings → Boards → Team Configuration → Templates). Templates are defined and scoped per team and will only apply to work items for that specific team — they do not apply to other teams even if the user creating the child work items belongs to those teams. If you need the same templates elsewhere, create or copy them for each team (or switch the active team in the web UI to manage that team's templates).
- Verify the supported work item types configured for the Project in the Azure DevOps Organization Process settings (Project Settings → Boards → Process → Backlog Levels).
- Known limitation (temporary): Custom portfolio backlog categories above Epic may not resolve child types correctly in the current extension version, which can surface a "No templates found" warning even when templates exist.
Work items not created
- On Azure DevOps Server, check that your server version is supported. See Compatibility.
- Confirm filter rules match the intended parent work item field values.
- Check for malformed JSON in template description. Ensure your JSON is valid. Common issues include trailing commas, missing brackets, or improper escaping of backslashes. Use a JSON validator if unsure.
- Confirm you have permission to create work items in the target project.
- Check browser console logs for error messages from the extension.
Tags filter not matching
Area or iteration path not matching
Child work item has the same title as the parent
Inheriting parent field values not working
- Check browser console logs for warnings or errors; look for messages about unresolved parent fields or invalid types during creation.
- Ensure the template field value is truly blank (empty), not whitespace. Remove spaces; leave the value empty to inherit.
- Confirm the parent has a value for that field; inheritance only copies parent values if the field and value exists.
- Verify the child work item type supports the field; some fields are type-specific or process-specific.
- For tags, use
System.Tags-Add and leave it blank to inherit; do not use System.Tags in the template.
System.Title, System.IterationPath, and System.AreaPath automatically inherit from the parent when not set in the template; you do not need to set them as blank to copy these values.
Field reference name not recognized
- Use field reference names in templates (e.g.,
System.Title), not display names.
- For a complete list of available work item fields and their reference names, see the official Microsoft documentation: Work item field reference.
- To view a field's reference name in the Azure DevOps Process UI (including custom fields): Organization Settings → Process → select the process used by your project → Work item types → Fields → "Edit" a field → click the Options tab; the "Field Reference Name" appears in the details.
A token appears in the child exactly as typed
↑ Back to top
FAQ
What child work item types are supported?
The extension supports creating many child work item types, not just Tasks. The available child types depend on how your process is configured in Azure DevOps Organization Process settings (Project Settings → Boards → Process → Backlog Levels) and on current extension category-resolution support. For example, you can use this extension to create Bugs, Features, or custom types as children when they are defined as valid child types in your process/backlog configuration. Custom portfolio levels above Epic aren't fully supported yet; see Troubleshooting.
Does this extension work with Azure DevOps Server / TFS (on-premises)?
Yes, with Azure DevOps Server 2020 Update 2 and later. For older versions, see Compatibility.
How do I match templates for multiple states or types?
Use arrays in the JSON for that field (e.g., "System.State": ["Approved", "Committed"]).
Can I use wildcards on Area/Iteration?
No. Wildcards only work on System.Title; area and iteration paths must match the full path. See Advanced Filter (JSON).
How do I make tags match either A or B?
Add a separate applywhen entry for each tag. See Advanced Filter (JSON).
Why is the child work item title the same as the parent work item? How do I specify the title?
If the template doesn't set System.Title, the child copies the parent's title. Add System.Title to the template to set your own. See Setting Field Values.
Can I use parent field values in child work items?
Yes. Use Dynamic Parent Field Values to inherit parent values, compose strings with {FieldName} tokens, or insert just part of a value, and see Special Tokens for runtime values like @me (AssignedTo) and @currentiteration (IterationPath). Some fields are copied from the parent automatically; see Setting Field Values.
Can I create child work items for more than one parent at a time?
Yes. In backlog views, you can select multiple parent work items and run Create Child Work Items once. The extension will process each selected parent and show progress in the status dialog.
Can I enable the extension for only some projects?
No. Azure DevOps Services installs extensions at the organization level (Azure DevOps Server: collection level). They become available to all projects in that scope. To restrict usage you’d need to control permissions or uninstall/disable the extension at the org level.
↑ Back to top
Security
Create Child Work Items runs inside the Azure DevOps UI in your browser and does not require a separate backend service.
Required Azure DevOps Permissions
The extension requests only these scopes:
- vso.work - Read access used to evaluate the selected parent work item, retrieve team templates, and determine which templates apply.
- vso.work_write - Write access used to create child work items and link them to the parent hierarchy.
Azure DevOps Authorization Boundaries
The extension runs under your current Azure DevOps user context. It cannot bypass your Azure DevOps project and work item permissions.
Secrets and Source Code
- The extension does not request personal access tokens (PATs), passwords, or other secrets from users.
- The source code is private commercial software. For review and governance details, see the Terms of Use and Privacy Policy.
↑ Back to top
Changelog
All notable changes to Create Child Work Items. Dates in YYYY-MM-DD.
1.5.0 — 2026-10-30
- Added: Insert just part of a parent field value with
before, after or between. See Using part of a parent field value.
- Added: Open-source license notices in section 13 of the Terms of Use, and updated Credits.
- Fixed: Text in braces that isn't a field token, such as
{TBD}, code or JSON, was removed from child work items. See Using field tokens in string fields.
- Fixed: Parent values containing
$ or token-like text could change when inserted into a child.
- Changed: A token missing its period, such as
{Title}, is now kept as typed instead of being removed, so typos show up rather than being silently dropped.
1.4.2 — 2026-08-14
- Changed: Renamed the extension from "Create Child Tasks" to "Create Child Work Items" to reflect that it creates child work items of any type, not just Tasks. This is a display name change only — functionality, templates, and existing installations are unaffected.
- Added: A new organization-level admin/settings page for Create Child Work Items.
1.4.1 — 2026-07-19
- Fixed: Child type resolution for Basic process projects that do not define a Requirement backlog level, preventing Epic-level parents (for example, Issues under Epics with no Feature level) from returning no child template types and showing a "No templates found" warning
1.4.0 — 2026-06-28
- Added: Terms of Use documentation and license information for clearer governance and usage expectations
- Added: Privacy Policy documentation describing current data handling and future telemetry disclosures
- Added: Security documentation to explain extension permissions, authorization boundaries, and secrets handling guidance
1.3.0 — 2026-06-07
- Added: Create child work items directly from backlog item menus and board card menus, in addition to the existing work item form toolbar action
- Added: Ability to process multiple parent work items at once from backlog views, with confirmation for large selections and an option to cancel during processing
- Added: Progress Status Dialog for child work item creation with live progress, multiple parent queuing, process cancellation, refresh support, and completion status
1.2.0 — 2026-02-16
- Fixed: Dynamic parent field value tokens not working correctly in child work item templates
- Added: Dynamic Parent Field Values – inherit parent work item values on child work items using
{FieldName} tokens and blank-value inheritance. See Dynamic Parent Field Values for details.
- Added: Special Tokens support –
@me for AssignedTo and @currentiteration for IterationPath (documentation)
- Changed: Improved troubleshooting guidance for field value inheritance scenarios
1.1.2 — 2026-01-25
- Fixed: Error creating work items on Azure DevOps Server 2020 due to api-version=6.0 compatibility; Extension now uses the required 6.0-preview version.
1.1.1 — 2026-01-16
- Fixed: Big speed boost in Chrome and Edge browsers
- Changed: Improved overall performance of child work item generation
- Changed: Logging glow-up that brings clearer formatting and coverage when you need details
- Changed: General tune-ups and polish across the extension
- Changed: Updated compatibility to Azure DevOps Services and Azure DevOps Server 2020 Update 2+ to take advantage of improved performance on modern platforms; dropped support for older on-premises installs (Azure DevOps Server 2019 and earlier TFS). See the Compatibility section for how to continue using version 1.0.0 on older servers.
1.0.0 — 2025-12
- Fixed: Broken Tag filtering
- Fixed: Resolved "Error saving [object Object]" error message when creating child work items
- Fixed: Invalid/malformed template JSON failing remaining template matching (possibly causing not all matching child work items to be created)
- Fixed: Graceful handling use of @currentiteration when no default iterations are setup for respective Project Team
- Added: IterationPath filtering
- Added: Release Notes / Changelog
- Changed: Improved end user documentation: Overview, Key Features, How-To, Examples, Troubleshooting, FAQs
- Changed: Improved browser console logging
- Changed: Marketplace listing updates: Description, Tags
0.3.x — 2020
- Added: Wildcard filtering on Title
- Changed: Removed "Create child work items" button from backlog and board menu views to prevent child work items not being created reliably
0.1.x — 2019
↑ Back to top
Support
For help and to get in touch:
- Check docs first: Review the Overview, How‑To Guide, Filter Examples, Troubleshooting, and FAQ sections to see if your question is already answered.
- Use Q&A: For questions, feature requests, and anything not covered by the documentation, please use the extension's Q&A to submit and discuss.
- Email: For other scenarios or to contact the developer directly, email support@mattwilks.ca.
↑ Back to top
Credits
Create Child Work Items is an actively maintained fork of 1-Click Child-Links by Rui Figueiredo and its contributors. The portions derived from that project are used under the MIT License.
The original copyright and permission notice, along with notices for the other open-source components included in the extension, is in section 13 of the Terms of Use, which this listing links to.
↑ Back to top