Skip to main content
addly

Prepare four listings without inventing a single one.

This preflight turns current Atlassian Marketplace rules into separate local drafts for the four addly concepts. It prepares copy, visuals, policies, security, and distribution; it creates and publishes no listing.

Open the workspaceRead the official principles

A launch review, not a fictional storefront.

addly apps
4 independent drafts
Evidence
6 packets without an overall score
Data transfer
None — browser only

Everything left empty becomes visible work.

Only the name, host product, and placement already present in the addly catalog are prefilled. Forge app key, distribution, pricing, policies, scopes, assets, and real channels start empty.

Discovery

Name, tagline, summary, category, host product, and languages that are clear at first glance.

Visuals

One primary visual, exactly three highlights, and an optional short demo, all referenced and accessible.

Detailed description

Problem, expected outcomes, capabilities, and use cases connected in readable, verifiable copy.

Policies and support

Privacy, terms, documentation, support channel, and response expectation that can genuinely be published.

Privacy and security

P&S, scopes, data access, and pricing model described without invented badges, certifications, or prices.

Linking and distribution

Forge app key, Forge link, distribution, installation path, and clean-site test are documented.

Build the packet before opening the portal.

Each app keeps its own local save. The six sections use four distinct evidence states; no overall score turns missing items into an impression of maturity.

App to prepare

No data is sent. Real fields remain empty except the name, host product, and placement from the addly catalog.

Reading local storage…

Locally ready: 0 · Action required: 0 · Blocked: 0 · Not reviewed: 6. This count is not a publication score.

Discovery

Not reviewed

Name, tagline, summary, category, host product, and languages that are clear at first glance.

No name warning detected by the modeled rules.

Marketplace keywords — up to 4

Use only portal keywords that genuinely relate to the app’s capabilities or use cases.

Preparation evidence

Not reviewed

‘Locally ready’ is available only after content validation, owner assignment, source addition, and review date.

Items to address: 4

  • — The tagline still needs completion.
  • — The summary still needs completion.
  • — Select at least one category.
  • — Supported languages still needs completion.

Visuals

Not reviewed

One primary visual, exactly three highlights, and an optional short demo, all referenced and accessible.

Highlight 1 of 3

One precise outcome and a cropped 580 × 330 screenshot.

Highlight 2 of 3

One precise outcome and a cropped 580 × 330 screenshot.

Highlight 3 of 3

One precise outcome and a cropped 580 × 330 screenshot.

Optional video

Leave all three fields empty if no real video exists. If you reference one, the packet requires a duration from 1 to 29 seconds and a caption reference.

Preparation evidence

Not reviewed

‘Locally ready’ is available only after content validation, owner assignment, source addition, and review date.

Items to address: 17

  • — The app-icon reference still needs completion.
  • — The app-icon alternative text still needs completion.
  • — The 1840 × 900 primary visual still needs completion.
  • — The primary-visual alternative text still needs completion.
  • — The primary-visual caption still needs completion.
  • — The title for highlight 1 still needs completion.
  • — The summary for highlight 1 still needs completion.
  • — The 580 × 330 screenshot for highlight 1 still needs completion.
  • — The alternative text for highlight 1 still needs completion.
  • — The title for highlight 2 still needs completion.
  • — The summary for highlight 2 still needs completion.
  • — The 580 × 330 screenshot for highlight 2 still needs completion.
  • — The alternative text for highlight 2 still needs completion.
  • — The title for highlight 3 still needs completion.
  • — The summary for highlight 3 still needs completion.
  • — The 580 × 330 screenshot for highlight 3 still needs completion.
  • — The alternative text for highlight 3 still needs completion.

Detailed description

Not reviewed

Problem, expected outcomes, capabilities, and use cases connected in readable, verifiable copy.

Preparation evidence

Not reviewed

‘Locally ready’ is available only after content validation, owner assignment, source addition, and review date.

Items to address: 1

  • — The detailed description still needs completion.

Policies and support

Not reviewed

Privacy, terms, documentation, support channel, and response expectation that can genuinely be published.

Preparation evidence

Not reviewed

‘Locally ready’ is available only after content validation, owner assignment, source addition, and review date.

Items to address: 5

  • — The privacy policy still needs completion.
  • — The EULA or terms still needs completion.
  • — The documentation still needs completion.
  • — The support channel still needs completion.
  • — The support response expectation still needs completion.

Privacy, security, and pricing

Not reviewed

P&S, scopes, data access, and pricing model described without invented badges, certifications, or prices.

Preparation evidence

Not reviewed

‘Locally ready’ is available only after content validation, owner assignment, source addition, and review date.

Items to address: 4

  • — The privacy and security content still needs completion.
  • — The scope justification still needs completion.
  • — The data-access and processing description still needs completion.
  • — The license and pricing model still needs completion.

Linking and distribution

Not reviewed

Forge app key, Forge link, distribution, installation path, and clean-site test are documented.

Preparation evidence

Not reviewed

‘Locally ready’ is available only after content validation, owner assignment, source addition, and review date.

Items to address: 5

  • — The Forge app key still needs completion.
  • — The Forge-to-listing link evidence still needs completion.
  • — The distribution evidence still needs completion.
  • — The validated installation path still needs completion.
  • — The clean-site test still needs completion.

JSON keeps a snapshot of the draft; import strictly checks structure and populated fields within a 1 MB limit. Markdown preserves human-readable review. No button in this workspace creates, links, submits, or publishes an Atlassian Marketplace listing.

Three sources, one authority that may change.

The workspace paraphrases the documents alongside it. The current Atlassian portal and documentation remain authoritative during preparation and official review.

Marketplace listing principlesJune 4, 2026Text limits, three highlights, visuals, outcomes, trust, support, brand, and accessibility.Create the listing and link the Forge appMay 19, 2026Metadata, policies, P&S, scopes, pricing, app key, distribution, and clean-site installation.Marketplace categories and keywordsCurrent official sourceUp to two categories and four keywords aligned with real capabilities and use cases.

This workspace makes no claim in place of evidence.

  • No Atlassian Marketplace listing is presented as created, submitted, approved, or published.
  • No addly app is presented as distributed, installable, priced, or available for trial.
  • No real asset, badge, policy, scope, data processing, or support channel is prefilled.
  • A ‘Locally ready’ state means only that this browser contains a complete, sourced, dated, and assigned packet.
  • Drafts, imports, and exports remain local; nothing is sent to addly, Atlassian, or a third party.

Open the portal only when the sources exist.

Export the active draft, have every packet validated by its owner, then compare it one last time with the current Atlassian screens and rules.

Resume the workspacePrepare partner security