Open a task to see its full detail. Most fields are optional, and a few earn their keep.
Title and description
The title is what everyone reads on the board, so make it a statement of what needs doing. The description is rich text, with headings, lists, links and images pasted straight in.
Assignees
A task can have more than one. Assignment is about accountability and not access: an unassigned task is still visible to everyone on the project, and anyone on it can still track time against it.
If your role only lets you assign tasks to yourself, you will be told so when you try to pick someone else.
Priority
Low, Medium, High or Urgent, colour-coded on the card and available as a filter. Priority is required, so pick honestly. A board where everything is Urgent tells you nothing.
Type
Task, Bug, Feature or Story. Its value is in filtering and reporting: "how much of this sprint was bugs" is a question you can only answer if the field was filled in.
Labels
Free-form tags for whatever cuts across your types and columns, such as a component, a client or a release. Create them as you go. They are shared across the project so the same label means the same thing on every task.
Due date
Shows on the card and drives filtering and reminders. Set it where there is a real deadline, not on everything.
Files and links
Attach designs, screenshots and documents to the task, and link out to anything living elsewhere. Files attached here belong to the task, while things everyone on the project needs belong on the project instead.
History
Every task keeps a record of what changed and who changed it. When a task has clearly moved backwards or lost its assignee, the history tells you when and by whom, usually faster than asking.