Subtasks
gira ticket create (extended)¶
Description: Creates a new ticket or sub-task in the project. Sub-tasks are linked to a parent ticket and are automatically associated with the same epic and sprint when possible.
Behavior:
-
When
--type subtaskis used: -
Sets
"issueType": "SubTask"in metadata - Requires
--parent, which must refer to a valid ticket - Appends the sub-task ID to the parent’s
subtasksarray - Optionally inherits
epic,sprint, andassigneefrom parent
Additional Options:
--type task|subtask– default istask--parent TICKET_ID– required when--type subtask
Example:
gira ticket list --parent <TICKET_ID>¶
Description: Lists all sub-tasks associated with a given parent ticket ID.
Behavior:
- Reads the
subtasksfield of the parent’smetadata.json - Lists each child ticket with its title, status, and assignee
Options:
--json– output structured list of sub-task metadata
Example:
gira ticket tree <TICKET_ID>¶
Description: Displays the parent ticket and all of its sub-tasks in a visual tree layout.
Behavior:
- Prints hierarchical view: parent followed by children
- Includes ID, title, and status for each item
Example:
Output:
GIRA-42 Implement authentication
├── GIRA-43 Create login form [ToDo]
├── GIRA-44 Build backend endpoint [InProgress]
└── GIRA-45 Validate token [Done]
gira ticket add-dep <TICKET_ID> --blocked-by <OTHER_ID>¶
Description: Adds a dependency indicating that the current ticket is blocked by another.
Behavior:
- Adds
OTHER_IDtoblockedByarray inTICKET_ID’s metadata - Optionally adds
TICKET_IDtoblocksarray inOTHER_ID’s metadata
Options:
--no-reciprocal– skip adding reciprocalblocksentry
Example:
gira ticket remove-dep <TICKET_ID> --blocked-by <OTHER_ID>¶
Description: Removes a dependency from a ticket.
Behavior:
- Removes
OTHER_IDfromblockedByarray ofTICKET_ID - Also removes
TICKET_IDfromblocksofOTHER_ID(unless skipped)
Options:
--no-reciprocal– do not update reciprocal relationship
Example:
gira ticket deps <TICKET_ID>¶
Description: Shows all dependencies for a given ticket.
Behavior:
- Displays both
blockedByandblocksrelationships - Shows status and title of referenced tickets
Options:
--json– output structured dependency data
Example:
gira ticket list --blocked¶
Description: Lists all tickets that are currently blocked by unresolved dependencies.
Behavior:
- Reads
blockedByfor all tickets - Filters those where at least one dependency is not in
donestatus
Options:
--json– output structured data
Example: