Working with other capabilities
Markdown for Jira is a standalone app. It does not need any other Capable app installed, and it does not share data with them. This page is the summary; Integration covers everything it connects to in Jira.
Where a connection does not exist, it is listed as such rather than left out, so you can stop looking.
#Every connection
Connects to | What you get |
|---|---|
Capable Markdown for Confluence | The same built-in templates and the same diagram languages. Documents do not move between Jira and Confluence: a Markdown document on a Jira issue does not appear in Confluence, and Confluence Markdown macros are not available in Jira. |
Capable Diagrams for Jira | No connection. Diagram code blocks in a Markdown document render on their own, whether or not Capable Diagrams is installed. |
Other Capable apps for Jira | No connection. Installing another Capable app adds nothing to the Markdown panel or the Capable Markdown page. |
Capable's hosted services | Diagram code blocks are drawn as images, and web images are loaded through Capable so they display inside Jira. |
#The pages
#A few things worth knowing
Diagrams and web images come from Capable's hosted services, so they need a signed-in session. Logged-out viewers see nothing from the app.
JQL search and the Capable Markdown page only see .md files added or removed since the app was installed and licensed.
Markdown for Jira has no Rovo agents or actions and no dashboard gadget.
#Related
Better with company.
