Azure-devops-docs: Provide an example for Create a work item on failure.

[code4clouds]

It is not clear how to implement this in the YAML build and a quick sample can make a huge difference.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 0fa5a83c-70fd-6925-a8c8-256b21c21a2e
• Version Independent ID: 75f4a136-7245-7878-2953-6b68272fe4ec
• Content: Build pipeline options - Azure Pipelines & TFS
• Content Source: docs/pipelines/build/options.md
• Product: devops
• GitHub Login: @andyjlewis
• Microsoft Alias: alewis

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[aaronclarke]

There is still no example YAML for "Create a work item on failure." I don't know where I would add it in my yaml file and I don't know what the name of the setting is.

[andyjlewis]

Thank you for posting this issue. Apologies for the delayed response. I've added this request to our backlog. Heads up to @steved0x

[GCHQ77703]

Is there any progress with this item?

[MichaelGoulding]

Is there a way, or is this feature not supported yet?

[sphanley]

@Andyjlewis, @steved0x, any chance one of you can provide clarity on whether this is really a documentation issue (i.e. this functionality exists, but isn't properly documented) or whether this is functionality that exists in classic pipelines but not in YAML? My org is in the process of migrating all of our pipelines to YAML, and we're going to lose a big piece of our failure handling workflow if we can't create work items on failures.

[sphanley]

For anyone still struggling with this - there's apparently no way to define this in the YAML, but I managed to find a way you can turn it on the same as for Classic pipelines by using some undocumented API functionality. Hope this helps someone - and that Microsoft can just expose the options in the UI, since it apparently works otherwise!

[code4clouds]

@andyjlewis @steved0x Is there any update on the backlog item to correct this in an elegant way?