github / github/app

[AzureDevOpsExtension] Inline work item attachment images do not render in canvas

未关闭
#3,274 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
没有语言数据
星标
2.1k
派生
153
PR 合并指标
30 天内没有已合并 PR

描述

### Affected version or release

1.0.80

### Installation context

GitHub Copilot app on Windows, using the built-in Azure DevOps canvas to view a work item.

### What happened?

Images uploaded as Azure DevOps work item attachments and embedded inline in the work item description do not render in the Azure DevOps canvas. The canvas shows a broken-image icon followed by the image alt text. The rest of the description renders normally.

The same description, including its inline images, renders correctly in the Azure DevOps web UI.

### Steps to reproduce

1. Open an Azure DevOps work item in the web UI.
2. Upload an image into the work item description so Azure DevOps stores it as a work item attachment.
3. Save the work item and confirm that the image renders inline in the Azure DevOps web UI.
4. Open the same work item in the built-in Azure DevOps canvas in the GitHub Copilot app.
5. Observe the broken-image icon and alt text instead of the image.

### Expected behavior

Authenticated Azure DevOps attachment images embedded in a work item description should render inline in the canvas, matching the Azure DevOps web UI.

### Additional context

This appears specific to protected Azure DevOps attachment URLs. The canvas can render the surrounding rich text, but its image request may not use the Azure DevOps extension's authenticated request path.

#### Example failing image reference

```markdown
![Template Package Import from file selection through Import check, Confirm, Import, and opening the imported Configuration Template.](https://dev.azure.com///_apis/wit/attachments/)
```

The failing source is a direct authenticated `_apis/wit/attachments/{id}` URL without a public access token or query string. The organization, project ID, and attachment ID are redacted because this is a public issue.

贡献指南

打开贡献指南

调研方向

从 Azure DevOps 的画布渲染路径开始,跟踪如何请求 _apis/wit/attachments/{id} 的 Markdown 图片 URL。将该请求与 Azure DevOps 扩展的已认证请求路径进行比较;完成标准是受保护的附件图片能够在画布中以内联方式渲染,与 Azure DevOps Web UI 一致,同时不破坏周围的富文本。

由索引模型根据 Issue 内容生成。

评估

技术栈
azure
领域
frontend
Issue 类型
缺陷
难度
3/5
预计耗时
1-2 天
活跃度
活跃
描述清晰度
基本清楚
新手友好度
55/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。