Priority level (High, Normal, Low, Critical, P1)
ID priority_level
DatatypeNot PIIcategoricalDraft
This record is a draft: it has not been reviewed yet and may be incomplete or wrong. Do not rely on it for compliance decisions. Help improve it (see CONTRIBUTING.md).
Priority of a task, ticket, bug report or request in an issue tracker or a task list: High, Medium, Low, Normal, Urgent and Critical, the levels Blocker, Critical, Major, Minor and Trivial of Trac and Jira, Highest and Lowest, the codes P1 to P5 of Bugzilla, the MoSCoW levels (Must Have, Should Have, Could Have) and the same words in other languages (hoch, haute, alta). The words are common in other columns (a risk level, a price level), so a column is a priority by its field name.
- Parent datatype
- Category
category - Categories
- Common
- Countries
- Global (not tied to a country)
- Languages
- English, German, French, Spanish, Italian, Dutch
- Quality
- 65/100 · missing: regexp, negative example, mapping (Wikidata, Schema.org, ...)
- Metacrafter rules
- 1 rule (1 by field name, 0 by value)
prioritylevelbynamefield, common/common.yaml
- Supported by tools
- metacrafter
Examples
| Value | Description |
|---|---|
| High | |
| Normal | |
| Low | |
| Critical | |
| Blocker | Trac and Jira |
| P1 | Bugzilla |
| Must Have | MoSCoW |
Translations
| Language | Name | Description |
|---|---|---|
| Russian | Приоритет (высокий, обычный, низкий, P1) |
Sources
- wikipedia: Bug tracking system (en.wikipedia.org)
Use this record
- Page URL:
https://registry.apicrafter.io/datatype/priority_level - JSON: API v1 · legacy shape (used by metacrafter) · Markdown (for LLMs)
- Improve it: edit
data/datatypes/any/common/priority_level.yamlon GitHub