Capable Markdown (global page)
A cross-project browser for Markdown. The header reads 'Capable Markdown for Jira'. It shows an item count, a project filter, a Getting started / List view toggle, and a table of Markdown attachments with columns Name, Issue, Summary, Author, Created and Size. Clicking a row opens the issue in Jira's own issue dialog. The list loads 50 issues at a time, with a Show more button for the rest.

#Worth knowing
Only visible to logged-in users. The list depends on the app's search index, so it only shows .md files added or removed since the app was installed and licensed.
#Where to find it
Jira > Apps > Capable Markdown

#When it opens
The page opens on Getting started until you click View markdown; after that it opens on the list in that browser. The project filter starts on 'All projects'.
#Where you do it
Task | Where |
|---|---|
Browse Markdown across projects | Jira > Apps > Capable Markdown |
Show only some projects | Apps > Capable Markdown > project selector |
Check the licence is active | Jira > Apps > Manage apps |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Getting started / List view | Apps > Capable Markdown > two icon buttons in the header | Switches between the welcome view, with help cards and a View full documentation button, and the list of documents. |
Project filter | Apps > Capable Markdown > project selector | Limits the list to the projects you pick. It is not saved when you leave the page. Clear filters appears when a filter leaves the list empty. |
#A few things that catch people out
There is no version history for a Markdown document, neither in Jira nor in the app.
Files that were on issues before the app was installed, or added while it was unlicensed, do not appear until a .md file is next added to or removed from that issue.
The Created column and the sort order use the date the attachment was uploaded. Saving an edit uploads a new file, so an edited document moves to the top.
Raw HTML inside a Markdown document is not rendered.
Diagram source is sent to Capable's hosted rendering service so it can be drawn as an image.
Content that does not look like Markdown can be replaced by an 'Invalid markdown provided' message naming the detected language.
#Related
How it actually behaves.
