Issue Project Keys
Every issue in ISO Mate is assigned a unique project key when it is created. The key consists of a type-based prefix and a sequential number.
Key Prefixes by Issue Type
- EPC: Epics (EPC-1, EPC-2, EPC-3, …)
- USR: Stories (USR-1, USR-2, USR-3, …)
- TSK: Tasks (TSK-1, TSK-2, TSK-3, …)
- BUG: Bugs (BUG-1, BUG-2, BUG-3, …)
- SUB: Subtasks (SUB-1, SUB-2, SUB-3, …)
How Numbering Works
Each prefix has its own independent counter per account. For example, your account might have TSK-1 through TSK-50 and BUG-1 through BUG-12 at the same time. Numbers increment automatically and are never reused, even if an issue is deleted.
Keys Are Permanent
A project key is locked in at creation and never changes. If you later change an issue from Task to Bug, it keeps its original TSK-* key. This ensures that references in commit messages, comments, documentation, and external tools remain valid.
Finding Issues by Key
You can search for issues by project key in the backlog filter bar. The MCP server also supports looking up issues by key, pass a key like BUG-7 directly to the get_issue tool, or filter by prefix using the project_key parameter in list_issues.