Issue Summary

Re-introduce native embedding of filtered Jira Roadmaps/Timelines in Confluence

Previously, users were able to embed targeted, filtered Jira Roadmap/Timeline views directly into Confluence pages (e.g., filtered by specific epics, labels, components, or custom views).

Following recent updates to how Jira Roadmaps and Smart Links/macros embed into Confluence, this direct filtered embedding capability has been restricted or removed. Users are now forced to use workarounds such as embedding the entire unfiltered project timeline, manually taking static screenshots, or using limited macro alternatives.

Current Workaround & Its Limitations:

• Unfiltered Views: Embedding a full project roadmap exposes irrelevant epics/issues to stakeholders and creates unnecessary clutter.

• Maintenance Overhead: Teams resorting to screenshots or manual table exports lose dynamic live syncing when issue dates or statuses change.

• Fragmented Reporting: Confluence pages intended as focused executive summaries or project charters cannot display the scoped roadmap views that teams need.

Suggested Solution:

1. Direct Filtered Embeds: Restore the ability to embed Jira Roadmaps/Timelines with applied filters (by epic, label, component, release, or custom JQL) directly within Confluence.

1. Macro View Configuration: Allow authors to configure and persist specific view options (e.g., hierarchy level, timeline view by month/quarter, visible fields) within the Confluence macro/embed settings.

1. Interactive & Dynamic Syncing: Maintain real-time sync with underlying Jira work items so changes to start/due dates and dependencies are immediately reflected.

Why this is important (Business Impact):

• Seamless Jira-to-Confluence reporting is a core value driver for cross-functional teams.

• Enables project leads and managers to communicate clear, targeted timelines to stakeholders without exposing extraneous project details.

• Eliminates friction and duplicate manual work across teams.