Totesoft Documentation

Shared Atlassian Marketplace Submission Checklist

Partner and listing setup

• Partner profile and identity verification are complete.
• Vendor name is consistently Totesoft LLC.
• App name, app key, and Marketplace product record match the production Forge app.
• Distribution is configured for the intended public or private Marketplace state.
• The Forge app is linked to the correct Marketplace listing.

Listing content

• Summary stays within the current Marketplace character limit.
• Three highlights are factual and supported by the production build.
• Long description stands alone and states important limitations.
• Category and keywords are selected in Partner Portal.
• Logo, banner, and screenshots meet current asset specifications.
• Screenshots use synthetic test data and no customer site URL, email, user name, issue content, or commercial values.

Public links

• Documentation URL works without login.
• Support URL and email work.
• App-specific privacy notice works.
• End-user agreement selection and provider-specific terms are complete.
• General company privacy policy is current.
• Security-reporting contact is published.

Permissions and privacy

• Every scope in manifest.yml has a plain-language justification.
• No unused scope remains.
• External egress and remote backends are verified from the production manifest and code.
• Current production logs are reviewed with debug variables both off and on.
• Stored record schemas are documented.
• Uninstall/reinstall behavior is tested and the hosted-storage retention answer matches current Atlassian rules.
• GDPR role, DPA availability, CCPA, and other legal answers are approved by an authorized owner.
• Privacy and Security tab answers are saved with release evidence.

Release validation

• Clean-clone build succeeds.
• forge lint succeeds.
• Automated tests succeed.
• Fresh installation succeeds on a clean Jira Cloud test site.
• Existing installation upgrade and consent flow succeeds.
• App works under all declared license states.
• Rate limiting and permission failures produce actionable customer messages.
• Uninstall and reinstall behavior is documented.
• Marketplace copy, customer docs, legal pages, and code all describe the same release.