Comment on page
Creating new Jira bug tickets
Bugs are any “obvious errors” on how the product or a feature is functioning as well as any UI issues. If you’re not reporting an obvious error, please file a Story ticket instead. Errors on unsupported platforms are not considered bugs.
- Search existing tickets in Jira's "Mattermost" project to confirm your issue isn’t already filed by someone else.
- If your issue involves security or if it involves confidential information or customer information, please mark the bug ticket as internal.
- Labels: Add a
customer-buglabel if the ticket is based on a customer bug report. Add a
community-buglabel if the ticket is based on a community bug report.
- Environment: There is an
Environmentfield with drop-down options to choose whether the bug was found in Cloud test servers, Cloud production servers, Self-Hosted test servers, Self-Hosted production servers, or in Master/PR testing.
- Steps to reproduce: How can we reproduce the issue.
- Expected behavior: Describe what you’re expecting to see.
- Observed behavior: Describe your issue in detail. What did you see happen? Please include relevant error messages and/or screenshots.
- Summary: Add a summary and any additional relevant details of the issue if it helps make the bug more clear. For example, you can add details on Mattermost server and version, OS and version, Mattermost mobile app version, Mattermost desktop app version, and any notable Mattermost configurations (such as HA, Elasticsearch, image proxy, SSO).
- Attachments: Please include screenshots and/or videos of any helpful error messages and snippets of what you are seeing.
- Possible fixes: If you can, link to the line of code that might be responsible for the problem.
- If you know which team would own fixing the bug, you can assign the ticket directly to that team.
- Otherwise, you can leave the team
Unassignedand the Release Manager assigns the ticket. The Release Manager follows the ~Bugs channel on a daily basis.