Found while building a test fixture during e2e verification of the --reply-to fix. Pre-existing on main, unrelated to that branch.
Problem
The documented markdown syntax for embedding an attachment is !media[attachment-id] (see AGENTS.md → Formatting Guidelines). But the id it needs is the Media Platform UUID (e.g. 0df3c2f3-721e-43e7-b481-a5cd54ac45e8), not the numeric attachment id that atl jira issue attachment PROJ-123 --upload file.png returns (e.g. 33327).
Passing the numeric id produces a media node Jira rejects.
There is currently no CLI path from an upload to the UUID — you have to read a comment or description ADF back through the REST API to find it. That makes the documented syntax effectively unusable from the CLI alone.
Suggested fix
Resolve the numeric attachment id to its Media Platform UUID when building the node, so !media[33327] works with the id the CLI itself just printed. Failing that, have --upload print the UUID alongside the numeric id, and document which one !media[] wants.
Related: #14, #15.
Found while building a test fixture during e2e verification of the
--reply-tofix. Pre-existing onmain, unrelated to that branch.Problem
The documented markdown syntax for embedding an attachment is
!media[attachment-id](seeAGENTS.md→ Formatting Guidelines). But the id it needs is the Media Platform UUID (e.g.0df3c2f3-721e-43e7-b481-a5cd54ac45e8), not the numeric attachment id thatatl jira issue attachment PROJ-123 --upload file.pngreturns (e.g.33327).Passing the numeric id produces a media node Jira rejects.
There is currently no CLI path from an upload to the UUID — you have to read a comment or description ADF back through the REST API to find it. That makes the documented syntax effectively unusable from the CLI alone.
Suggested fix
Resolve the numeric attachment id to its Media Platform UUID when building the node, so
!media[33327]works with the id the CLI itself just printed. Failing that, have--uploadprint the UUID alongside the numeric id, and document which one!media[]wants.Related: #14, #15.