Run your final checks, submit your app for Atlassian review, respond to any feedback, and verify everything works once approved.
OUTCOME: By the end of this phase, you should have:
What to do
|
Why this matters
Most review rejections come from avoidable gaps like incomplete listing fields, missing policy links, or install failures on a clean site. A final pass against the approval guidelines avoids such gaps. | Resources |
What to do
|
Why this matters
Review timelines vary. Setting up notifications early ensures you don't miss a reviewer's question and can respond promptly throughout the process. |
What to do
|
Why this matters
Fast, thorough responses keep your review moving. Documenting what reviewers flagged saves you from repeating the same issues on future version submissions. |
What to do
|
Why this matters
Approval doesn't guarantee everything works for real customers. Verifying install links, documentation URLs, and the end-to-end purchase flow before announcing your app ensures a smooth experience from day one. |
Rate this page: