Skip to content
HamstikHamstik Docs

Work Items

Work Item is Hamstik’s umbrella term for the work your team needs to understand, plan, and deliver. The current Work Item types are Task, Bug, Story, Feature, and Epic.

Work Item fields

Work Items can include:

  • title and Markdown description;
  • type, status, priority, assignee, due date, and labels;
  • parent and sub-task relationships;
  • Project links and dependencies;
  • Sprint assignment and ordering;
  • comments, replies, attachments, and an activity log.

Work Item keys are stable within a Project, such as WEB-42.

Status and priority

The standard status flow includes backlog, todo, in_progress, in_review, and done. Boards make that flow visible, while the Work Items list provides filters for status, open scope, type, priority, assignee, Sprint, and label.

Priorities are low, medium, high, and urgent.

Backlog, Boards, and Sprints

Unscheduled Work Items appear in the Project Backlog. A Board is a filter view over the same Project-wide Work Item set. A Sprint adds a time-boxed planning view; its order is separate from the status order used by Boards.

Discussion and activity

Comments support replies and Markdown. Deleted comments leave a placeholder so a conversation remains readable. The activity log records important changes such as status, assignment, priority, and Sprint transitions.

Attachments

Attachment hosting depends on the Organization plan. Existing attachments remain readable, downloadable, and exportable after a downgrade; the plan gate applies to hosting new bytes.

See the API resources guide for the public Work Item projection and Personal Access Tokens for automation access.