# QA Bug Report: Same Issue on Desktop and Mobile? _2026-11-05 • 7 min read • By clip.qa team_ **Category:** Engineering **Keywords:** QA bug report: same issue on desktop and mobile, one bug or two; Bing: qa bug report combine desktop mobile same issue separate bugs best practice — 4 impressions, average position 3; Google: mobile app bug report error validation expected actual result quantity unavailable — 3 impressions, average position 3 --- ## Overview If the same defect appears on desktop and mobile, file one report when the behavior and likely fix are shared, then document separate reproduction steps and results for each platform. File separate reports when the symptoms, cause, owner, or fix differ. When the root cause is not yet known, create one report per distinct observation and link them as related until triage confirms whether they share a fix. --- ## Introduction

If the same defect appears on desktop and mobile, file one report when the behavior and likely fix are shared, then document separate reproduction steps and results for each platform. File separate reports when the symptoms, cause, owner, or fix differ. When the root cause is not yet known, create one report per distinct observation and link them as related until triage confirms whether they share a fix.

## Should the same desktop and mobile bug be one report or two? Ask whether a developer would investigate and fix both platform behaviors in the same change. If yes, one report can keep the shared defect together. If each platform needs different diagnosis or code changes, split the reports so each has its own owner, status, and verification. Do not decide based only on a similar screenshot or error message. A desktop layout defect and a mobile layout defect can look alike while coming from different components. Conversely, one shared API validation problem may produce visibly different symptoms in a browser and an app. Use this rule of thumb: What triage findsHow to fileSame behavior, same underlying cause, one fixOne issue with separate desktop and mobile reproduction sectionsSame symptom, different cause or different fixSeparate issues with platform-specific detailsCause is not known yetRecord each reproducible observation; link the reports as related and merge only after evidence supports itOne platform is unaffectedKeep the issue focused on the affected platform and note where you tested without reproducing it This is a triage heuristic, not a universal tracker rule. The aim is to avoid both duplicated work and one oversized ticket that hides different defects. ## When should you split a cross-platform bug report? Create separate bug reports when any of these conditions changes the work: Different trigger: the desktop bug needs a keyboard sequence, while mobile needs a gesture or device state. Different result: the same action causes a crash on one platform but a wrong value or layout on another. Different likely component: browser code, native code, or platform-specific styles appear to be responsible. Different severity or impact: one platform blocks a core task, while the other has a cosmetic issue. Different owner or release: separate teams or release trains need to fix and verify each platform independently. Independent workaround: users can avoid one platform’s issue without avoiding the other’s. Split even when the reports seem related if combining them makes it difficult to assign, prioritize, or verify either fix. Link the issues and state what evidence connects them. If Jira is your tracker, Atlassian supports issue links such as “duplicates” and “relates to”; link types can depend on site configuration. ## What details should each platform's reproduction steps include? Write the shared context once, then list exact steps and results separately for desktop and mobile. Include the platform, environment, action, expected result, actual result, and evidence. For example: Summary: Applying a saved address leaves the delivery fee unchanged Shared context: - Account: test account with a saved address in a different region - Starting state: cart contains one shippable item - Expected: delivery fee recalculates for the selected address Desktop — Chrome 131 on macOS 15: 1. Open checkout. 2. Select the saved address in another region. 3. Observe that the address changes but the delivery fee does not. Mobile — Android 15, Pixel 8: 1. Open checkout in the app. 2. Select the same saved address. 3. Observe that the delivery fee does not change. Evidence: - Desktop recording: [link] - Mobile recording: [link] - Actual fee / expected fee: [values] The example is a template, not a claim about a tested product. Replace its values with what you observed. Do not infer a shared cause from matching outcomes; keep the evidence visible so the assignee can investigate. For more structure, follow this bug report template with reproduction steps. A screen recording paired with a bug report can show the timing or interaction that is hard to describe in text. ## How do you report a bug that only happens on one platform? File the issue for the platform where you reproduced it. State the exact platform and version, the relevant browser or app version, and any conditions required to trigger the defect. Add a short note about the other platform only if you tested it using a comparable setup. For example, “Not reproduced on desktop” is useful only when the browser, account, test data, and steps were comparable. If the setups differ, write what you actually checked rather than treating the second platform as proof that the bug is absent. Avoid broad titles such as “Checkout broken everywhere.” Prefer a title that names the behavior and scope, such as “Delivery fee does not refresh after changing address on Android.” This helps a team route the issue before it knows whether the cause is shared. If the report will go to an AI coding assistant, keep the same discipline: describe what happened, what you expected, steps to reproduce, and the environment. The AI bug report feature explains how a structured report can give an agent context to inspect. ## How should you track related desktop and mobile issues? When reports are separate, link them and add a short explanation of the relationship. A good note says what matches and what still differs: Both reports show the delivery fee staying unchanged after an address change. Desktop and Android have separate reproduction steps. Shared cause is not confirmed yet. After triage, update the relationship: Same defect and same fix: choose one issue as the implementation ticket and close or mark the other as a duplicate, following your team’s tracker conventions. Related but separate defects: keep both open and link them as related, with a distinct owner or fix for each. Not related: remove the link or explain why the similar symptom came from different behavior. Regression risk: add a verification step for each affected platform to the relevant fix or test plan. Jira’s links can associate issues without forcing their descriptions into one ticket. Check that issue linking is enabled and that your account has permission to create links. For a mobile report that needs device-specific evidence, see mobile bug reporting without an SDK. ## Sources https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-linking/ — Atlassian’s Jira Cloud issue-link configuration, link types, and permission requirements. Date checked: 2026-11-05. https://confluence.atlassian.com/jirasoftware/linking-issues-1528303986.html — Atlassian’s guide to linking Jira issues and describing why they are linked. Date checked: 2026-11-05. https://clip.qa/features/ai-bug-reports/ — clip.qa’s structured AI-assisted bug report overview. Date checked: 2026-11-05. https://clip.qa/features/screen-recording-bug-report/ — clip.qa’s screen-recording report workflow. Date checked: 2026-11-05. ## Key Takeaways - Ask whether a developer would investigate and fix both platform behaviors in the same change. - Create separate bug reports when any of these conditions changes the work: Different trigger: the desktop bug needs a keyboard sequence, while mobile needs a gesture or device state. - Write the shared context once, then list exact steps and results separately for desktop and mobile. - File the issue for the platform where you reproduced it. ## Frequently Asked Questions **Q: Should I combine a desktop and mobile bug into one Jira ticket?** Combine them when they share a cause and will be fixed and verified together. Otherwise, create separate tickets and link them so the relationship stays visible. **Q: How do I report the same bug on multiple devices?** Record the exact device, OS, browser or app version, and reproduction steps for each device. Use one report only when the investigation and fix are shared; otherwise, split and link the reports. **Q: What if the desktop and mobile symptoms look the same but the cause is unknown?** Document each observation separately and link the reports as related. Combine or mark one as a duplicate only after triage confirms they represent the same defect. **Q: Should I file a bug if it only happens on mobile?** Yes. File a mobile-specific report with the device, OS, app version, steps, expected result, actual result, and evidence. Mention desktop only if you tested comparable steps there. **Q: Can I attach separate recordings to one bug report?** Yes, if the recordings demonstrate one defect that will be investigated together. Label each recording by platform and include separate reproduction steps so the evidence is not ambiguous. Sign up free to turn bug recordings into structured reports with platform context. ## Related Posts - [Read more](/blog/how-to-write-bug-reports-ai-template) - [Read more](/blog/screen-recording-to-bug-report) - [Read more](/blog/mobile-bug-reporting-without-sdk)