Runs on Atlassian: DocDelta AI summaries use Atlassian Forge LLMs only. Page content is not sent to external AI providers.
Significance levels are AI-assisted guidance. Always verify against the diff output.
1. What DocDelta does
DocDelta is a Confluence macro that compares any two versions of a page. It shows a color-coded text diff and generates a plain-English AI summary of what changed.
- Version comparison: choose any two saved versions.
- Visual diff: added lines appear in green; removed lines appear in red.
- AI change summary: a headline, bullets, and a significance badge (low/medium/high).
- Audit context: each compared version includes the author and edit timestamp.
- Optional Jira review: create Jira issues for high-significance changes (if enabled).
2. Getting started
2.1 Insert the macro
- Open a Confluence page in Edit mode.
- Type / and search for DocDelta — Page Diff.
- Insert the macro.
- (Optional) Open the macro configuration panel to set options.
- Publish the page.
2.2 Configure the macro (optional)
If the macro is placed on the page you want to compare, you can usually leave configuration at defaults.
- Page ID: leave empty to use the page where the macro is placed; set to track another page.
- Default comparison: choose Latest vs previous or pick versions manually.
- Jira review options (if enabled): set project/issue options and the risk threshold for review creation.
3. Compare page versions
When the macro loads on a published page, you’ll see two dropdowns: From version and To version.
- Each version option includes the version number, author display name, and the edit date/time.
- Quick action: Compare with previous sets the To version to the latest version and From to the immediately previous version.
4. Read the diff
4.1 Line highlighting
- Green background (+): text added in the To version.
- Red background (−): text removed from the From version.
- No highlight: unchanged context lines.
4.2 Large page behavior
For long diffs, DocDelta paginates the comparison output. Use Previous and Next to move through the diff.
4.3 How content is compared
DocDelta converts Confluence storage HTML into normalized plain text before diffing, then compares line-by-line.
Formatting-only changes may appear as small or no textual changes.
5. AI change summary (with significance)
Above the diff you’ll find a Change summary card containing:
- Headline: one-line overview of the overall change.
- Bullets: details per section/topic that changed.
- Significance badge: low, medium, or high.
5.1 Cached summaries
If a summary was generated previously for the same version pair, DocDelta shows a Cached badge and loads it instantly.
Use Regenerate to refresh the summary.
5.2 Collapse / expand
Use Collapse or Expand to hide or show the summary details while keeping the headline and significance visible.
5.3 Audit trail: author & timestamp
DocDelta includes author and timestamp context alongside the version data you select. This helps reviewers understand who made the change and when, not just what the text changed to.
6. Share results
6.1 Copy to clipboard
- Open the Change summary card.
- Click Copy.
- Paste into Slack, email, tickets, or other internal documents.
6.2 Post as comment
- Click Post as comment in the summary card.
- DocDelta posts a footer comment to the current page containing the version range, headline/bullets, and significance.
Permission note: You need permission to add comments on the page.
7. Optional Jira review
If Jira review is enabled in the macro options for this placement, DocDelta shows a
Create Jira review issue button beneath the summary when significance meets the configured risk threshold.
- DocDelta must be installed on Jira as well as Confluence (same app, same site).
- The Jira issue includes the change summary (with author and timestamp context) and a link to the Confluence page at the selected To version.
- Jira issues are created manually from the macro — not automatically on publish.
8. Common scenarios
- Review the latest edit: use Compare with previous and read summary first, then scan the diff.
- Audit an older change: set From to an earlier version and To to a later version, then use Post as comment.
- Monitor from a dashboard: set Page ID to target a specific Confluence page and use Latest vs previous.
9. Limitations and tips
- Diff fidelity: summaries describe the diff excerpt provided to the model. Verify against the diff.
- Formatting and embeds: macros/embeds may not diff in fine detail; focus on text content changes.
- Tables and code: complex structures are flattened to text lines; review carefully.
- Performance: larger pages may take longer; wait for each diff page to load.
10. Troubleshooting
- No page selected: place the macro on a page, or configure a valid Page ID.
- No history available: publish at least two versions of the page.
- Permission denied: confirm DocDelta is installed and you have page access.
- Summary unavailable: click Regenerate or ask your admin about Forge LLM availability.
- Jira button missing: enable Jira in macro options; confirm significance meets the risk threshold; confirm DocDelta is installed on Jira.
11. Support
Email: support@helmlabs.uk
If you update this guide for new functionality, also update the “Document Version” and “Effective Date” fields above.