Multiple views per module
Move between purpose-built views without rebuilding filters or changing the team’s source of truth.
Your work, your way - custom views for every engineer
Create multiple table and board views across Backlog, Planning, Sprint, and Kanban, then keep adjustments local or share them with the team.
Why it matters
Make the work clearer, not heavier.
A tech lead, product manager, and engineer rarely need the same lens. One person needs initiatives grouped by epic, another needs a board filtered to active work, and another needs a dense priority table. Taskonio keeps the underlying work consistent while allowing each view to answer a different question.
Designed around the way real teams decide and deliver.
Table or board
Choose dense rows for detail or spatial cards for flow, then expose only the properties that matter.
Personal or shared
Keep display choices and filters local or deliberately push useful changes to the team space.
A closer look
How custom views works in Taskonio.
01
Create multiple views in every module
Backlog, Planning, Sprint, and Kanban can each hold multiple independent views. Keep a board for standups, a table for triage, and a focused view for one owner or work type without rebuilding the module each time.
- Views remain attached to the module where they are useful
- Each view keeps its own layout and display decisions
- Framework choice changes available modules, not the view model
02
Choose an epic-based or item-based perspective
Epic-based views make initiatives the primary level and reveal their items. Item-based views make execution work primary and reveal sub-items. This keeps the first useful level of context visible without expanding the entire hierarchy at once.
- Epic-based views for initiative and roadmap conversations
- Item-based views for day-to-day planning and execution
- A consistent first-sublevel pattern across modules
03
Use tables when detail matters
Item-based tables can expose sub-items, epic, stage, label, owner, status, start date, target date, priority, and estimate. Epic tables keep the higher level focused on owner and dates.
- Dense, scannable rows for planning and triage
- Choose visible columns according to the purpose of the view
- Keep initiative and execution tables side by side
04
Use boards when spatial flow matters
Item-based board views turn the same work into cards. Show the supporting properties that help a standup or flow review - such as owner, priority, labels, dates, and sub-item progress - without duplicating the work.
- Card-based views for visual status and flow
- The same items remain available in table views
- Board properties stay focused on what is useful at a glance
05
Keep changes local or share them deliberately
Display options and filters do not need to become global decisions. Adjust the workspace for the question you are answering, keep the change local, or push it to everyone when it becomes a useful team convention.
- Local display options preserve individual working styles
- Team-wide sharing makes useful conventions repeatable
- The same local-or-shared choice applies to filters
06
Group, sort, filter, and search without changing the work
Manage views gives a team several ways to read the same work. Group related items, sort the order, turn properties on or off, and narrow the result with filters or search.
- Group by the property that fits the conversation
- Sort rows and choose the properties shown in tables and cards
- Use filters for a focused subset and search for a particular item
07
Act on the work from the view
A view is also a working surface. Select items for batch actions, or open the new task modal when a conversation uncovers something the team needs to capture.
- Select multiple items before applying a batch action
- Create work without rebuilding the view around it
- Open an item for its complete description, discussion, and supporting context
How it works
From setup to useful work.
- 01
Pick a module
Open the Backlog, Planning, Sprint, or Kanban module where a different perspective would help.
- 02
Choose the view level and layout
Decide between epic- or item-based work, then select a table or board layout and the properties to show.
- 03
Focus and share
Apply the filters needed for the question, then keep the setup local or share it with the team space.
Taskonio’s approach
One source of truth, several useful lenses
Custom views let different roles work from the same underlying items without forcing the team to agree on one permanent screen.
- Modules
- Views work across Backlog, Planning, Sprint, and Kanban where those modules are enabled.
- Perspective
- Choose epic-based views for initiatives or item-based views for execution.
- Layout
- Use tables for density and boards for spatial flow.
- Properties
- Expose only the ownership, status, dates, priority, estimates, and relationships needed for that view.
- Sharing
- Keep display and filter changes local or deliberately push them to the team space.
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.
Sprint planning
Sprint planning that doesn’t slow you down
Plan sprints in minutes with three focused modules - Backlog, Planning, and Sprint - plus live scope totals and flexible views for every planning conversation.
ExploreKanban boards
Kanban boards built for how engineers actually work
Choose Kanban for a clean two-module flow - Backlog and Kanban - with table and board views for teams that want continuous delivery without sprint ceremony.
ExploreHierarchy 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.
ExploreQuestions
Know before you switch.
Can different teammates adjust the same view?
Yes. Views belong to the team space, while each person can keep filter and display changes local unless they deliberately share those changes with the team.
What is the difference between epic-based and item-based views?
Epic-based views show epics as the primary level with items underneath. Item-based views show items as the primary level with sub-items underneath.
Can we use a board in a sprint team space?
Yes. Backlog, Planning, and Sprint modules can use board or table views. Kanban team spaces can do the same in Backlog and Kanban.
Which properties can table views show?
Item-based tables can show sub-items, epic, stage, label, owner, status, start and target dates, priority, and estimate. Epic tables focus on owner and dates.
Will changing a filter affect everyone?
Not unless you choose to share it. Filters and display options can stay local or be pushed to the whole team space.
Find the view that fits the question
Use tables, boards, epic views, and item views without splitting the team’s source of truth.