Idea: A Rovo-Powered AI Assistant & Proactive Guided Checklist for Marketplace App Submissions

Rovo Dev
, , , , , , ,
1

Hi everyone,

Having recently navigated the full lifecycle of building, testing, and submitting a commercial Atlassian Forge application connecting Jira to Atlassian Rovo agents and Model Context Protocol (MCP) tooling, I wanted to share some constructive observations on developer onboarding and propose an idea.

Building on Forge with modern Native UI Kit (@forge/react) and Node.js 22.x has been a solid experience, but moving from local code to a public Marketplace listing introduces several workflow hurdles where new vendors and independent developers easily get stuck:

Current Friction Points in the Submission Journey:

  1. Multi-Tab Security Questionnaire Draft States:
    In the Marketplace Security assessment, it’s possible to answer 16/16 questions across tabs like Partner - Extended, yet have the tab sit quietly in a “Not Submitted” draft state without an obvious global reminder before proceeding to app review.

  2. Context Switching Between Portals:
    Developers frequently balance three separate interfaces during submission:

    • Developer Console (developer.atlassian.com/console) for App IDs & environments.
    • Marketplace Vendor Console (marketplace.atlassian.com/manage) for profile, address, and listing versions.
    • Jira Service Management (ecosystem.atlassian.net) for review tickets and security clearance.

  3. Submission State & Metadata Lock Awareness:
    Once an app version transitions to SUBMITTED, metadata fields (like Documentation URLs) become read-only to protect reviewer integrity. First-time submitters often struggle to understand whether they should edit the listing or communicate updates directly through their review ticket.

The Proposal: A Rovo-Powered Marketplace Co-Pilot & Pre-Flight Checklist

Given the power of Atlassian Rovo, why not bring a native Rovo Agent directly into the Developer Console and Marketplace Management portals as an interactive DevEx Assistant?

A Rovo-powered Developer Co-Pilot could provide:

  • Interactive Pre-Flight Validation:
    Before hitting “Submit for Review”, Rovo could run a pre-submission sanity check:

    • “Your Partner Extended questionnaire has 16/16 answers saved, but hasn’t been submitted yet—submit now?”
    • “Your vendor profile is missing a physical street address—update before submitting?”
    • “Your documentation link points to an external article rather than an installation guide—would you like to review documentation requirements?”

  • Contextual Navigation & Guidance:
    A step-by-step interactive tour guide helping first-time builders map their Developer Space, Vendor Profile, and Cloudflare/external egress permissions in manifest.yml.

  • Automated Ticket & Review Explainer:
    When an app enters SUBMITTED or Waiting for Customer in ECOHELP review tickets, Rovo could explain exactly what the reviewer is asking for and how to reply.

Questions for the Community & Atlassian Team:

  1. How are other Forge and Marketplace builders handling the multi-step verification and submission workflow today?
  2. Would having an embedded Rovo assistant or automated pre-flight validator inside the Developer Console make your publishing process faster and less error-prone?

Curious to hear thoughts from fellow developers and the Atlassian Developer Relations team!