Forge ReadyWill your Forge app pass Atlassian Marketplace review - and what does the next version cost you in review and admin consent?

How it works - and what is sourced

The checks follow the skill's six rules and its sections on architecture, payment, submission, Connect migration, versions and keeping the listing. The manifest is read by a small YAML subset parser written for manifest.yml (nested maps, lists, quoted strings, block scalars, comments, keys such as jira:issuePanel) or by JSON.parse, and every parse error names its line. Each scope is classed by its syntax only, from a fixed set: Connect (read:connect-jira), Rovo (read:chat:rovo), app storage and data (storage:app, report:personal-data), admin (manage:*), granular (read:issue:jira), classic (read:jira-work) or other. Egress comes from permissions.external.fetch, backend and client, as strings or objects with address, category and inScopeEUD; "*" and "*.domain" are wildcards.

The major-version diff compares the two manifests: every added scope, egress domain, remote or auth provider, an inScopeEUD false to true flip, a changed egress category, a changed or removed auth provider and a licensing toggle is a major; removing egress is minor; removing a scope is still major; removing a remote is left unclassified. When the previous manifest carries app.connect.key, a moved Connect baseUrl, a changed auth provider or a licensing toggle fails the first-Forge-version rule. A moved remote baseUrl counts as new egress - a reading of the rule, not a quote. The architecture ladder puts Forge UI with remotes first and a 3LO listing first only when the manifest declares no UI module and buyers run no security review; the trust ladder promotes AEC when buyers run a vendor security review; the payment model is resolved from the revenue and stage answers. The timeline counts three weeks per round† from today by your browser's clock, with one returned round.

The fixed manifest enables licensing when the page fails revenue_licensing and, with a plan, removes the scopes the plan drops and replaces a wildcard egress only with concrete domains the plan names that your input already contains - it never invents a domain, and a wildcard it cannot replace stays and is named in the change list. A saved app keeps a snapshot of its checks, so reopening it shows what changed since you saved it; mark it resubmitted and the next fixes run carries the previous round's fixes with the plan.

Every Atlassian figure the skill quotes carries a dagger: Connect support ends on 31 Jan 2027†; a major is reviewed in 5-10 business days†; the annual price is 10 times monthly†; old prices hold for 60 days†; the partner share is 83%† for Forge-only apps, 75%† otherwise, and 100% until $1M lifetime Forge revenue†; plan three weeks per round† (official figures range from one week to 15 business days†); cloud Critical fixes within 10 days†, High within 4 weeks†, badges removed and the app hidden after 15 days†; silence for 90 days† hides the app; incidents are reported within 24 hours†; a version ships every 18 months†. † verify against current Atlassian developer docs, because Atlassian changed its framework, badge and revenue-share rules within one year.