v2.1.0

• Admin screen now requires global admin permission (descriptor roles-required + in-code check), independent of websudo
• REST writes require an authenticated, licensed user (401 for anonymous callers); the API-user restriction now also covers the new endpoints
• New GET /code/{issueKey} and DELETE /code/{issueKey}?url= REST endpoints
• Field values are validated at 255 characters (400 names the field), stored trimmed, and blank optional fields are treated as omitted; error responses carry JSON errorMessages bodies
• Racing upserts self-heal: duplicate rows for the same issue + URL are collapsed to the newest on write, and a client-supplied updated timestamp is honored
• All user-visible strings are internationalised; the notification toggle works without JavaScript; nullable fields no longer risk rendering as Velocity literals
• Faster issue views: existence checks use indexed queries only, and the duplicate tab-panel condition is gone
• Unit tests grew from 5 to 77, covering the REST authorization matrix, URL policy, email HTML escaping, and notification recipient selection

Full Changelog: v2.0.1...v2.1.0

v2.0.1

Production release for Jira Data Center 11.x (requires JDK 21 / Jira 11 runs Java 21 only). Completes the v2.0.0 migration, which could not install on Jira 11.

• Complete the Jakarta/Platform 8 migration: REST v2 security annotations, jakarta.inject, Jackson model binding, velocity method allowlist, platform-aligned AMPS/SAL/ActiveObjects
• Fix old pull requests not displaying after a Jira project key rename (issue key history lookup + null-safe sorting), and index the queries that run on every issue view
• Fix duplicate rows when updating a pull request stored before v1.0.3
• Harden the REST endpoint: payload validation, browse-permission check, real error codes instead of a false 201
• Escape notification emails, never render unsafe URL schemes as links, and add XSRF protection to the notification toggle and admin save

Upgrade notes: API callers now need browse permission on the target issue; name and an http(s) url are required; Jira 11 disables basic auth by default, so use a Personal Access Token for the REST endpoint.

Full Changelog: v2.0.0...v2.0.1

v2.0.0

Warning

Known-bad release — do not use. This version compiles but cannot install on Jira Data Center 11 (legacy REST v1 security annotation with an unresolvable OSGi import, javax.inject under Spring 6, javax.xml.bind model, no Velocity method allowlist) and ships no jar. Use v2.0.1 instead.

What's Changed

• Migrate plugin for Jira 11 compatibility by @thomasmo2002 in #5

New Contributors

• @thomasmo2002 made their first contribution in #5

Full Changelog: v1.0.3...v2.0.0

v1.0.4-RC1

Add support for Jira project key renames

v1.0.3

• Remove duplicate text in email notification subject

Full Changelog: v1.0.2...v1.0.3

v1.0.2

Prod release implementing user feedback:

• Sort by most recently updated
• Improve email notification
• Add to Jira Agile board view

Full Changelog: v1.0.1...v1.0.2

v1.0.2-RC1

• Sort by most recently updated
• Improve email notification
• Add to Jira Agile board view

Full Changelog: v1.0.1...v1.0.2-RC1

v1.0.1

Production-grade release

• Proper logging
• Configurable email notifications
• Global admin configuration
• Decent documentation

Full Changelog: v1.0.0...v1.0.1

v1.0.1-RC1

Add admin and user level enable/disable options.

Full Changelog: v1.0.0...v1.0.1-RC1

v1.0.1-SNAPSHOT

Adding user notification preferences and custom email notifications