Sprint issues by status
Current sprint · Leera App
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 focused report. A useful metric. Enough context to know what it means.
Start with sprint, team, project, or metrics templates, or write a custom analysis brief. Generate a report, refine the text, and download it as Markdown, HTML, or Word.
ContextTemplates for sprint summaries, retrospectives, burndown, velocity, workload, and more.
ControlEdit saved reports, make a copy, or export the result for your next discussion.
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.
Generate charts in AI chat by naming the project, metric, and period. Inspect the values, ask a follow-up, and return to generated charts in the Charts view.
ContextRefine the question in the same conversation.
ControlKeep issue count, estimates, and logged time clearly distinguished.
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
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.
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.
A view of the work, with the context to understand it.
Keep exploring