Attachment triggers and queue consumer
When a .md file is added to or removed from an issue, Markdown for Jira recounts the .md attachments on that issue and updates its search index. This runs in the background on your Jira site, and there is nothing to set up.
#Worth knowing
The index only updates while the app is licensed. 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 |
Edit a Markdown document | Issue view > Markdown panel > Edit |
Delete a Markdown document | Issue view > Markdown panel > Delete icon on the tab |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Title | Editor modal | Sets the filename. Saving any edit, including a new title, deletes the old file and adds a new one, and the index is updated both times. |
#A few things that catch people out
Editing replaces Jira's attachment record: the old .md attachment is deleted and a replacement uploaded, so the attachment id, upload date and author all change, the issue history shows a delete and an add, and links to the old attachment 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 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.
#Related
How it actually behaves.
