Projects in Papirus

When you have many tasks to accomplish, it might be convenient to arrange them in lists called “projects”. Projects resemble tags; a task can be part of a few different projects simultaneously.

Each project has administrators and a team. The person who created the project is its first administrator.

Administrators can add and remove participating team members, assign other administrators and change any of the project’s settings. A participant of the project’s team can add tasks to the project.

***

Projects have 2 access levels – shared access and limited access.

Shared access (set by default) means that all the project’s participants can see all the tasks. Limited access means that team members can see only the specific tasks assigned to them or ones they had already participated in.

Administrators always have access to all project tasks.

***

A project can be broken down into sub-projects. All of the project’s administrators and participants automatically become administrators or participants of a sub-project.

New participants can be added to a sub-project. Once added, they can all set tasks for the sub-projects or review the sub-project tasks (if the sub-project has shared access).

However, the participants of a sub-project never see the tasks of the head project or parallel sub-projects.

Sub-project samples:

1. Electronic Voting System project
• setting tasks
• development
• release 1.0 - November 10
• release 1.5 - November 25
• trunk
• testing
2. Animated film project
• script
• animation
• dubbing

By default, the access level of a sub-project is the same as the access level set for the head project, but it can be changed.

***

Projects can be used as groundwork for stage-by-stage task accomplishment by a few different people; this is called workflow.