> ## 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. # Raise an issue from a failed Playwright test > Create a Jira, Linear, Asana, or monday.com issue from a failed or flaky Playwright test case, with the failure report and files attached. Raise an issue from a failed or flaky test case to file it in Jira, Linear, Asana, or monday.com. The issue carries a report of the failure, the test case's screenshots and error context, and any files you add. Raise Issue is available on TestDino **Team** and **Enterprise** plans. Before you start, connect at least 1 tool in **Settings → Integrations**: [Jira](https://docs.testdino.com/integrations/jira-playwright-test-failures.md), [Linear](https://docs.testdino.com/integrations/issue-tracking/linear.md), [Asana](https://docs.testdino.com/integrations/issue-tracking/asana.md), or [monday.com](https://docs.testdino.com/integrations/issue-tracking/mon.md). ## Open the issue panel **1. Open a failed test case** Open a test run and click a failed or flaky test case. **2. Click Raise Issue** Click **Raise Issue**. With more than 1 tool connected, pick the tool, for example **Report to Jira**. The issue panel opens on the right. The tool's own fields come first (for Jira: project, issue type, priority, assignee, labels). Each tool page lists them. ## Write the title TestDino fills the title as ` - `. Edit it as you like. ### Generate a title with AI Click **Generate with AI** next to the title. After a few seconds the list shows up to 3 suggestions under **AI suggestions**. Click one to use it. **AI suggested · Undo** appears under the title. Click **Undo** to go back to the title you had before. Titles are generated only when you click **Generate with AI**. Opening the panel does not generate anything. The button is hidden when AI is off for the project. To turn it on, open [Project Settings → AI Settings](https://docs.testdino.com/platform/project-settings.md#ai-settings) and switch on **Enable AI Insights** and **Test Case Recommendations**. ## Choose what the description includes Pick a **Report format**: | Section | Concise | Detailed | | :- | :-: | :-: | | **Summary**: 1 line saying what failed, where, and why | ✅ | ✅ | | **Error type and message** | ✅ | ✅ | | **TestDino run, commit and CI links** | ✅ | ✅ | | **Test details**: environment, branch, test run, runtime, attempts | | ✅ | | **Test steps**: every step of the final failed attempt | | ✅ | | **Console output** | | ✅ | **Detailed** is the default. TestDino remembers the format you picked last time in this browser. To pick sections yourself, open **Customize included context** and tick or untick them. A **Customized** badge appears. Ticking exactly the sections of a format selects that format again. ## Edit and copy the description The description is filled in from your report format. Switch to **Write** to edit it, and to **Preview** to see how it will look. Click **Open larger preview** to read it in a larger window. If you edit the description and then change the format or a section, TestDino asks **Update the description?**: * **Keep my edits** keeps your text. * **Update description** rebuilds the description from the report and replaces your edits. Click the copy icon (**Copy description**) to put the description on your clipboard. Pasted into Jira, Slack, or Google Docs, it keeps its headings, tables, and links. Pasted into a plain text field, it arrives as Markdown. On monday.com the description is plain text, so it copies as plain text. ## Add labels Labels are available for Jira and Linear. The **TestDino** label is added for you, so you can find every issue raised from TestDino. Remove it with its **×** if you do not want it. Click **Labels** to search the labels that already exist. To add a new one, type its name and click `Create ""`. | | Jira | Linear | | :- | :- | :- | | Labels you can pick from | Every label on your Jira site | The labels of the selected team | | A new label | Created when the issue is saved. Spaces become hyphens (`flaky checkout` becomes `flaky-checkout`) | Created in the team. The first issue in a team creates the **TestDino** label there | | Changing the team | | Resets the labels to **TestDino** | Some Jira issue types have no labels. For those, the field says **This issue type doesn't use labels** and the issue is created without labels. The same message appears when the issue type's fields did not load; close and reopen the panel to try again. ## Attach files The **Attachments** area lists every file the issue will carry. Drop files onto it, or click it to choose files. * **Error context**: when the test case has Playwright's error context, `error-context.md` is listed and marked **From this test**. It records the page at the moment the test failed. Remove it with its **×**, or untick **Error context** under **Customize included context**. * **Test case screenshots**: shown as thumbnails above the attachments. Click **×** on a thumbnail to leave that screenshot out. To leave out every screenshot, untick **Screenshots** under **Customize included context**. * **Your own files**: any file type, up to 10 MB each. An issue takes up to 25 files in total, counting the error context and test case screenshots. Your own files come first, and screenshots fill the space left. Executable and script files, such as `.exe`, `.sh`, `.ps1`, and `.js`, cannot be attached. If a test case screenshot cannot be read, or does not fit in the 25 files, TestDino shows a warning saying how many were left out, and still creates the issue. How the files appear in each tool: | Tool | Where files appear | | :- | :- | | Jira | The issue's attachments | | Linear | Images in the description, other files as links in the description | | Asana | The task's attachments | | monday.com | The item's update | ## Create the issue Click **Create**. The panel then shows: * **Issue created in** the tool name, and where it was filed, such as the Jira project or the Linear team * The issue key, with buttons to copy its link and to open it * The issue title * **Included**: the report format, `error-context.md`, the number of other files, and any file that was not attached, with the reason Click **Open in** the tool name to go to the issue, or **Done** to close the panel. ## Close without creating Click outside the panel, press Esc, or click **Cancel**. If you have not changed anything, the panel closes. If you have changed something, TestDino asks **Discard changes?**. Click **Keep editing** to go back to the panel, or **Discard** to close it. The panel cannot be closed while an issue is being created. ## Troubleshooting > **No Integration Found** > > The **Raise Issue** button reads **No Integration Found** and cannot be clicked when no issue tracker is ready to use. Connect a tool in **Settings → Integrations**. If Linear is connected, reconnect it there. > **Generate with AI is not shown** > > AI is off for the project. In [Project Settings → AI Settings](https://docs.testdino.com/platform/project-settings.md#ai-settings), switch on **Enable AI Insights** and **Test Case Recommendations**. > **AI titles are turned off for this project.** > > Check that **Enable AI Insights** and **Test Case Recommendations** are on in [Project Settings → AI Settings](https://docs.testdino.com/platform/project-settings.md#ai-settings), then reopen the panel. If they are on, write the title yourself and contact [support](https://docs.testdino.com/support.md). > **Couldn't generate titles. Try again** > > TestDino could not get suggestions. Click the message to ask again. > **Couldn't load existing labels** > > TestDino could not read your Jira labels. You can still type a label and create it. Close and reopen the panel to load the list again. > **This issue type doesn't use labels** > > The selected Jira issue type has no labels, or its fields did not load. Close and reopen the panel. If the message stays, the issue type has no labels: pick another issue type to add labels, or create the issue without them. > **Executable and script files can't be attached** > > Files such as `.exe`, `.sh`, `.ps1`, and `.js` cannot be attached to an issue. Put them in a `.zip` archive or share them another way. > **Larger than 10 MB** > > Each file can be up to 10 MB. Compress the file or share a link to it in the description. > **An issue takes up to … of your files** > > TestDino added the files that fit and named the ones it left out. Remove a file you do not need, or combine files into a `.zip` archive. > **A saved filter no longer finds new TestDino issues** > > Issue titles no longer start with `[TestCase]`. In Jira and Linear, filter by the **TestDino** label instead, for example `labels = TestDino` in Jira. ## Related > **[Jira](https://docs.testdino.com/integrations/jira-playwright-test-failures.md)** > > Connect Jira and the fields its issues use > **[Linear](https://docs.testdino.com/integrations/issue-tracking/linear.md)** > > Connect Linear and the fields its issues use > **[Asana](https://docs.testdino.com/integrations/issue-tracking/asana.md)** > > Connect Asana and the fields its tasks use > **[monday.com](https://docs.testdino.com/integrations/issue-tracking/mon.md)** > > Connect monday.com and the columns its items use This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.