# Report Issue

{% hint style="info" %}
**Purpose:** The application provides an in-built mechanism to report defects or anomalies, allowing end-users to communicate potential issues directly to the development team.
{% endhint %}

**Navigation Path:** Menu > Report Issue

<figure><img src="https://1721684721-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPaF9cGX0SlYrvgRNs9Wi%2Fuploads%2FCMQxqOqUqx2DjLAovS4p%2Fimage.png?alt=media&#x26;token=ffa01625-9744-4cfc-b2be-7e795300f1bd" alt=""><figcaption><p>Navigation to Report issue popup modal</p></figcaption></figure>

<figure><img src="https://1721684721-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPaF9cGX0SlYrvgRNs9Wi%2Fuploads%2F6XvXVgBH9f7fRyZgrJcP%2Fimage.png?alt=media&#x26;token=a09fa6ad-e943-46b4-8112-1d73ce3752ed" alt=""><figcaption><p>Report issue popup modal</p></figcaption></figure>

**Functionality Overview:**

1. **Defect Logging:** Upon encountering any software issue, users can utilize the dedicated defect logging form to register the issue. This form is intuitively designed to capture essential data, including a description of the problem, severity, and potential steps to reproduce.
2. **Attachment Support:** To provide a comprehensive view of the encountered defect, the system supports the attachment of supplementary files. Users can include screen captures, video recordings, or any other relevant documentation, aiding the development team in understanding, reproducing, and addressing the defect.

**Issue Tracker Grid:** Once logged, defects are listed in the Issue Tracker grid. This grid serves as a central repository and offers users an overview of all reported defects, their status, and more. Users can easily refer to this grid for updates and modifications related to their reported issues.

```url
https://staging.buildsolution.com.au/administrator/tools/issue-tracker
```

**Database Integration:** The defect logging system interacts with multiple database tables to ensure structured and efficient data storage. The following database tables are implicated in this process:

* `issue_tracker`: This primary table stores the core information of each logged defect.
* `issue_tracker_activity_logs`: Logs activities and updates related to each defect.
* `issue_tracker_activity_log_comments`: Houses comments and notes added to a defect's activity log.
* `issue_tracker_activity_log_uploads`: Manages the storage references of any attachments associated with a defect's activity log.

**Backend Implementation:** The server-side logic governing the defect logging process is encapsulated within the `IssueTrackerController` located at `App\Http\Controllers\Admin\Tools\IssueTrackerController`. The `store` method within this controller handles the actual defect registration process, ensuring that the provided data is validated and stored appropriately.

**Configuration Data:** For a seamless user experience, certain dropdown values, such as 'Issue Type', are populated dynamically from configuration files rather than hardcoding them into the system. In this context, the dropdown values are sourced from `config/enums.php`, promoting easy modification and extension in the future.

<br>


---

# 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://skaleptyltd.gitbook.io/build-solution/product-guides/issue-tracker/report-issue.md?ask=<question>
```

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.