Task Tools

Recommended usage

Mention @Hana and describe your task/sprint intent in plain language. Hana maps this to the right task workflow.

Supported operations/arguments

Operation	Purpose	Supported arguments
Create tasks	Create one or more tasks for a user	user_name, tasks[] (title, notes, task_due_timestamp, task_due_date, priority, story_points)
Update task fields	Update status/ETA/priority/tags/assignees/story points	task_id, status, task_due_date, task_due_timestamp, priority, story_points, tag_names[], assignee_user_names[], update_message
Add task progress note	Add narrative update without field changes	task_id, update_message
List sprints	List sprints with filters	status, search_query, max_results
Active sprint summary	Show active sprint summary	none
Sprint board view	Show board details for a sprint	sprint_id, max_tasks

How Hana Chooses Update Mode

• If you request field changes, Hana performs a field update.
• If you only provide progress text, Hana adds a progress note.

Invocation examples

create tasksupdate tasktask updateactive sprint summary

@Hana create tasks for deployment:
- Prepare release notes by tomorrow (MEDIUM, 2 points)
- Monitor metrics after rollout by Friday (HIGH, 3 points)

@Hana update task TSK-120: move due date to next Friday, set priority HIGH.

@Hana add a progress update to task TSK-120: backend integration complete, QA pending.

@Hana show active sprint summary as a table: task id, owner, status, blockers.

When to use

• Use @mentions for better assignee resolution.
• Include exact dates/times for due-date changes.
• Specify desired output format.

See also

• Invocation Examples
• Sprint Tools
• Tool Quick Reference
• Dashboard Tasks

What it does

Hana creates, updates, and summarizes tasks, including sprint-context views and progress updates.

Troubleshooting

• Update failed: confirm task id format and that the task exists.
• Ambiguous intent: specify whether you want create, update, or progress-note mode.

Permissions/limits

• Task actions depend on project integration permissions.
• Include due date/priority explicitly to avoid inferred defaults.

High-signal invocation

@Hana create tasks for release hardening: run load test (HIGH), finalize rollback checklist (HIGH), update runbook (MEDIUM).

Edge-case invocation

@Hana update task TSK-120: set due date to 2026-03-01 17:00 IST, priority CRITICAL, and add progress note "QA blocked by flaky integration tests".