Sprint health monitor
ActiveReview the current sprint. Summarize blocked work, missing owners, and issues that need a decision.
Weekly at 9:00 AM
SMTWTFS
Last run Sep 11
12 runs
leera AIReports & Charts
See the progress.
Understand the story.
Turn project activity into a report you can read and charts you can explore. Keep the question, the numbers, and the next decision together.
A view of the work, with the context to understand it.Built into your workspace.
From “how’s it going?” to “here’s what’s next.”
A focused report. A useful metric. Enough context to know what it means. Leera’s built-in AI generation requires a configured provider; saved reports and charts remain viewable without one.
01Templates & custom briefs
A good report starts with a better question.
Start with sprint, team, project, or metrics templates, or write a custom analysis brief. Generate a report, refine the text, and download it as PDF, Markdown, HTML, or Word-compatible HTML (.html).
ContextTemplates for sprint summaries, retrospectives, burndown, velocity, workload, and more.
ControlEdit saved reports, make a copy, or export the result for your next discussion.
02Project reports
An update worth opening.
Start from a template or a focused brief. Build a report around completed work, open blockers, workload, or logged effort, with a clear audience and reporting period.
ContextKeep the report focused on the reader’s next decision.
ControlCheck important findings against the underlying work.
03Custom charts
Ask a question. See the shape of the answer.
Create charts in Leera AI or with a connected MCP client. Name the project, metric, and period, then inspect the values in Charts. Start with a copyable prompt when you need help framing the question.
ContextMCP live charts refresh from supported issue or test-result queries; snapshots keep supplied values.
ControlKeep issue counts, story points, and logged effort clearly distinguished.
04Recurring reports
Make the next update part of the routine.
Give an AI Agent a reporting objective and schedule for recurring reviews. Set the scope and cadence, then inspect the output in execution history.
ContextA consistent reporting period makes a review easier to follow.
ControlMissing owners, estimates, or worklogs are gaps to investigate.
A few details
A little more context.
Do reports and charts need an AI provider?+
Leera’s built-in AI generation requires a configured provider. Saved reports and charts remain viewable without one. A connected MCP client can save charts without using Leera’s configured provider, subject to AI access, connection scopes, and project permissions. Check source records and important findings before sharing a result.
Can I create charts with an AI client connected through MCP?+
Yes. With AI access and chart-write permission, your connected client can save a live chart of issues or test results, or a snapshot of supplied data. Live values are recomputed when you open or refresh a chart; snapshots stay fixed. Charts belong to the connected member and appear in that member’s Charts library after refresh. MCP uses supported datasets and metrics, not arbitrary SQL. The chart prompt library includes copyable starting points; confirm the project, metric, and reporting period with your client.
Are reports only for sprint reviews?+
No. Reports can support project summaries, workload discussions, worklog reviews, and other questions about the records in your workspace. Choose the template or prompt that matches the question and review the generated result.
Which formats can I export?+
Save your edits, then export a report as PDF, Markdown, HTML, or Word-compatible HTML (.html). For PDF, use Print / save as PDF to preview the report, choose the paper size, orientation, and scale, and download the file. Reports use the same print preview as Documents. The Word-compatible option is an HTML file, not a DOCX document.
What if the data behind a report is incomplete?+
The report can only work with the records available to it. Check missing owners, estimates, statuses, and worklogs before interpreting a trend. Make those gaps explicit when sharing the report rather than treating absent data as zero.
Less overhead. More possibility.
Make room for the work ahead.
A view of the work, with the context to understand it.
Keep exploring