KeyedIn - Projects (Legacy)

NOTE:
If you are managing projects with project workflows enabled, processing is different and is described at Projects (Project Workflows).

All planning is based on a project and all time and expenses are booked to specific projects. Therefore, a project must be created for each distinct block of work that is undertaken, whether chargeable or not.

The project is the main entity for planning and control. All other business entity records are linked to projects, either directly or via other business entities.

Select Projects from the Business Entities section of Administration and a search screen appears. You can then change the search (as described at Searching and Filters to list different records:

 

Click:

•Add to create.

•Create Data Template to add a record with spreadsheet format that defines the data to be used to import data

•Import Data to import and load project data from a spreadsheet template file.

Change the details shown for listed projects by clicking   and then selecting the columns to include or reverting to the default display.

For a listed project, you can click:

•Project name to view details within Projects.

•Client name to amend the client record.

•  then:

Edit	to make changes within the list.
Open	to edit the project.
Clone	creates a project at the same level as the selected one, so that it has the same parent and general details. You must specify a code for this entry and can change other details.
Add Child Project	only appears for projects above the lowest level and if the generation of child projects is allowed (set by the Administrator). It creates a project as a sub-project of the selected one. This will have the same project code plus a suffix. You can change any settings from those for the original project.
Code Converter	to change the code of the project if it is incorrect. All affected records will be updated.
Add Post	to start a new post.
View Posts	to list existing posts for the project (so you can add comments or create others.
Delete	to delete the project, after confirmation, providing it is not in use. If so, you have the option to delete all associated tasks and assignments. Choosing not to do this will prevent the project being deleted since an active relationship with another entity will exist. Deletion is also prevented if other records, such as timesheets and expenses, reference the project. However, you can make the project inactive.