Move a Claude investigation into Jira

To move work from Claude to Jira, paste the checked decision or reproduction steps into the ticket’s description, then attach the full conversation as a PDF. Keep a Markdown copy too when teammates need a text record. These instructions cover Jira Cloud.

Choose what belongs in the description

Start with the bug, expected behavior, and next step. Keep rejected suggestions in the transcript so the assignee doesn’t have to untangle them.

Label an unconfirmed explanation “Suspected cause” and a change awaiting review “Proposed fix.” Record the reproduction steps only after testing them yourself.

For a feature request, use intended behavior and acceptance criteria. Put a longer specification or runbook in a Confluence page and link it from the ticket.

Paste the useful excerpt into Jira Cloud

For a short answer, select and copy the relevant text in your browser.

1. Open the Jira ticket you want to update.
2. Edit its Description field.
3. Paste the excerpt into the description.
4. Apply headings to sections such as “Steps to reproduce” and “Expected result.”
5. Read the saved description to catch missing lines or broken lists.

Jira’s editor accepts pasted raw Markdown in rich text fields. It supports headings, lists, and code blocks, and converts supported syntax as you type. You can also open a Markdown file in a text editor and copy just the relevant passage from it.

In desktop Chrome, DocMyChat’s export icon under a Claude reply offers Copy, labeled for Google Docs. It places formatted text and Markdown on the clipboard. Use it for one finished response, then inspect the result in Jira, especially around tables.

Keep code, tables, and screenshots readable

Put stack traces, sample requests, and queries into code blocks. Type /code in the description to insert a Code snippet, then paste the code and select its language. Jira’s code controls let you adjust wrapping and line numbers. Compare indentation and punctuation with the source.

Use columns for the test input, expected result, and actual result. If a pasted table still shows pipes and separator dashes, type / and insert a table through Jira’s quick-insert menu. Copy the values into its cells under the correct headings.

DocMyChat’s Markdown export contains image links that open while you’re signed in to claude.ai. Attach essential screenshot files separately so teammates can open them with the ticket.

Attach the conversation as a separate record

Use a PDF to keep prompts, corrections, and the final answer together. DocMyChat exports the branch shown on screen, so open the version you intend to preserve.

1. Open the conversation on claude.ai in desktop Chrome.
2. Click Export beside Share.
3. Choose PDF.
4. Select Save as PDF in Chrome’s print dialog.
5. Give the file a recognizable name, such as BILL-214_2026-11-03_transcript.pdf.
6. Drag the saved file onto the open Jira ticket.

The PDF guide covers print settings. Before uploading, inspect large screenshots and wide tables. The export date records when you saved it, which may differ from the investigation date.

For a text record, choose Markdown from the export menu. Package the downloaded .md file in a ZIP with your computer’s archive command, then attach it. Jira’s attachment guide lists PDF and ZIP as supported file types. Keep a PDF too for colleagues who want a reading copy.

As of November 2026, Atlassian’s attachment administration guide lists a default limit of 1 GB per file and a maximum setting of 2 GB. Your site’s configured Attachment Size applies. Ask your administrator for that value if Jira rejects an upload for being too large.

Example: a duplicate invoice investigation

Suppose a staging test accepts an invoice number with surrounding spaces despite an existing matching invoice. Keep the tested reproduction steps separate from the suspected cause and proposed fix.

Summary: Invoice creation accepts a duplicate number with surrounding spaces.

Environment: Staging, build 2026.11.03. Test customer C-104 already has invoice INV-0081.

Steps to reproduce:

1. Start a new invoice for customer C-104.
2. Enter INV-0081, including the leading and trailing spaces.
3. Save the invoice.

Actual result: A second invoice is created for the same customer.

Expected result: Reject the duplicate after trimming surrounding spaces, following the agreed invoice-number rule.

Suspected cause: The duplicate check may compare the original input before trimming it. Trace the validation and storage steps to confirm where normalization happens.

Proposed fix: Apply the agreed normalization before the duplicate check and before storage.

Tests to run: An exact duplicate and a duplicate with surrounding spaces should both be rejected. A new number should still save.

Attachment: BILL-214_2026-11-03_transcript.pdf, containing the investigation and the proposed change.

Update the cause once code inspection establishes it. After implementing the fix, record which regression cases passed before marking the bug resolved. The developer workflow guide covers saving accompanying files and decisions.

Review the handoff

Read the ticket without opening the transcript. A teammate should know what to reproduce, what outcome is expected, and what still needs investigation. Add the relevant build or commit reference, and make sure the attached copy also omits credentials or customer details the ticket’s readers don’t need.

Jira’s Rovo can draft or edit descriptions, and the Atlassian MCP connector lets Claude work with Jira within your existing permissions and admin settings. DocMyChat provides a file or clipboard copy for you to add yourself, without automatic sync.

Questions