---
title: Accepted words for kinds
description: Look up the eight kinds of tzTrack issue and the other words each kind accepts, so a raise in your own words files the right kind.
slug: /reference/accepted-words-for-kinds
order: 4
visibility: public
redirects_from: []
---

# Accepted words for kinds

Every issue has one kind, and tzTrack accepts a few other words for some kinds. This page lists the kinds, what each means, and the other words each reads.

## The kinds

| Kind | Means | Accepted other words |
| --- | --- | --- |
| `bug` | Something is wrong, in code, data, text, or anything else. | `problem`, `error`, `mistake` |
| `gap` | Something is missing. | `missing_capability` |
| `docs` | The instructions or help for a product are wrong. | `documentation_gap` |
| `friction` | It works, but it is hard to use. | `refusal_not_understood`, which also keeps the label `refusal_not_understood` |
| `question` | Something needs an answer. | none |
| `task` | Work to do. | none |
| `praise` | Something works well. | none |
| `idea` | A possible new thing to make. It takes no priority, is never marked fixed, and later requests link to it, so its report count is its demand. | none |

An accepted other word files the kind it reads as, at `raise` and at an `update` of the kind alike. A raise with the kind `problem`, for one, files a `bug`.

## Choosing a kind

A book or another project with no code is not all `docs`. What is wrong in a chapter is a `bug`, and what is missing from it is a `gap`. `docs` is for the instructions or help of a product. Something to consider later, with no work owed yet, is an `idea`.

## Related

- [Issues and kinds](/concepts/issues-and-kinds) explains each kind beside the states and outcomes.
- [The tools](/reference/the-tools) lists `raise`, which takes the kind.