Submitting a useful Issue Council report

Before submitting

Search the public Issue Council for an existing report describing the same underlying problem. Confirm the canonical report when it matches.

A useful report includes

• A focused title describing what failed and where.
• The correct release branch and exact patch or build when known.
• What you expected to happen.
• What actually happened.
• Ordered reproduction steps.
• Relevant screenshots that contain no private information.

Saved drafts remain private. Normal submitted reports are public by default unless the selected build or evidence requires restricted visibility. Accept the current Community Guidelines and Issue Council Rules before participating.