3.0 - Project Editing Print

Starting a New Project

Creating a New Project can be started from within the Clients Profile projects tab, or from the main Projects Manager left and top drop-down menus. Starting a project from within the Clients Profile projects tab will automatically create a client relationship with the new project. Note: Associated project tabs will be hidden until the new project has been saved.

Undestanding of Project Fields

1. Project Name - this is a free-form input that should be used to uniquely identify the project
2. Type - this customizable field is used for organizing different major project types
3. Status - this customizable field is used for organizing overall project completion
4. Visible Status - this field defines the basic level of security associated with the project
5. Date Start - this is the date that the project has / will begin
   Note: Date Start will automatically be adjusted to accomodate Actions that have a date preceding the specified date. This feature can be disabled in the system configuration file.
6. Date Finish - this is the date that the project has / will be completed
   Note: Date Finish will automatically be adjusted to accomodate Actions that have a date following the specified date. This feature can be disabled in the system configuration file.
7. Client - this dynamic selection is used to relate the project with a specific client
8. Client Contact - this selection is used to relate the project with a specific client contact
9. Managed by - this is the administrator that is responsible for managing the project
10. Assigned to - this is the administrator that is responsible for maintaining the project materials
11. Project Details - this is a free-form textarea field that should be used to store general project objectives

Project Visibility

Project Visibility is controlled by the "Visible Status" select field found on the Details tab of a project. The Visible Status of a project determines whether non-related administrators will see the project, project actions, files, discussions, and time logs from the top-level list views. The options for Visible Status are:

1. All - all administrators will have access to view / edit the project
2. Manager Only - only the Managing administrator of this project can view / edit the project
3. Manager & Assigned - both the Managing and Assigned administrators of this project can view / edit the project

Project Actions

The Actions tab provides a two display modes for adding, managing, and removing actions that have been created for the project. The term "Actions" describes the dynamic hierarchy of Milestones, Groups, and Tasks that are created for the particular project.

1. Milestones - a top-level action node that is intended to maintain a collection of task groups.
   Action Milestones are intended to describe top-level objectives for the project.
2. Groups - a sub-level action node that is intended to maintain a collection of tasks.
   Action Groups are intended to be organizational units for managing collections of specific Task activities.
3. Tasks - the leaf nodes of the action heirarchy that are intended to indicate specific activities.
   Action Tasks are intended to be specific quantifiable activities that can be easily deligated and tracked against the time log.

Action Display Modes & Functionality

1. Tree View - the default view for Project Action management, the Tree View provides a hierarchical display of actions that can be edited, ammended, or removed for the project. The Tree View provides unique abilities that are not present in the List View:
   1. Drag-Drop Ordering - using your mouse you can Click-and-Drag the Action nodes to re-order them within the scope of the respective parent.
   2. Sub-Node Addition - each Action row has a icon that will trigger the creation of a new child node for the selected row.
   3. Milestone Addition - the Header row has a icon that will trigger the creation of a new Milestone Action.
   4. Action Editing - each Action row has a icon that will trigger the display of all editable fields for the selected record.
   5. Action Removal - each Action row has a icon that will trigger the removal of the Action, All Sub-Action nodes, and any Time Logs that are associated with the selected Action.
      Note: Because the removal of an Action elicits the removal of dependant Sub-Action and Time Log records, the removal option is only available from the Project Action Tree View. All removals are Permanent and cannot be undone.
   6. Time Log Stopwatch - each Action row has a icon that will trigger the Creation, Starting or Stopping of a Time Log event for the selected Action.
2. List View - the optional List View for Project Actions provides the Filters, Column Sorting, and Export features that are not found in the Tree View display. Similar to other list views within the system, clicking on the labels in the column header will change the sorting order of the Project Actions. Included with the List view are these primary functions:
   1. Sort, Filter, & Export - common to most List views throughout the system, the Action List View provides column sorting, record filtering, and export functionality.
   2. Action Viewing - the Label for each Action row is a link that will open the Project Tree View and expand the appropriate Action.
   3. Action Editing - each Action row has a icon that will trigger the display of all editable fields for the selected Action.
   4. Time Log Stopwatch - each Action row has a icon that will trigger the Creation, Starting or Stopping of a Time Log event for the selected Action.

Undestanding Action Fields

1. Name - this is a free-form input that should be used to uniquely identify the action
2. Type - this customizable field is used for organizing different major action types
3. Status - this customizable field is used for organizing overall action completion
4. Main Contact - this selection is used to relate the action with a specific client contact
5. Date Start - this is the date that the action has / will begin
   Note: Date Start will automatically be adjusted to accomodate Sub-actions that have a date preceding the specified date. This feature can be disabled in the system configuration file.
6. Date Finish - this is the date that the action has / will be completed
   Note: Date Finish will automatically be adjusted to accomodate Sub-actions that have a date following the specified date. This feature can be disabled in the system configuration file.
7. Managed by - this is the administrator that is responsible for managing the action
8. Assigned to - this is the administrator that is responsible for maintaining the action activity
9. Detail - this is a free-form textarea field that should be used to store detail eplaining the action objectives
10. Parent Action - this is a select list that can be used to move the node under a different parent.
    Note: Moving a node will cause all child nodes to be moved as well.

Project Tickets

The Tickets tab provides a list view of Support Tickets that have been associated with the particular project. From the Tickets tab you have the ability to open and create new tickets that will be related to the Project & Client.

Ticket Relationships - Support Ticket relationships are created and managed from within the existing WHMCS Support Tickets view. From the Support Tickets view you will find a new "Projects" tab added to the tab bar from which you can select what project to connect with the active ticket. When creating new tickets, you will first need to save the ticket before creating the Project relationship.

Project Files

The Files tab provides a list view of File Threads, each of which can contain any number of versions for the specific file. A "Thread" logic is used to provide a basic method for versioning, however the Thread format may also be used as a grouping system for tracking files as a collection. From the Files tab you have the option to Open, Remove, or Create a "New Thread".

File View - When opening a File Thread, a new "File View" tab will be created where you will be able to manage the files that have been added to the File Thread. Files are listed in the order they were created, starting with the most recent. Each file version can be edited or removed with the exception of the first file which can only be edited. Deleting a File Thread will delete all files that are stored for the thread.

Project Discussions

The Discussions tab provides a list view of Discussion Topics, each of which can contain a thread of discussion posts similar to a common forum format. While Discussions are designed to be a collaborative tool for tracking a decision making process, the Discussion feature may also be used to store relevant project information in an organized container. From the Discussions tab you have the option to Open, Remove, or Create a "New Thread".

Discussion View - When opening a Discussion Topic, a new "Discussion View" tab will be created where you will be able to view the posts that have been added to the Discussion Topic. Posts are listed in the order they were created, starting with the most recent. Each discussion post can be edited or removed with the exception of the first post which can only be edited. Deleting a Discussion Topic will delete all posts that are stored for the Discussion Topic Thread.

Project Time Logs

The Time Log tab provides a list view of Time Log records specific to the active project. The Time Log tab provides the ability to manage the following:

1. Time Log Editing - each Time Log row has a icon that will trigger the display of all editable fields for the selected record.
2. Time Log Removal - each Time Log row has a icon that will trigger the removal of the Time Log. Note: All removals are permanent and cannot be undone.
3. Stopwatch Stop - each Time Log row displays the time Elapsed for the specific record. A icon is displayed alongside the Elapsed time of active Time Logs, providing a trigger for stopping the active Stopwatch.

Understanding Action Time Logs

All Time Log records are associated with a specific Project Action. The association of a Time Log is established upon the creation of a Time Log record, which can be performed from any of the Action Tree or List views found throughout the system. Once a Time Log has been created, it can be modified or removed from any of the Time Log list views. There are two options made available when creating a Time Log event:

1. Stopwatch Feature - by default a Time Log event is a trigger that creates a new Time Log record marked with an Active timer status. This default Stopwatch feature is used when actively tracking the activity of an Action Task.
2. Manual Entry Feature - alternatively, a Manual Time Log event can be created that will be marked as Complete when saved. This optional Manual feature is useful when recording a history of Action Task events that have already been performed.

Understanding the Stopwatch Feature

The Time Log Stopwatch is designed to actively track the time elapsed between creating and manully stopping a Time Log event. It is important to consider that there are no restrictions on the number of Time Log events that can be running simultaniously, nor do Time Log events have a limit on duration.

Rogue Time Logs - In the event that a Time Log Stopwatch has been left unattended, the Time Log list view provides the opportunity to edit and adjust the recorded duration. The Time Log list view found under the top-level Project Management display is a useful location to review and manage Time Log events that are actively tracking time elapsed.