Review code changes, open coding issues, publish release notes. Every one is ready to run, and you can adjust it in plain language.
Open a linked review when approved product requirements change.
See which specification changes need another decision before production continues, with a linked review for your product manager and a visible reapproval flag.
Summarize approved release changes for product review.
Get a release note draft on your team's website that follows your format and highlights questions for the release owner.
Draft product release changes for the owner's review.
You get a release changelog draft on your review issue, with clear features and fixes linked to the completed work behind them.
Organize release notes around customer impact for review.
Get release notes grouped by user impact, with source links and open questions ready for your maintainer to review before publication.
Compare finished story points with the current sprint scope.
Your team gets a sprint halftime report in its shared document, with point progress against current scope and links to work needing attention.
Group shipped changes by what users can now do or what was fixed.
Get a sourced release note draft in your tracker when version work closes. Review shipped changes against the previous release and resolve open questions.
Draft a sprint update with links to the underlying issues.
Get a sprint status report ready for your manager, with current issue and point progress and links to blocked work.
Track scope changes and unfinished backlog issues at sprint close.
Your team gets a sprint closure report that compares planned work with finished work. Linked unfinished issues show what needs attention.
Show completed story points and open blockers in the sprint.
Your sprint dashboard shows fresh issue and story point totals each workday morning, with blockers and links to the work behind the numbers.
Publish approved release changes for customers to read.
Your app changelog gets a dated customer update when a release goes live. Your product owner gets the public link on the release card.
Show how sprint work changed before stakeholder reviews.
Your Friday sprint report brings progress, blockers, and likely carryover together in a shared document, with links to the issues behind each claim.
Summarize completed work and remaining blockers for a chosen sprint.
Get a sprint report in a shared document for the sprint you choose. See progress and blockers, with links back to the issues.