(1min 30 read time)
The Task Structure section outlines the key components that define each task, ensuring all necessary information is included for effective management and tracking.
The task's name should provide an easy, at-a-glance identifier, focusing on brevity. Detailed information and context are covered in other sections.
This refers to the repository where the issue is opened. It generally corresponds to the Project the task belongs to. The repo also serves as an indicator of the Client, as repositories are almost always prefixed with the client name.
The description provides the full details of the task. This includes:
This field lists the staff member(s) responsible for the task's progression. Only those directly involved should be assigned.
The status reflects where the task is in its lifecycle (e.g., To Do, In Progress, Backlog, etc.).
Labels help organise tasks into specific categories relevant to developers.