2.5.0 — Jira publishing and ELS reminders
New Features
- Publish to Jira: a site administrator can switch on publishing so each service’s status shows on its linked Jira issue and can be searched in Jira. Only status is shared: readiness, gate outcome, plan health, overdue task count and early-life support state. Names, notes and gate conditions are never sent.
- Publishing is off until you turn it on. Switching it on covers every service in every project, and the admin page says so above the switch.
- Turning publishing on brings the services you already have up to date straight away, up to 50 at a time. The admin page tells you if some remain, and the daily check finishes the rest.
- The admin page reports how many services have no linked issue, so an empty search result is explained rather than mysterious.
- Remove published state: a site administrator can delete everything the app has published to Jira, in batches, at any time, including after a licence has lapsed.
- Early-life support (ELS) reminders: the service owner is mentioned in a comment on the linked Jira issue 14 days before the ELS period ends, and again if it ends without sign-off. Jira’s own notifications deliver it.
- Each ELS reminder is sent once per period. Extending the period earns a new pair of reminders.
- Services that have an ELS period ending or ended but no linked issue are counted on the portfolio, so nobody is left without a reminder unnoticed.
- The ELS tab shows where each reminder stands.
Improved Features
- Published status is checked and repaired daily, so a change that failed to reach Jira the first time does not stay wrong.
- Publishing never blocks your work: if Jira cannot be reached, your change is still saved.
- Owners are shown by name, not by account ID, in the edit-service dialog and on task rows.
- Plan health follows the target go-live date: change the date and a plan can move to or from Late straight away.
- Validate JQL now catches a misspelt field or function and shows Jira’s reason, both when you validate an incident query and when you save it.
- The Extend and Sign-off dialogs explain what is missing next to the field, instead of leaving the button greyed out.
- The portfolio shows “Updating…” while it refreshes, so a slow load no longer looks like an empty list.
- A daily check keeps each service in step with Jira: it refreshes overdue task counts and plan health that changed overnight, and reports linked issues Jira can no longer find.
Defect Fixes
- A Jira issue can no longer be linked to two services at once.
- A service linked to an issue that has since been deleted now says so, and the link can be cleared. The same applies to an issue linked from a plan task, which shows “not found” with a ✕ to remove it.
- A service keeps its place in its project when the project’s key is renamed. The daily check repairs it within a day.
- The publish and removal reports now name issues Jira cannot find instead of counting them as refused.
- Early-life support can only be started for a service that has a Go or Conditional Go decision.
- Archiving or restoring a service now needs project administrator permission.