> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/mosip-docs-1.1.5/contribute/issue-reporting-guideline.md). # Issue Reporting Guideline ### Pre-requisite MOSIP issues are maintained in [Github](https://github.com/mosip). File the issue against the right repository. ### Reporting Issues 1. Check if the issue is already reported. 2. Check if the issue is already fixed. 3. If not, just go and file the issue 4. Template for filing new issues > **Describe the issue** A clear and concise description of what the bug is. > **To Reproduce** Steps to reproduce the behavior: > **Expected behavior** A clear and concise description of what you expected to happen. > **Actual behavior** A clear and concise description of what you see. > **Screenshots** If applicable, add screenshots to help explain your problem. > **Environment (please complete the following information):** Hardware and software details such as client OS, Server OS, Browser details etc > **Attach logs** Helps in faster resolution of data > **Additional context** Add any other context about the problem here. *** ### Features/Enhancement request guidelines 1. Check if the feature is already reported. 2. Check if the feature is already fixed. 3. If not, just go and file the feature request 4. Template for filing new feature request > **What is the current limitation without the feature** > **Describe the feature request** > **What would the key benefits of this feature** > **Do you have any recommendations and solutions that are existing in the field** > **Any technology/solution recommendation would be highly appreciated** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.mosip.io/1.2.0/mosip-docs-1.1.5/contribute/issue-reporting-guideline.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.