> For the complete documentation index, see [llms.txt](https://help.usehaystack.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usehaystack.io/faq/what-is-status-category.md).
# What is Status Category?
Difference between JIRA's Status Category, Status and Resolution
Jira has 4 fields that are often confused
1. **Status Category**: Groups various statuses into broader categories to provide a quick overview of a task's state. Has `To Do`, `In Progress`, and `Done`. These are used to uniformly understand the phase of a task across different projects.
2. **Status**: Describes the specific stage a task is in within its lifecycle. Examples include `In Progress`, `In Review`, `QA`, `Closed`. Each status belongs to one of the status categories, helping to map more detailed stages to simpler groupings.
3. **Resolution**: Indicates the final outcome of a task once it is closed. It explains why a task was closed, with options like `Done`, `Won't Do`, `Duplicate`. This field is typically empty while a task is still open or in progress.
4. **Column**: Represents a visual component on a board (like in Kanban or Scrum boards) that correlates to task status. Columns organize tasks visually by status, facilitating a clearer view of workflow and progress through statuses like `To Do`, `Doing`, `Done`.
Below is an example board reflecting different Status Categories, Statuses and Columns.
**Status Categories:**
* To Do (gray)
* In Progress (blue)
* Done (green)
**Columns:**
* TO DO
* IN PROGRESS
* IN REVIEW
* MERGED
* DONE
**Statuses:**
* TODO
* IN PROGRESS
* IN REVIEW
* MERGED
* DONE
* WON'T DO
You can access the following page from your [Board configurations](https://confluence.atlassian.com/jirasoftwareserver/configuring-a-board-938845252.html).
---
# 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://help.usehaystack.io/faq/what-is-status-category.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.
