Provide an option to toggle the Jira Work Items macro between interactive (editable) and read-only (immutable) display modes, allowing page authors and administrators to prevent viewers from editing issue fields directly from within the Confluence page — even when those viewers have edit permissions in Jira.

Problem Statement

The Jira Work Items macro (SLLV) allows inline editing of Jira issue fields — including summary, priority, and status — directly from the Confluence page.

While this inline editing correctly respects the user's permissions in the Jira project (only users with edit access in Jira can modify fields), there is no way for a Confluence page author or administrator to override this and enforce a read-only display regardless of the viewer's Jira permissions.

This is a behavioral regression from the Jira Legacy macro, which displayed issues as a static, read-only table where no modifications were possible from within Confluence — irrespective of the viewer's Jira permissions.

The core issue is one of context-appropriate access: a user may legitimately have edit permissions in Jira for their day-to-day work, but the Confluence page where those issues are embedded may serve a different purpose (release notes, audit records, stakeholder reports) where editing should not be possible. The admin or page author needs the ability to decouple the Confluence display behavior from the user's Jira permissions based on the use case.