Jira Dashboard Analytics Millarum Dashboards

Six purpose-built Jira dashboard widgets β€” all synchronized through a single master filter. Visualize your team's work with charts, lists, flow diagrams, and activity streams without ever writing JQL.

βœ“ Jira Cloud βœ“ 6 Widgets βœ“ Real-time Sync βœ“ No JQL Required

What is Millarum Dashboards?

Millarum Dashboards extends Jira's native dashboard experience with six purpose-built widgets that work together as a cohesive analytics suite. The core concept is dashboard-wide filter synchronization: configure one Millarum Slicer gadget and every other Millarum widget on the same dashboard instantly responds β€” project, issue type, status, assignee, date ranges, and any custom Jira field you choose.

BenefitDescription
One filter, all widgets Change the Slicer and every chart, list, and diagram updates immediately.
No JQL required Pick filters from dropdowns β€” no query language knowledge needed.
Rich visualizations Pie, Donut, Gauge, Bar, Stacked Bar, Line charts, and Sankey flow diagrams.
Clickable drilldowns Click any chart segment to open the matching Jira issue search.
Preset filters Save and restore named filter combinations for quick switching.
Inline editing Edit issue Status, Assignee, Priority and more directly from the List widget.

Creating a Dashboard from Scratch

  1. Open the Dashboards page

    In Jira, click the Dashboards menu in the top navigation bar, then select Manage dashboards.

  2. Create a new dashboard

    Click Create dashboard in the top-right corner. Give it a name (e.g., Team Overview), choose a sharing option (Private, My organization, or specific people), then click Create.

  3. Open "Add a Gadget"

    Once your empty dashboard opens, click the Add gadget (+) button in the top-right area of the dashboard canvas.

  4. Search for Millarum widgets

    In the Add a Gadget dialog, type mill in the search box. All six Millarum gadgets will appear. Click Add next to each one you want.

  5. Configure the Slicer first

    After adding widgets, open the Millarum Slicer configuration dialog, give it a name, and save. The Slicer must be set up before the other widgets will display data.

Important

The Slicer must be on the same dashboard as the other widgets. Filters only broadcast to widgets on the same dashboard page.

Recommended Starter Layout

For a well-rounded team dashboard, add gadgets in this order:

#WidgetPurpose
1Millarum SlicerAdd this first β€” it drives all other widgets
2Millarum ChartsVisual distribution breakdowns by any field
3Millarum Created vs ResolvedTimeline health view
4Millarum ListDetailed issue browsing with inline editing
5Millarum Activity StreamTeam contribution visibility by person
6Millarum Sankey DiagramFlow and transition analysis

How Filter Synchronization Works

Millarum Dashboards keeps all widgets in sync automatically. When you change a filter in the Slicer, every other widget on the same dashboard updates to match β€” no manual refresh needed.

  1. You select filters in the Slicer (Project, Issue Type, Status, etc.).
  2. The Slicer broadcasts the filter selection to all other widgets on the dashboard.
  3. All other Millarum widgets detect the change and automatically reload their data.

Every widget updates simultaneously within a few seconds of changing a filter β€” no manual refresh needed on any individual widget.

Tip

Use Presets in the Slicer to save commonly used filter combinations (e.g., "Sprint 42", "Bugs only", "My team") and switch between views in a single click.

Tips & Best Practices

  • Always add the Slicer first. Without a Slicer, other widgets show a "Please add the Millarum Slicer" message.
  • Use Presets in the Slicer to save frequently used filter combinations.
  • Resize columns in the List widget by dragging column headers. Widths are saved automatically.
  • Click chart segments in Charts, Created vs Resolved, and Sankey widgets to open a Jira issue search for that exact data point.
  • Use Sankey History mode to visualize how issues have flowed through statuses over time β€” great for retrospectives.
  • Use Stacked Bar charts when you want to compare two fields simultaneously (e.g., Issue Type stacked by Status).
  • Lower Activity Stream's Max Issues if the widget is slow β€” it reads the full history of each issue, which takes longer for large sets.