> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/works/works-v1.0/programmes/muktasoft-v2.0/implementation/uat-planning/issue-reporting-template.md).

# Issue Reporting Template

## Template

<table><thead><tr><th width="95">#</th><th>Type</th><th>Title</th><th>Description/Summary</th><th>Screenshot</th><th>Steps to Reproduce</th><th>Status</th><th>Priority</th><th>Resolution</th><th>Assignee</th><th>Ticket No.</th></tr></thead><tbody><tr><td>1</td><td>Defect</td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td></tr><tr><td>2</td><td>Clarification</td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td></tr><tr><td>3</td><td>Enhancements</td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td></tr><tr><td>4</td><td>Task</td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td></tr><tr><td>5</td><td>Defect</td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td></tr><tr><td>6</td><td>Defect</td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td><td> </td></tr></tbody></table>

## Definitions

| **Title:** Enter a clear title for the bug, so anyone, regardless of role, can understand it (e.g., “Invoice Will Not Print for User”).                                                                                                               |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Description/Summary:** In addition to a clear title, add an easy-to-understand description of the bug (e.g., “The invoice will not print for the user when they have the invoice opened and click the Print button”).                               |
| **Environment:** Include any environment details (such as browser, operating system \[OS], URL, software version, etc.), so anyone reviewing the bug can easily glean the environmental factors, and so development can replicate the bug and fix it. |
| **Screenshot:** Add a screenshot of the bug, if applicable. That way, whatever the software malfunction, the issue will be clear to anyone reviewing the report.                                                                                      |
| **Steps to Reproduce:** Include the exact steps you take to reproduce the bug occurrence (e.g., “Customer running Windows 10 and Internet Explorer 8 cannot print an invoice”).                                                                       |
| **Status:** Specify the status of the bug using the Status dropdown list (e.g., new, open, resolved, accepted, in progress, to be validated, done, etc.).                                                                                             |
| **Priority:** Select a priority for the bug using the Priority dropdown list (e.g., critical, high, medium, low, etc.).                                                                                                                               |
| **Resolution:** Select the bug’s status using the Resolution dropdown list (e.g., unresolved, fixed, etc.).                                                                                                                                           |
| **Assignee:** Enter the name of the employee who is responsible for ensuring that the bug is fixed.                                                                                                                                                   |
| **Reporter:** Enter the name of the person who reported the bug.                                                                                                                                                                                      |
| **Created:** Enter the date that the bug was reported.                                                                                                                                                                                                |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digit.org/works/works-v1.0/programmes/muktasoft-v2.0/implementation/uat-planning/issue-reporting-template.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.