# Request a feature

Using GitHub to fill out a feature request issue helps us keep track of and implement improvements to issues you may find in our application. This short guide will help you understand what we look for when a user fills out this template.

* **Title**: Use a clear and descriptive title that summarizes the issue.
* **Contact Details**: Provide a good follow-up email address to contact if we need more info.
* **Is your feature request related to a problem? Please describe**:
  * Provide a detailed description of the problem that the feature would solve.
  * Include error messages, logs, etc., to help us understand the problem.
* **A clear and concise description of what you want to happen**:
  * Provide as much detail as possible for how you would like the software to function with your new feature idea implemented.
* **Describe alternatives you've considered**:
  * This will help us follow your thought process and rule out any alternatives you have researched and considered before filling out the request.
* **Screenshots and additional context**:
  * Embed any screenshots, gifs, or external video links that can help explain the issue you are experiencing.
* **Assignees**: Optionally, assign the issue to specific team members if necessary.

## Change log

Major updates to the content of this page will be added here.

<table><thead><tr><th>Date</th><th width="240">Update</th><th>Notes</th></tr></thead><tbody><tr><td>2/12/2024</td><td>Initial Content</td><td>Updated with Initial content</td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr></tbody></table>


---

# 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://wiki.simpler.grants.gov/get-involved/github-planning/filling-out-a-feature-request.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.