Private Connect → Forge assessment
Initial structural review of a private Atlassian Connect application. This deliverable identifies implementation decisions requiring investigation, not guaranteed feature equivalence or a production cutover.
Feature inventory
| Connect module type | Review category | Count |
|---|---|---|
| jiraCustomFieldTypes | Custom field continuity | 1 |
| jiraIssuePanels | Jira user interface | 1 |
| jiraWorkflowValidators | Workflow continuity | 1 |
| webhooks | Event delivery | 1 |
Technical findings
| Priority | Finding / next check | Area |
|---|---|---|
| REVIEW | CONNECT JWT MIGRATION Plan the transition from Connect JWT and tenant secrets to Forge OAuth and permission checks. | security |
| REVIEW | CONNECT UNINSTALL BEHAVIOR CHANGED Since September 2026, Connect uninstalled hooks are suppressed during Forge-only upgrades. Validate cleanup and migration state transitions separately; do not interpret every upgrade as a real tenant uninstall. | lifecycle |
| REVIEW | FORGE SCOPE UPGRADE IMPACT Native Forge modules need explicit classic or granular scopes; verify privilege elevation, major-version behavior and any admin approvals against current Atlassian scope guidance. | security |
| REVIEW | INSTALL LIFECYCLE Document tenant install/uninstall and migration semantics; no automatic lifecycle parity. | lifecycle |
| REVIEW | MODULE REVIEW Check a matching Forge surface and verify user-visible behavior on a consented test site. | modules |
| REVIEW | MODULE REVIEW Events must be remapped and processed with Forge permissions and retry semantics. | modules |
| REVIEW | MODULE REVIEW Locked custom field identity, schema, data and migration listener may need separate treatment. | modules |
| REVIEW | MODULE REVIEW Verify workflow validator parity and failed-transition handling. | modules |
| REVIEW | POTENTIAL DATA OR WORKFLOW MIGRATION Record the current behavior, stored values, settings and acceptance tests before upgrading. | data |
| REVIEW | POTENTIAL DATA OR WORKFLOW MIGRATION Record the current behavior, stored values, settings and acceptance tests before upgrading. | data |
| REVIEW | REMOTE BACKEND DEPENDENCY Assess whether backend code can move to Forge functions, Forge Remote or remain external by design. | hosting |
| REVIEW | USER IMPERSONATION Validate user identity, consent and permissions before porting impersonated operations. | security |
Acceptance plan — next scope
- Review the real Connect module inventory, tenant events and authentication controls
- Verify existing app identity, custom-field data, entity properties and workflow parity
- Map actual Forge capabilities, scopes and costs with official documentation
- Specify staging tests, data verification, rollback and owner go/no-go decision