> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testdino.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Jira Forge App

> Install the TestDino Forge app to view linked test cases, runs, sessions, and releases inside Jira issues.

export const VideoSchema = ({name, description, thumbnailUrl, uploadDate, duration, contentUrl, embedUrl}) => {
  const schema = {
    "@context": "https://schema.org",
    "@type": "VideoObject",
    name,
    description,
    thumbnailUrl,
    uploadDate,
    ...duration ? {
      duration
    } : {},
    ...contentUrl ? {
      contentUrl
    } : {},
    ...embedUrl ? {
      embedUrl
    } : {},
    publisher: {
      "@type": "Organization",
      name: "TestDino",
      logo: {
        "@type": "ImageObject",
        url: "https://docs.testdino.com/logo/light.svg"
      }
    }
  };
  return <script type="application/ld+json" dangerouslySetInnerHTML={{
    __html: JSON.stringify(schema)
  }} />;
};

<VideoSchema name="TestDino for Jira Forge App" description="How to install the TestDino Forge app and view linked test cases, runs, sessions, and releases inside Jira issues." thumbnailUrl="https://i.ytimg.com/vi/3YOoxNS8rxM/maxresdefault.jpg" uploadDate="2026-06-11T00:00:00+00:00" contentUrl="https://www.youtube.com/watch?v=3YOoxNS8rxM" embedUrl="https://www.youtube.com/embed/3YOoxNS8rxM" />

The TestDino for Jira Forge app links TestDino test cases, manual runs, exploratory sessions, and releases to Jira issues. You create the link from TestDino; the app shows the linked items in a panel on the matching Jira issue, so testing progress is visible without leaving Jira.

The app pairs with the [Jira Issue Integration](/integrations/jira-playwright-test-failures). That integration connects Jira to TestDino and creates and links issues from your test entities. The Forge app is the Jira-side view of those linked items. Use both together.

<Warning>
  **Warning**

  Jira Cloud only. The app runs on Atlassian Forge and installs from the Atlassian Marketplace.

  Connecting a TestDino project requires a **Team** or **Enterprise** plan.
</Warning>

<iframe className="w-full rounded-lg h-[500px]" src="https://www.youtube.com/embed/3YOoxNS8rxM" title="Jira Forge App demo" frameBorder="0" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share; embedding" referrerPolicy="strict-origin-when-cross-origin" allowFullScreen />

## Quick Reference

| Task                    | Where                 | Link                                           |
| :---------------------- | :-------------------- | :--------------------------------------------- |
| Install app             | Atlassian Marketplace | [Install](#install-the-app)                    |
| Connect a project       | App dashboard         | [Connect](#connect-a-testdino-project)         |
| Link a test entity      | From TestDino         | [Link items](#link-test-entities-to-an-issue)  |
| View linked items       | Jira issue panel      | [Issue panel](#link-test-entities-to-an-issue) |
| Track releases          | Jira issue panel      | [Releases](#track-releases-and-sessions)       |
| View connected projects | App dashboard         | [Dashboard](#project-dashboard)                |

## What You Can Link

The panel surfaces four TestDino entity types linked to a Jira issue, each on its own tab. The status shows inside the issue, so the Jira owner sees test progress without opening TestDino.

| TestDino entity | What it tracks                           | Status shown in Jira                                       |
| :-------------- | :--------------------------------------- | :--------------------------------------------------------- |
| Test case       | A single test case                       | Active, Draft, Deprecated, Retired, Under review, Rejected |
| Manual run      | A test case result in a manual run       | Untested, Passed, Failed, Blocked, Skipped, Retest         |
| Session         | An exploratory testing session           | Findings status                                            |
| Release         | A TestDino release and its testing scope | Not started, In progress, Completed                        |

## Prerequisites

* A TestDino project with test data ([Getting Started](/getting-started))
* A Jira Cloud site with permission to install Marketplace apps
* Jira project access for the issues you want to link

## Install the App

<Steps>
  <Step title="Open the Marketplace listing">
    Go to the <a href="https://marketplace.atlassian.com/apps/320968797/testdino-for-jira?hosting=cloud&tab=overview" target="_blank" rel="noopener noreferrer">TestDino for Jira listing <Icon icon="arrow-up-right-from-square" size={12} /></a> on the Atlassian Marketplace.
  </Step>

  <Step title="Install to your site">
    Click **Get it now** and select the Jira site to install to. The app is free now. A Jira admin approves the install if you lack admin rights.
  </Step>

  <Step title="Approve the scopes">
    The app requests read access to issues and app storage. It reads issue context and does not modify your Jira issues.
  </Step>
</Steps>

## Connect a TestDino Project

Pick which TestDino projects appear in Jira from the app dashboard. Clicking **Connect** opens the TestDino connection flow, which generates the access token and saves it to the Forge app for you. There is no token to copy or paste.

<Steps>
  <Step title="Open the app dashboard">
    In Jira, go to **Apps → TestDino** to open the dashboard, then click **Connect / Disconnect projects**.

    <img src="https://tdstorageus.blob.core.windows.net/public/docs/integrations/issue-tracking/jira-forge-app/jira-forge-dashbooard-header.webp" alt="TestDino Forge app dashboard header with Open TestDino and Connect / Disconnect projects buttons" />
  </Step>

  <Step title="Select projects to connect">
    A TestDino window opens listing your organizations and their projects. Tick the projects to link to this Jira site. Use **Select All** or **Clear** per organization. Already-connected projects show a **Connected** badge. Some organizations may require a plan upgrade to connect.

    <img src="https://tdstorageus.blob.core.windows.net/public/docs/integrations/issue-tracking/jira-forge-app/jira-forge-project-selection-connection.webp" alt="Connect Your Project to TestDino's Jira app window listing organizations and projects with access checkboxes" />
  </Step>

  <Step title="Apply the selection">
    Click **Apply** to generate tokens and link the selected projects. TestDino confirms with a count of connected projects.

    <img src="https://tdstorageus.blob.core.windows.net/public/docs/integrations/issue-tracking/jira-forge-app/connection-flow-project-connected.webp" alt="Confirmation showing projects connected, with a Done button to close the window" />
  </Step>

  <Step title="Return to Jira">
    Click **Done** and close the window. The Jira app updates automatically and the dashboard shows the connected projects with their entity counts.
  </Step>
</Steps>

<Note>
  **Note**

  The connection flow generates a project access token per selected project and saves it to the Forge app. You manage these tokens by reconnecting or disconnecting projects here, not by copying keys.
</Note>

## Link Test Entities to an Issue

Linking starts in TestDino, not in Jira. A TestDino test case, release, session, or manual run result has a **create and link Jira issue** option. Once linked, the item shows on the matching Jira issue, and the Forge app renders it in the issue panel.

<Note>
  **Note**

  Linking from TestDino requires the Jira OAuth integration connected under **Settings → Integrations → Jira**. See the [Jira Issue Integration](/integrations/jira-playwright-test-failures#connect-jira-to-testdino) page for that setup. The Forge app provides the Jira-side view of the items you link there.
</Note>

<Steps>
  <Step title="Link from a TestDino entity">
    In TestDino, open a test case, release, session, or manual run result and use its option to create and link a Jira issue. The link records the issue on both sides.

    <img src="https://tdstorageus.blob.core.windows.net/public/docs/integrations/issue-tracking/jira-forge-app/create-and-link-jira-issue.webp" alt="TestDino test entity showing the create and link Jira issue option" />
  </Step>

  <Step title="Add the TestDino panel to the issue">
    Open the linked Jira issue. Click the **apps** (gear) button near the issue title, then select **TestDino** to add the panel.

    <img src="https://tdstorageus.blob.core.windows.net/public/docs/integrations/issue-tracking/jira-forge-app/jira-issue-panel-gear-button.webp" alt="Jira issue apps menu showing TestDino and Add apps options under the gear button" />
  </Step>

  <Step title="View linked items in the panel">
    The **TestDino** panel opens with tabs for **Test Cases**, **Releases**, **Manual Runs**, and **Sessions**. Each tab lists the items linked to this issue. The panel shows a last-synced time with a refresh button.

    <img src="https://tdstorageus.blob.core.windows.net/public/docs/integrations/issue-tracking/jira-forge-app/jira-forge-issue-panel.webp" alt="TestDino panel inside a Jira issue with Test Cases, Releases, Manual Runs, and Sessions tabs and a last synced refresh control" />
  </Step>
</Steps>

## Track Releases and Sessions

Releases and sessions give the Jira owner a view of testing scope beyond a single test case.

| Link type | What the Jira owner sees                                             |
| :-------- | :------------------------------------------------------------------- |
| Release   | Release readiness, testing progress, and bugs tied to the release    |
| Session   | Exploratory findings, notes, and defects captured during the session |

From TestDino, link a release to an epic or a tracking issue to follow readiness as the release is tested. Link a session to the issue that prompted the exploratory work, so findings and defects stay attached to that issue. Both appear in the issue panel under the **Releases** and **Sessions** tabs.

## Project Dashboard

The dashboard aggregates totals across all connected projects, then breaks them down per project. The **Linked** count under each total is how many of that entity are attached to a Jira issue.

<img src="https://tdstorageus.blob.core.windows.net/public/docs/integrations/issue-tracking/jira-forge-app/jira-forge-dashboard.webp" alt="TestDino Forge app dashboard showing Test Cases, Releases, Manual Runs, Sessions, and Projects totals with Linked counts and connected project cards" />

| Card        | Shows                                      | Linked count means                  |
| :---------- | :----------------------------------------- | :---------------------------------- |
| Test Cases  | Total test cases across connected projects | Test cases attached to a Jira issue |
| Releases    | Total TestDino releases                    | Releases attached to a Jira issue   |
| Manual Runs | Total manual run executions                | Runs attached to a Jira issue       |
| Sessions    | Total exploratory sessions                 | Sessions attached to a Jira issue   |
| Projects    | Connected TestDino projects                | —                                   |

## Troubleshooting

<AccordionGroup>
  <Accordion title="TestDino panel not visible on the issue" icon="eye-slash">
    * Add it: click the **apps** (gear) button near the issue title and select **TestDino**
    * Confirm the app is installed and a TestDino project is connected in **Apps → TestDino**
  </Accordion>

  <Accordion title="Panel shows no linked items" icon="list">
    * Items are linked from TestDino, not from the panel. Link a test case, release, session, or manual run result to the issue in TestDino first
    * Linking from TestDino needs the Jira OAuth integration in **Settings → Integrations → Jira**. See [Jira Issue Integration](/integrations/jira-playwright-test-failures)
    * Click the refresh button on the panel to pull the latest links
  </Accordion>

  <Accordion title="Linked item shows no status" icon="circle-exclamation">
    * Status reflects TestDino data. Confirm the linked test case, run, or session has results in TestDino
    * Use the refresh button on the panel to re-sync
  </Accordion>

  <Accordion title="Install blocked by Jira admin" icon="lock">
    * Marketplace installs need admin approval on most sites. Request approval from a Jira admin, or have them install from the Marketplace listing
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Jira Issue Integration" icon="bug" href="/integrations/jira-playwright-test-failures">
    Create Jira issues from failed or flaky tests inside TestDino
  </Card>

  <Card title="Generate API Keys" icon="key" href="/guides/generate-api-keys">
    Project access tokens for CLI uploads and the API
  </Card>

  <Card title="Manual Testing" icon="circle-play" href="/test-management/manual-testing/overview">
    Releases, manual runs, and sessions you can link to Jira
  </Card>

  <Card title="All Integrations" icon="puzzle-piece" href="/integrations/overview">
    Issue tracking, CI/CD, and communication connections
  </Card>
</CardGroup>