A description with substance
Write the requirements, constraints, and acceptance criteria in markdown, or start from a Vibe Speccing draft.
The context belongs with the task
Keep the description, attachments, links, sub-items, comments, and task activity together. Open the work and get the information needed to move it forward.
Why it matters
Make the work clearer, not heavier.
A task title rarely explains the whole job. When the specification lives in one place, the discussion in another, and supporting files in a third, the next person has to reconstruct the context. Taskonio gives that context a home alongside the work itself.
Designed around the way real teams decide and deliver.
The supporting material
Keep files, links, properties, and child work close to the task they explain.
A conversation in context
Use comments and task activity to understand the discussion and changes around the work.
A closer look
How task view works in Taskonio.
01
Describe what a good result looks like
Use the task description for the problem, relevant context, and acceptance criteria. Markdown gives the content structure; Vibe Speccing can help create an editable starting point.
- Write and edit markdown descriptions
- Keep the requirements on the task
- Review AI-generated descriptions before saving
02
Attach the evidence and link the source
Add supporting attachments and links where people will look for them: on the work. A design, reference document, or source conversation can explain details that would otherwise disappear into a chat history.
- Attach files relevant to the work
- Add links to supporting material
- Keep references with the epic, item, or sub-item they explain
03
Break the task into meaningful sub-items
When an item needs more execution detail, add sub-items beneath it. Keep the parent task as the shared context and use the children for the smaller pieces of work.
- Add child work from the detail view
- Use task types to communicate the nature of each item
- Use Vibe Breakdown when you want a reviewable proposal first
04
Keep questions and answers on the work
Comments, mentions, reactions, and threaded replies let teammates discuss the task without separating the conversation from its context. Direct mentions connect that conversation to the recipient’s Actions inbox.
- Comment and reply in context
- Mention the person who needs to respond
- Return from a notification to the relevant work
05
Read the task activity alongside the discussion
Task activity provides a place to review changes around the work. Use it with the description and comments to understand the task’s current state before making the next update.
- Review task activity in the same detail view
- Check the current properties before acting
- Use the task ID to refer to the exact item
How it works
From setup to useful work.
- 01
Open the work
Choose an epic, item, or sub-item from a view or notification.
- 02
Build the context
Add the description, supporting links and files, and child work the task needs.
- 03
Discuss and move forward
Resolve questions in comments, review task activity, and keep the task’s properties current.
Taskonio’s approach
One place to understand the next step
The task view is the detailed counterpart to your tables and boards. It holds the context a compact row or card cannot show.
- Description
- Editable markdown for context, requirements, and acceptance criteria.
- Attachments and links
- Supporting files and references attached to the work.
- Sub-items
- Child work beneath an item when more detail is useful.
- Comments
- Threaded discussion, mentions, and reactions.
- Task activity
- A view of activity around the task.
- Properties
- Ownership, status, priority, dates, estimates, and relationships.
Compare this workflow with the tools your team already knows.
Taskonio vs JiraA focused engineering workflow or a deeply configurable platform: choose the operating model your team can sustain.Read comparisonTaskonio vs TrelloA board you can shape around almost anything, or an engineering workflow with the planning structure already in place.Read comparisonTaskonio vs NotionCompare an opinionated engineering workflow with a flexible workspace that combines databases, documents, knowledge, projects, and AI.Read comparison
Considering another tool? Explore the full set of guides to find the right fit for your team.
View all comparisonsRelated features
Keep exploring the workflow.
Hierarchy and properties
From the team space to the smallest next step
Organize work in team spaces, connect initiatives to epics, items, and sub-items, and give each piece the ownership and properties it needs.
ExploreTaskonio AI
Shape the work. Review the next move.
Use Vibe Speccing to draft a specification, Vibe Breakdown to propose child work, and Decisions to review AI recommendations against the current state of a task.
ExploreInbox: Actions and Updates
Notifications that separate action from awareness
Keep assignments and mentions open until they are handled, while routine activity clears naturally after you read it.
ExploreQuestions
Know before you switch.
What is included in the task view?
The task view brings together the description, properties, sub-items, attachments, links, comments, and task activity.
Can we use markdown in descriptions?
Yes. Taskonio supports markdown-formatted descriptions, including editable content produced by Vibe Speccing.
Can a task contain smaller pieces of work?
Yes. Items can contain sub-items. Use them for execution detail while keeping the parent item as shared context.
Where should we discuss a task?
Use comments on the task, with threaded replies and mentions. This keeps the discussion connected to the work and gives the recipient relevant context.
Can we open the same task from a table or board?
Yes. Tables and boards are views of the same underlying work, not separate copies of a task.
Give the next person the full picture
Keep the specification, references, and conversation where the work happens.