[Bug]: Images in Azure DevOps work item descriptions show "Image unavailable" on the Issues page

Offen
#39,723 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@juliusmarminge arbeitet bereits daran.

Seit 20.11.2026.

  • #39741 von @juliusmarminge — offen

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Veraltet
Tech-Stack
azure, typescript
Bereich
backend, desktop

Rechercherichtung

The issue identifies apps/server and the Azure DevOps work item attachment URL under /_apis/wit/attachments/. Start by tracing how read_issue loads the description and how the existing pull request attachment handling authenticates image requests. Done means pasted work item images display on the Issues page using the available Azure DevOps credential; an open linked pull request shows work is already underway.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/server

Steps to reproduce
  1. In a private Azure DevOps project, create a work item and paste a screenshot into its Description.
  2. Add a local repository whose origin is an Azure Repos URL in that project.
  3. Open Issues and open the work item.
Expected behavior

The pasted image shows in the description.

Actual behavior

Each image shows an "Image unavailable · Image" card.

The body read_issue returns is HTML whose images point at the work item attachment endpoint:

<img src="https://<org>.visualstudio.com/<project-guid>/_apis/wit/attachments/<attachment-guid>?fileName=image.png" alt=Image>

That endpoint answers only a request that carries an Azure DevOps credential. The client loads the URL directly, without one, so the load fails. The environment does have the credential: the same work item's text loads through az.

Related, but not the same URL or surface:

  • #36148 (open) authenticates Azure DevOps pull request attachments. Its matcher accepts only /_apis/git/repositories/<id>/pullRequests/<n>/attachments/<name>, and its comment says "Only pull request attachments may be fetched". Work item attachments under /_apis/wit/attachments/<guid> are not covered.
  • #21014, #25922, #19828 and #39085 report the same symptom for GitHub, Bitbucket and Linear.
Impact

Major degradation or frequent failure

Work items that explain a problem with screenshots lose them, for the user and for an agent that is handed the work item.

Version or commit

0.1.11 (desktop)

Environment

macOS 26.5.2, T3 Code desktop 0.1.11, azure-cli 2.90.0, azure-devops extension 1.0.4, Azure DevOps Services on a *.visualstudio.com organisation

Workaround

Open the work item in Azure DevOps.

Vorherrschende Sprache
TypeScript
Sterne
24.8k
Forks
6.4k
Ø Merge
4 Std. 29 Min.
Gemergte PRs (30 T.)
488

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus pingdotgg/t3code

Alle Issues in pingdotgg/t3code

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.