Projects and sections: how work is organized
A project in Taska brings together work on one topic, and the actual work happens in its sections: boards, knowledge bases and roadmaps. A project can have one section or several.
Project
You might create a separate project for launching a website or releasing an app. Every project belongs to one space, personal or team. All of a space's projects are listed on the space page and in the sidebar under the space name.
A project has a name, sections and the people who work in it. In a team space, the team's members see the project. You can also invite someone from outside to a single project, and they won't see the team's other projects.
Three kinds of sections
The actual work happens in a project's sections. There are three kinds.
| Section | What's in it | What it's for |
|---|---|---|
| Board | Tasks in columns. A column shows the task's status | Day-to-day work: who is doing what and at which stage |
| Knowledge base | Articles and folders | Guidelines, instructions, agreements and notes next to the tasks |
| Roadmap | The project's epics on a Gantt chart | Plans for months ahead and epic dates |
A project can have several sections of the same kind. For example, designers and developers can each have their own board, and the release plan and the marketing plan can sit on separate roadmaps.
One section or several
While a project has one section, it's a simple project. It opens straight on that section, for example on its board.
When you add a second section, the project becomes an extended project. It gets an “Overview” page with a card for each section, and section tabs appear in the header, such as “Boards” and “Knowledge”. If the project has a board, there's also a “Workflow” tab with a map of how tasks move between boards. An extended project doesn't turn back into a simple one. See “Simple and extended projects: how a project grows” for details.
How to move between sections
In an extended project, you can open a section in three ways.
- The tabs in the project header. On a narrow screen, the tabs show only icons.
- The section name in the header. Click it to open a list of all the project's sections.
- The sidebar. An extended project's sections are listed under its name.
Sections and your plan
Plans count sections, not projects. A simple project takes up one place in the limit. In an extended project, every board, every knowledge base and every roadmap takes up a place. The overview, “Workflow” and the time report don't count as sections.
| Plan | Sections in a space | Boards in one project |
|---|---|---|
| Free (personal space) | 5 | 1 |
| Pro | 300 | unlimited |
| Free Team (team space) | 10 | 4 |
| Business | 500 | unlimited |
On the free plans, a project can have one knowledge base and one roadmap. The counter next to the space name on the space page shows how many places are used, such as “7 / 500”. Archived projects and sections don't count towards the limit. See “Archiving projects and sections”. The plans are compared in “Taska plans and feature comparison”.
Example
The Aurora team runs two projects in the “Aurora product” team space.
- “Aurora” is an extended project. It has the “Design”, “Development”, “Testing” and “Release” boards, a knowledge base and the “Release plan” roadmap. That's 6 sections.
- “Launch marketing” is a simple project with one board. That's 1 section.
Together, the projects take up 7 places in the team's section limit.