Project hierarchy and general management

---

The following is a list of general Project requirements proposed for the 1.0 functionality.

Create new Project

• Users with tiki_p_admin_projects should be able to create and subsequently maintain the system attributes for a new project. The system should assign a unique project Id to each new project, log who creates it and when, as well as tracking version history.
• The Project system attributes should be as follows:
  • assign an initial project name and description - can be subsequently updated but a history should be kept.
  • a parent project should be selectable (sets a child_of project Id signifier) so that a hierarchy of projects can be created (i.e. as an overall programme)
  • assign a designated project manager from the existing users - should only be selectable from a list of users with tiki_p_edit_projects permission. The userId should be stored.
  • assign to Categories - so that all the usual category access controls can apply
  • set some display options? not sure what these are yet

Once a project has been created it will then appear in the table displayed when using the "List Projects" menu item.

"Buttons" at the top of the projects table listing screen should be:

• Manage Resources: only visible to users with tiki_p_admin_projects permissions
• Admin Projects: only visible to users with tiki_p_admin_projects permissions

The "Action" icons for each individual Project, which by convention should be in the last column of the 'list' table, are:

• View: ONLY the designated project manager + assigned team members for the individual project plus users with tiki_p_view_projects permission for the project (observing categorisation) should be able to see the View icon and access the project view screen (see later)
• Edit: ONLY the designated project manager for the individual project plus users with tiki_p_edit_projects permission for the project (observing categorisation) should be able to see the Edit icon and access the project edit screen (see later)
• Assign Team: ONLY the designated project manager for the individual project plus users with tiki_p_edit_projects permission (observing categorisation) for the project should be able to see the Assign Team icon and access the assign team screen (see later)
• Create/Assign Tasks: ONLY the designated project manager for the individual project plus users with tiki_p_edit_projects permission (observing categorisation) for the project should be able to see the Tasks icon and access the project task screen (see later)

View a Project
As discussed above a View Project screen would display a detailed 'report' for the Project and should include the following:

• Project name
• Project description
• Project Manager
• If part of a programme: Parent project(s) - ideally a tree showing how the specific project fits into an overall programme + the manager of the top programme and the managers of other sibling projects should ideally be visible
• Current project Jeopardy Status (Red/Amber/Green) with a history kept
• Project priority: 1-lowest, 5-highest with a history kept
• Project start date
• Project target finish date with a history kept
• Project actual finish date
• add more here later

Edit and maintain a Project

As discussed above, an Edit Project screen should allow the following detailed project attributes to be set/updated for the project:

• updates to the project title and description
• jeopardy status for the project - on a Red, Amber or Green basis
• formal start date for the project
• target completion date for the project (history kept)
• actual completion date for the project - when it is completed!
• add more here later

Assign Team members to a Project

As discussed above, an Assign Team screen should allow the following to be carried out:

• existing users to be selected from a pick list and assigned to the Project team as an available Resource. The pick list should only show users in the system that are 'eligible' to be project team members by have tiki_p_can_be_in_project_team
• current team members are summarised in a table with an Actions column that allows the following:
  • Current tasks: lists all tasks assigned to the user in this project
  • User page: links to the user's personal page, if it exists
  • Remove: removes the user from the Project team (this implies that this user would have to be removed from all the Tasks that have been assigned to them in this project)
  • add more here later

Create/Assign Tasks within a Project

As discussed above, an Assign Task screen should allow the following to be carried out, not sure if this could/should be the existing Task screen once it has been 'enhanced', or a new screen:

• define an individual Task where the project signifier is set to the current project
• all other aspects as set out on the Project Management - Existing Task functionality and Project Management - New Required Task functionality pages

Table of contents for section:

Table of contents for main document: