Roadmap
Forge migration
The Issue Publisher is currently running on the Atlassian Connect platform. We plan to fully migrate to the new Forge platform before Atlassian stops to support the Connect platform in December 2026.
Forge manifest
Feature | Time-frame | Status |
|---|---|---|
Add a Forge manifest | July 2026 | DONE |
Migrate end user UI to Forge
Feature | Time-frame |
|
|---|---|---|
Migrate end user facing UI, i.e. the Publish Issue dialog, to Forge | August/September 2026 | COMING SOON |
Migrate admin UI to Forge
Feature | Time-frame | Status |
|---|---|---|
Migrate admin user facing UI to Forge:
| Q4 2026 | FUTURE |
Migrate post function
Feature | Time-frame | Status |
|---|---|---|
Migrate the | Q4 2026 | FUTURE |
Migrate event trigger
Feature | Time-frame | Status |
|---|---|---|
Use Forge triggers instead of Connect webhooks for the | Q4 2026 | FUTURE |
Automation action
Feature | Time-frame | Status |
|---|---|---|
Create a Jira Automation Action that triggers an operation | Q1 2027 | FUTURE |
Native Confluence connection
Feature | Time-frame | Status |
|---|---|---|
Admins can optionally install the Issue Publisher in Confluence enabling a native Confluence connection | Q1 2027 | FUTURE |