Azure-devops-docs: Pipeline Trigger Issues

[spowser]

In the section YAML resource trigger issues support and traceability it states there is a menu item in the pipeline definition page. Where on the page? Which pipeline definition, source or destination? Can we get a screenshot showing the menu item on the page? I've clicked on just about everything I can think of and not seeing it :(

https://docs.microsoft.com/en-us/azure/devops/pipelines/process/resources?view=azure-devops&tabs=schema#yaml-resource-trigger-issues-support-and-traceability

---

Document Details

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

• ID: ee4ec9d0-e0d5-4fb4-7c3e-b84abfa290c2
• Version Independent ID: 3e2b80d9-30e5-0c48-49f0-4fcdfedf5eee
• Content: Resources - Azure Pipelines
• Content Source: docs/pipelines/process/resources.md
• Product: devops
• Technology: devops-cicd-process
• GitHub Login: @juliakm
• Microsoft Alias: jukullam

[juliakm]

To get to the Trigger Issues menu item, go to the pipeline runs page. Then, open the menu with three dots. If your pipeline supports Trigger Issues, you should see that as an option. Here's what it looks like for me. I'll also update the docs.

[scp-mb]

@juliakm What defines a pipeline as supporting trigger issues? That option doesn't show for any of our pipelines, yaml or classic, CI or CD. None of them it seems. You also seem to have export options that aren't present?

Classic CI

YAML CI / CD

[spowser]

@scp-mb This was also my next question. What constitutes a supported pipeline? I have pipeline resource triggers so I would think this should qualify?

[scp-mb]

@Court72 Requesting this be reopened please as the problem is still there. Seemingly nobody can find said page.

[juliakm]

@scp-mb What version of Pipelines are you using?

[scp-mb]

We're using the cloud hosted DevOps if that's what you're asking (not self hosting via DevOps Server). As far as I know that doesn't give us a specific "version" of pipelines?

[spowser]

@juliakm It appears we are currently on Sprint 178

[juliakm]

@scp-mb and @spowser The development team is looking into this issue and possible fixes. It is not a documentation issue right now, but more of a functionality one.