Skip to main content

50 posts tagged with "mermaid"

View All Tags

Map States & Approval Workflows in Confluence with Mermaid

· 6 min read

The issue workflow lives in a wiki page that says "the approval chain is: team lead, then manager, then finance". The config says otherwise, the Jira post-function disagrees, and the incident report asks "who actually approved this?" — with three different answers on screen. A prose paragraph cannot hold a workflow; a diagram can, if it is the workflow.

Quick answer: document state machines and approval chains in Confluence as Mermaid stateDiagram-v2, rendered by Mermaid Plus Diagrams & AI Agent for Confluence. Every legal state, every transition, every human decision on a labeled arrow — in editable text that stays true. This post gives you three copy-paste examples: an issue lifecycle, a spending approval chain, and a retry loop with a timeout.

UML Use Case Diagrams in Confluence (Mermaid, Copy-Paste)

· 4 min read

The use case diagram is the scope picture: actors on the outside, what the system does for them on the inside, and — the reason product and engineering fight — the line between them. In Confluence that picture usually comes from a diagramming tool export that goes stale the moment scope moves.

Mermaid 12 added the syntax to render UML use case diagrams from text — usecase-beta — and Enhanced Markdown for Confluence renders it in the same macro as everything else on the page. This guide gives you the syntax and two copy-paste diagrams.

ZenUML Sequence Diagrams in Confluence: Copy-Paste Guide

· 4 min read

Sequence diagrams die in Confluence in one of two ways: someone draws one in a diagramming tool, exports a PNG, pastes it into a page — and three sprints later the flow has changed but the image has not. Or someone writes the flow as prose ("the client calls the order service, and if payment is approved…"), which is accurate but impossible to read under time pressure.

ZenUML splits the difference: the diagram is code, so it edits like code and renders like a diagram — branches, error paths, and parallel work included. This guide shows the syntax with copy-paste examples you can drop into Confluence today.

Mermaid 12 in Confluence & Jira: UML Use Case Diagrams and a New Look

· 5 min read

Mermaid 12 is the biggest release the diagram language has had in years — and as of today it is live in all three NGPILOT diagram apps: Enhanced Markdown for Confluence, Mermaid Plus Diagrams & AI Agent for Confluence, and Mermaid Plus Diagrams for Jira. You get the headline feature immediately: UML use case diagrams, the diagram type Confluence and Jira teams have been asking for since requirements documents moved out of dedicated UML tools.

How to Create a Flowchart in Jira — 3 Methods with Copy-Paste Examples

· 6 min read

Jira is where the work happens — but the process behind the work usually lives in someone's head or in a stale Confluence page nobody opens. A flowchart on the Jira issue itself fixes that: bug triage paths, approval chains, and escalation procedures become visual, unambiguous, and impossible to miss.

Jira Cloud gives you two ways to get there, and they serve different needs. This guide walks through both, then gives you three copy-paste Mermaid flowchart examples for the scenarios Jira teams hit most: bug triage, approval workflows, and incident escalation.

How to Build a Release Timeline in Jira — 3 Methods with Copy-Paste Examples

· 5 min read

A release date doesn't slip in one dramatic moment — it slips in six quiet ones: QA took two extra days, staging froze late, sign-off waited on legal. A release timeline pinned to the release epic makes those slips visible while they're still cheap to fix, because every stakeholder reads the same picture of what's next and what's blocked.

Jira gives you three ways to build that picture. This guide walks through them, then gives three copy-paste Mermaid Gantt examples sized for real releases: a single version, a multi-team launch, and a launch-week sequence.

Mermaid vs PlantUML vs Graphviz for Confluence: Which Diagram Tool to Choose

· 7 min read
Quick Answer

Mermaid, PlantUML, and Graphviz are the three most popular text-based diagramming languages. Mermaid is the easiest to learn and covers the widest range (30 diagram types). PlantUML excels at detailed UML with precise notation control. Graphviz is best for technical network and dependency graphs. Most Confluence teams should start with Mermaid and add Graphviz for network diagrams if needed.

What you'll learn
  1. The strengths and weaknesses of each tool
  2. Which diagram types each one supports
  3. How easy each is to learn and use
  4. A practical recommendation for Confluence teams

Text-based diagramming — writing a few lines of code that render into a diagram — is how modern teams keep diagrams in sync with their documentation. No more drawing boxes by hand in Visio, exporting screenshots, and pasting them into Confluence where they go stale. With text-based diagrams, you edit the source and the diagram redraws instantly.

But there are three major text-based diagramming languages, and they are not interchangeable. Each has different strengths, different syntax, and different ideal use cases. This guide compares Mermaid, PlantUML, and Graphviz so you can choose the right one (or combination) for your Confluence team.

Mermaid Diagrams for Jira Sprint Workflows — Which Diagrams Actually Help the Standup

· 9 min read
Who should read this
  • Scrum masters and eng leads who run standups from Jira
  • Development teams deciding which diagrams to maintain across a sprint
  • Anyone who wants to know which of Mermaid's 30 diagram types are actually useful for agile work
What you'll learn
  1. The four Mermaid diagram types a sprint team actually reaches for
  2. How to embed each one inside a Jira issue, with copy-paste syntax
  3. When a diagram belongs in Jira vs. Confluence
  4. The full 30-type reference for less common needs

Every team that adopts Jira diagrams hits the same moment: you discover Mermaid supports 30 diagram types, you get excited, and then you realize you have no idea which ones to actually use during a sprint. Most of them never get drawn. The diagrams that earn their keep are the ones that make a standup faster, an onboarding doc clearer, or a ticket unambiguous — and those are a small, repeatable subset.

This post is the workflow guide we wish we'd had: the four diagram types a sprint team actually uses, each with a real scenario and copy-paste syntax you can drop straight into a Jira issue. The full 30-type reference follows, so the same page works as both a sprint playbook and a complete catalog.

Write Markdown in Confluence With Mermaid, LaTeX & Code — One Editor, Live Preview

· 8 min read
Who should read this
  • Engineering teams who write docs in Markdown but live in Confluence
  • Research/academic teams who need LaTeX math equations inside wiki pages
  • Anyone tired of Markdown editors that drop Mermaid diagrams or render math as plain text
What you'll learn
  1. How to write Markdown in Confluence with a live split preview
  2. Embedding Mermaid flowcharts and ZenUML sequence diagrams inside Markdown
  3. Rendering KaTeX and full LaTeX (MathJax) math — inline, block, and fenced
  4. GitHub-flavored tables, 190+ code languages, and dark mode

The scenario every technical team hits: your engineering docs live in Markdown — READMEs, API references, design docs — and they contain diagrams (Mermaid), equations (LaTeX), and code samples. You paste that Markdown into Confluence, and it falls apart. The Mermaid code blocks render as plain text. The LaTeX equations show as raw $...$ syntax. The code blocks lose their syntax highlighting. Confluence's native editor is WYSIWYG, not Markdown, and the import tools treat Markdown as a one-time conversion rather than something you edit live.

Enhanced Markdown for Confluence solves this with a Markdown editor that renders everything inline — Mermaid diagrams, KaTeX and LaTeX math, syntax-highlighted code, and GitHub-flavored tables — with a live split preview. It runs on the Quikdown engine, so all rendering libraries are bundled locally (no external CDN dependencies, which matters for "Runs on Atlassian" compliance). This guide walks through writing Markdown in Confluence with diagrams, math, and code all rendering live.