# Bug Reporting ## Who can report a bug? ### Internal * Cybera & PIMS ### External * Callysto creator (content creator / curriculum expert - professor, teachers etc) * Callysto developer (Student developers) * End users - Students, Teachers ## Where can they report a bug? * Internal bug tracking - JIRA. * External bug tracking - Bugs can be reported by creating an [issue](https://help.github.com/en/github/managing-your-work-on-github/creating-an-issue) on the Github [repo](https://github.com/callysto/curriculum-notebooks/issues). ## How to report a bug? * Three important aspects of bug reporting in general are: * Brief description of the bug, with steps on how to reproduce it. * Expected result * Actual result * When writing down the steps to reproduce a bug, * It would be helpful to note down the environment details like web browser or other system information if thats relevant. Also, note down general details like name of the notebook, section of the notebook where you find the error, etc. * Add screenshots if possible and only if it adds to the explanation. Please note, for external bug reporting, screenshot uploads are not available natively in Github, therefore you may want to consider hosting your image and linking to it via [imgur](https://imgur.com/) or your host of choice. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://training.callysto.ca/coding/bug-reporting.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.