Productivity Tools

Linear

Review AI suggestions about incoming issues and check whether a possible duplicate describes the same problem.

Review checked

Example tasks

  • Reviewing newly reported work before sending it to a team
  • Checking duplicate suggestions against the original reports
  • Revisiting a suggested link when new details arrive

Check before use

  • Similar titles can refer to different steps, symptoms, or owners
  • Marking a duplicate can move attachments, so check the target and its access before merging
  • Check which teams and data the AI feature can consider before using sensitive reports

Check Both Reports Before Marking a Duplicate

Linear’s Triage Intelligence guide describes suggestions for related issues and possible duplicates. Try two fictional reports titled “Export failed.” In one, no file was created. In the other, the file was created but could not be opened. Compare the steps and observed results rather than treating matching titles as evidence of the same problem.

Keep the report IDs and the reason you kept them separate or linked them. When another report arrives, check the exact sequence again. The incident timeline practice pack offers a way to practice distinguishing observations from explanations.

Before marking a real issue as a duplicate, review how Triage handles attachments, the destination issue’s visibility, pricing, and the workspace’s privacy requirements.

More use cases and potential advantages

Ways to explore

  • Review two fictional reports with the same short title
  • Compare what users did and what happened before linking them
  • Note why a suggestion was accepted or left open for more evidence

Potential advantages

  • Linear documents suggesting related issues and showing why a match was suggested
  • A linked report gives reviewers a place to compare conditions and outcomes