Task Panel Views
Summary: What Views Can I Use?
What Views Can I Use?
Views change the layout of the Tasks Panel to suit different ways of working. Each view adds something to the previous view.
You Can Use Seven Different Views:
[The Pad View:]
A simple, clean, rearrangeable list of tasks for creating simple checklists. Without all the details.
The Pad view is the most basic view.
The Table (List) View:
(Managing a queue, or selecting work by priority) A sortable table of every type of task visible.
The table adds sorting and searching to the view.
The Outline (Tree) View:
What we consider the 'default' view: A hierarchical list of various types of tasks.
The Outline view adds hierarchy and subtasks to the view.
[The Column View:]
(Single Stack: Sequentially Performed):
A graphical list of 'cards', organized into columns, each column representing a different state. With the option of sorting the cards in the column so that each card can be completed sequentially.
The Column View adds Images and Stages to the view.
The Board View
(Presenting Collections: Non-sequentially Performed. For Agile iterations and Kanban streams.)
The Board adds Stages and Sorting to the view.
[The Timeline View:]
(Scheduling work)
The Timeline adds time and scheduling to the view.
The Gantt View:
(Managing Dependencies and schedules)
The Gantt adds dependencies to the view.
Can I Switch Between Views?
Yes. Of course. Always. Tasks all the same in Runcible. Runcible views just display tasks differently.
Tip: Projects, Deliverables, Folders, and all the different task types are all stored as tasks with different properties and rules. So when you switch between views Runcible displays only presents the information differently. Runcible did not start out as a bug tracking or task list. We designed it from the very beginning as an accounting system for collaboration and tasks. And our various views have always been part of the architecture. We have even considered what a 3D view of projects would look like and experimented with it. We cut the feature not because it was difficult (its not), but because it started to become too easy to use Runcible as a game engine, and we felt it might expose us to misrepresentation in the market.