Attachment triggers and queue consumer
Listens for attachment created and attachment deleted events, recounts the .md attachments on the affected issue and updates the search index. Two install/upgrade triggers also run for bootstrap. The work is dispatched through the app's queue.
#Worth knowing
The attachment triggers only fire on a licensed site. There is no backfill and no scheduled reindex.
#Where to find it
Runs on the Jira site
#Where you do it
Task | Where |
|---|---|
Add a Markdown document to an issue | Issue view > Markdown panel > Add |
Read a Markdown document | Issue view > Markdown panel |
Edit a Markdown document | Issue view > Markdown panel > Edit |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Title | Editor modal | - |
#Worth knowing
Editing is destructive to Jira's attachment record: the old .md attachment is deleted and a replacement uploaded, so the attachment id, upload date and author all change, watchers see delete-then-add events, and links to the old attachment id break.
The global page's Created column and its sort order use the attachment's created date, not a true modification date.
Without an active licence in production the whole panel and the whole global page are replaced by a licence banner. Existing documents cannot be read through the app, though the .md files remain downloadable from Jira's attachment list.
Non-production builds (staging, PR previews, local tunnels) run with licensing disabled, which bypasses the licence check and also drops the licensed attachment triggers unless a licence is forced.
#Related
How it actually behaves.
