IssueSubtasks
Lists all subtasks associated with Jira issues, including parent-child relationships and statuses.
Table Specific Information
You can search for IssueSubtasks by using SQL and JQL (Jira Query Language).
Select
The add-in uses the Jira API to process some of the filters.
The add-in processes other filters within the add-in.
The available columns for IssueSubtasks are IssueId, IssueKey, and JQL. For example:
SELECT * FROM IssueSubtasks WHERE IssueId = 10009 AND JQL = 'creator = john'
Columns
| Name | Type | References | SupportedOperators | Platform | Description |
| SubtaskId [KEY] | String | Common | The unique identifier assigned to the subtask within Jira. Used internally to reference the subtask across the platform. | ||
| SubtaskKey | String | Common | The user-facing key of the subtask, usually in the format 'PROJECT-123'. This value is used to reference the subtask in the user interface and API. | ||
| IssueId | Integer |
Issues.Id | =,<>,>,>=,<,<=,IN,NOT IN | Common | The unique identifier of the parent issue to which this subtask is linked. All subtasks must be associated with a parent issue. |
| IssueKey | String |
Issues.Key | =,<>,>,>=,<,<=,IN,NOT IN | Common | The key of the parent issue, used to identify the parent issue in the UI and via API calls. |
| IssueCreatedDate | Datetime | =,<>,>,>=,<,<=,IS,IS NOT,IN,NOT IN | Common | The date and time when the parent issue for this subtask was created. Useful for tracking issue timelines. | |
| IssueUpdatedDate | Datetime | =,<>,>,>=,<,<=,IS,IS NOT,IN,NOT IN | Common | The most recent date and time when the parent issue was modified. Reflects the last activity or change. | |
| Summary | String | Common | A short summary or title describing the subtask. Typically used to capture the subtask's main objective or activity. | ||
| TypeId | String |
IssueTypes.Id | Common | The internal identifier representing the issue type of the subtask, such as bug, task, or technical debt. | |
| TypeName | String |
IssueTypes.Name | Common | The display name of the subtask's issue type. This could be labels like 'Sub-task', 'Development Task', or 'QA Task'. | |
| TypeDescription | String |
IssueTypes.Description | Common | A detailed description of the issue type associated with this subtask. This helps explain the role or purpose of the type within workflows. | |
| TypeSubtask | Boolean |
IssueTypes.Subtask | Common | If the value is 'true', this issue is classified as a subtask. If 'false', it is a standard issue type. Helps distinguish between top-level and dependent issues. | |
| PriorityId | String | Common | The unique identifier of the priority assigned to this subtask, indicating its urgency or importance within the project. | ||
| PriorityName | String | Common | The display name of the subtask's priority level, such as 'High', 'Medium', or 'Low'. | ||
| StatusId | String | Common | The identifier of the current status for the subtask, such as 'To Do', 'In Progress', or 'Done'. Reflects its progress in the workflow. |
Pseudo-Columns
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| JQL | String | Jira Query Language (JQL) allows you to build structured queries to filter and retrieve specific subtasks based on custom criteria. |