RevloBetaDocs
    Back
    Atlassian Jira Integration

    Jira Integration

    Connect your Atlassian account to automatically generate Jira Epics, Stories, and Sub-tasks directly from your Revlo project using AI.

    Authentication MethodOAuth 2.0 (3LO)

    Revlo uses Atlassian's OAuth 2.0 3-Legged flow to securely connect to your Jira account. No API tokens or manual setup required — just authorize and start generating tickets.

    How It Works

    1. AI Analysis

    Claude analyzes your project's source files, components, and original prompt to understand the full scope of your application.

    2. Ticket Planning

    AI generates a structured plan: 1 Epic covering the project, 3–6 User Stories per feature, and 1–3 technical Sub-tasks per Story.

    3. Jira Creation

    Tickets are created in your chosen Jira project with proper hierarchy: Epic → Stories → Sub-tasks, all linked correctly.

    How to Connect

    1. Navigate to /integrations in your Revlo dashboard
    2. Find the Atlassian integration card and click Connect
    3. A popup window opens and redirects you to Atlassian's authorization page
    4. Select the Jira site(s) you want Revlo to access and click Accept
    5. The popup closes and Atlassian is now connected
    Popup-based OAuth

    Authorization opens in a popup so you never leave the integrations page. The connection completes automatically when you accept.

    Generating Jira Tickets

    1. Open a project workspace
      Go to any project you've built with Revlo.
    2. Click the "Jira" button in the toolbar
      The button is visible for Starter, Pro, and Business plan users.
    3. Select a Jira project
      Choose which Jira board/project should receive the tickets. Use the search box if you have many projects.
    4. Click "Generate Jira Tickets"
      AI analyzes your codebase and creates all tickets. This usually takes 15–30 seconds.
    5. View in Jira
      A success screen shows how many tickets were created. Click "View in Jira" to open the Epic directly.

    Ticket Structure

    Epic

    One epic per project generation covering the entire application scope.

    Stories (3–6)

    User stories written as "As a user I want to..." based on distinct features and screens. Each story includes acceptance criteria.

    Sub-tasks (1–3 per Story)

    Technical implementation tasks linked under each Story — covering frontend, backend, and integration work.

    Supported Jira Project Types

    Next-gen (Team-managed)

    Full support with native parent-child hierarchy. Epic → Story → Sub-task links work out of the box.

    Classic (Company-managed)

    Supported via Epic Link custom field (customfield_10014). Revlo automatically detects the project type and uses the correct linking method.

    Troubleshooting

    Session expired

    If the Jira button shows "Session expired", your Atlassian OAuth token has expired.

    Click Reconnect Atlassian to re-authorize. This takes about 10 seconds.

    No Jira projects found

    This means your Atlassian account has no Jira projects, or the connected site doesn't have any.

    • Make sure you have at least one Jira project in your Atlassian site
    • Try disconnecting and reconnecting to refresh your site list
    Jira button not visible

    The Jira button in the workspace toolbar is only available on Starter, Pro, and Business plans. Upgrade your plan to access this feature.

    Issue type errors

    Revlo dynamically detects the available issue types in your Jira project and maps Epic → Story → Sub-task accordingly. If your project uses custom issue type names (e.g. "Feature" instead of "Story"), Revlo will fall back to the closest matching type automatically.

    Ready to connect Atlassian?
    Head to the Integrations page and connect in one click.
    Atlassian OAuth Docs Open Integrations