Search the same game and patch first
Choose League of Legends or Teamfight Tactics, then check the patch shown above the results. The library starts with the current patch filter. Open Filters to choose an older patch or all patches. Search a distinctive part of the behavior, then narrow the results with a champion, item, tag or status. Champion and item filters use catalog identifiers, so changing the interface language does not change which entity you selected.
Read the original report and any corrections before deciding that two reports describe the same issue. A similarly named item or a report from a different patch can have different conditions. An empty result means that the current search found no report; it does not prove the behavior is new.
Separate observation from expectation
Sign in with Google to create a report. Use a title that identifies the interaction. In Observed, describe what happened. In Expected, explain what you thought should happen and why. List reproduction steps in their original order, one step per line. Include the patch, relevant champions and items, environment and whether the behavior happened always, sometimes or once.
Keep uncertainty visible. If you have reproduced the behavior only once, say so. Record conditions you actually tested and distinguish them from guesses. Link evidence that helps another person inspect the same sequence, but remove credentials and personal information before sharing anything publicly. A saved local draft is for recovery in that browser; it is not a published report.
Use discussion to improve the record
Other signed-in readers can record whether they reproduced the behavior or could not reproduce it. These reactions describe their experience, not a formal verdict. A comment can be marked as a correction, not a bug, or a workaround. Put the supporting steps or evidence in the comment so the difference can be checked. Use Report a concern for a private moderation concern, rather than publishing someone's personal information in discussion.
Corrections appear prominently alongside the report. Author or administrator resolution is a community status, not an official Riot announcement. If an interaction changes with a later patch, retain enough patch context for the earlier observation to remain understandable.
Check the summary's sources
AI summaries are optional reading aids built from the report and its cited comments. Read the linked sources when a conclusion matters. A stale badge means the source discussion changed after that summary was generated. New corrections are visible before a replacement summary is available.
Summary generation is scheduled by the service, not requested by a Generate button. Activity thresholds and batch limits affect eligibility and timing; check the current policy shown in the app. Eligibility does not promise immediate processing. You can always inspect the original report and its discussion without an AI summary.
Keep your own account and reports in order
You can bookmark a report and edit or delete content you own. Profile export downloads your account data as JSON. Account deletion removes the login and anonymizes retained public reports and comments, as described in the privacy policy; it is not the same action as deleting an individual report. Bug Atlas is an independent community tool and is not endorsed by Riot Games.