Release notes
What changed, and when
Every ImproveDesk release is listed here, newest first. Security fixes are released as soon as they are ready rather than waiting for a scheduled release.
Current version: 3.2.0
-
Version 3.2.0 — Dashboards and digests
New Features
- A dashboard gadget for Jira dashboards. It shows one project’s figures, including how many improvements need attention and how many are overdue, and the five improvements that have waited longest, with a link to the register. Only people who can browse the project see its figures.
- An email attention digest, sent weekly or daily after the daily check. Send the whole project’s list to up to ten people, and optionally send each owner an email listing only their own improvements.
- Preview the digest before it is sent. The settings page shows when the next digest will go and what happened to the last one.
- A site setting for Jira administrators, under Apps → Manage your apps → ImproveDesk → Configure. Digests are off until an administrator allows them, and the administrator decides whether a digest may include improvement titles.
- Publish improvement status onto linked Jira issues, so the issues can be found in Jira search (JQL). It is off by default and switched on per project. Switching it on publishes the register that is already there.
- Remove published status from a project’s issues on demand, once publishing has been switched off.
Improved Features
- Attention reasons now read the same everywhere: Overdue, Stale, Due for review and No owner.
- The settings page confirms a save beneath the Save button, where you pressed it.
Security Fixes/Patches
- None in this release.
Defect Fixes
- Checkboxes and radio buttons on the settings page no longer sit inside oversized boxes that pushed their labels out of line.
-
Version 3.1.0 — Foundation
New Features
- A continual improvement register for each Jira project, with a project-scoped reference for every improvement (such as CSI-1), a source, category, owner, sponsor and target date.
- Search the register by title, reference, tag or linked issue key, and filter it by status, category or overdue.
- Export the register as it is currently filtered to a CSV file.
- A nine-status lifecycle mapped to Plan–Do–Check–Act. An improvement can only be verified once it has been implemented, and work that is put on hold resumes to the status it left.
- A board view of the lifecycle.
- Prioritise with RICE scoring and a composite score that weighs forecast value, effort and risk. An unscored improvement is shown as unscored, never as zero.
- Record forecast, realised and cost figures for each improvement. Realised benefit counts only from verified and closed work.
- Measures with a baseline, target and actual value, including measures where lower is better, such as time to restore.
- A dashboard with the realisation rate, return on cost, net benefit, a trend over time and the list of improvements that need attention.
- A daily check that flags improvements that are overdue, stale, due for review or without an owner, shown as a banner above the register.
- Comments on each improvement, and a complete audit trail of every change, with who made it and when.
- Link existing Jira issues to an improvement, or create a delivery issue from it in one step.
- A panel on Jira issues showing the improvements each issue contributes to.
- Project settings for categories, services, scoring weights and review cadence, with a log of deleted improvements.
Improved Features
- None in this release.
Security Fixes/Patches
- None in this release.
Defect Fixes
- None in this release.
How updates reach you
ImproveDesk is a Forge app, so minor and patch releases are deployed by us and propagate to every installation without your administrators doing anything. Major upgrades, and any upgrade that adds a permission scope, need your Atlassian site administrator to approve them. The binding version of that, with the release cadence and the support commitments around it, is §9 of the Support and Maintenance Description.