Field Discovery Tools

Discover available priorities, statuses, issue types, labels, and more.

Field discovery tools let you query the available values for fields in your project tracker. Use these to ensure you are using exact, valid values when creating or updating issues.

get_priorities

Lists available priority levels (e.g., Highest, High, Medium, Low, Lowest). Use the exact names returned here when setting priority on create_task or update_task.

When it runs: Called when you need to know the available priority levels.
Example trigger: "What priority levels are available?"

get_statuses

Lists available statuses and their categories (To Do, In Progress, Done). Use exact status names when setting status on update_task.

When it runs: Called when you need to know the valid statuses for transitions.
Example trigger: "What statuses can I use?"

get_issue_types

Lists available issue types (e.g., Story, Bug, Task, Epic, Sub-task). Useful for knowing what types of issues you can create.

When it runs: Called when you need to know what issue types exist.
Example trigger: "What issue types are available in this project?"

get_labels

Lists existing labels in the project. Use when setting labels on tasks to ensure you use existing labels.

When it runs: Called when you need to know available labels.
Example trigger: "What labels exist in this project?"

get_components

Lists project components (e.g., Frontend, Backend, API) with their leads and descriptions.

When it runs: Called when you need component information.
Example trigger: "What components does this project have?"

get_assignable_users

Lists users who can be assigned to issues. Returns display names, which is what you pass to the assignee field on create_task and update_task.

When it runs: Called when you need to know who can be assigned to issues.
Example trigger: "Who can I assign tasks to?"

get_custom_fields

Lists custom fields and their IDs. Use when you need to set custom field values via the custom_fields parameter on create_task or update_task.

When it runs: Called when you need to set or read custom fields.
Example trigger: "What custom fields are available?"