Issue Project Keys
Every issue in ISO Mate is assigned a unique project key when it is created. The key consists of a prefix and a sequential number.
Project-Based Keys
When an issue belongs to a project, the key uses the project prefix. For example, if your project key is PROJ, issues created in that project are numbered PROJ-1, PROJ-2, PROJ-3, and so on. This groups all issues under a single recognizable prefix regardless of issue type.
Type-Based Keys (No Project)
If an issue is not assigned to a project, the prefix is determined by the 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 PROJ-1 through PROJ-20, 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 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. Filter by project to see all issues under a specific project prefix. The MCP server also supports looking up issues by key. Pass a key like PROJ-7 or BUG-7 directly to the get_issue tool, or filter by prefix using the project_key parameter in list_issues.