Support

Answered by the developer, not a queue.

Reporting a bug

The fastest fixes come from reports that include:

• What you did, what you expected, and what happened instead.
• The chart configuration — chart type, group-by field, and the source (project, filter, or the JQL text) with anything sensitive redacted.
• Roughly how many issues the filter matches.
• A screenshot of the gadget, including the footer line.
• The time it happened (with timezone) — this lets us find the exact run in the logs.

Common questions

Two people see different numbers on the same dashboard. Why?

By design. Every chart is computed as the person viewing it, so it only counts issues their Jira account can see. If your numbers differ, your browse permissions differ.

My chart says “Updated 12m ago”. Is it broken?

No — results are cached for 15 minutes per person to keep dashboards fast. Click Refresh in the footer for an on-the-spot recomputation.

My scheduled export didn’t arrive at the exact hour.

Schedules fire on an hourly sweep, so a run lands within the hour after its scheduled time. Note that schedule hours are UTC. Use Run now in the Schedules panel to fire one immediately.

Where do scheduled exports go?

Into the Recent runs list in the gadget’s Schedules panel, kept for seven days. Koala never emails files or sends them anywhere — your data stays inside Atlassian.

The line chart says it needs a date field.

Line and area charts plot time, so Group by must be a date field — created, resolved, or due date. Any other field suits the donut, bar, KPI, or table.

Can I chart issues from several projects?

Yes — choose Custom JQL as the source, e.g. project in (ONE, TWO) AND created >= -90d.