I really need the concept of "my work" to be expanded.

I really need the concept of "my work" to be expanded. It's currently tied exclusively to GitHub Issues and PRs, but I'm also doing a lot of work in Azure DevOps and for "my work" to be useful, it needs to include those items as well. It may be better to generalize "my work" as more of a generic underlying "to do" system that could be linked to GitHub Issues, GitHub PRs, ADO work items, ADO PRs, or even just arbitrary "to do" items that could be created as output from Automations, or even just manually.

---
| Field | Value |
| --- | --- |
| App version | 1.1.10 |
| OS | Windows 10.0.26100 |
| Theme | GitHub |
| Path | /workflows |
| Tenure | Week 6 |

The issue identifies /workflows as the relevant path but names no files or tests. Start by tracing how “my work” currently handles GitHub Issues and PRs there, then clarify the supported work-item sources and completion criteria with maintainers before changing anything.

Rédigé par le modèle d'indexation à partir du texte de l'issue.