Plugin / Easy Project

Currently we support the following objects:

The Project object holds the high level project information: Project specification, lists of project tasks, project risks, files and mailing lists. This object also support status change and user comment email notifications. Projects have 4 custom fields allowing to customize this object for particular business needs. Project field 1 and Project field 2 are links to database objects. Object Fields: Manager A project manager. Once someone is assigned as Project Manager he or she gets a virtually full access to all project objects. Though, there are several operations which project managers are not able to perform: they are not able to ‘un-assign’ themselves, project managers also are not able to transfer project tasks between projects. Status A current project status. Project statuses are flexigle objects allowing to filter out completed and closed projects from the project view. Click See also to find out more. Start date A project start date. Finish date A project finish date. Project field 1 A custom project field. This field is linked to the Project Field 1 database object. Project field 2 A custom project field. This field is linked to the Project Field 2 database object. About Project description Team A list of the project team members. Tasks A list of the project tasks. Risks A list of the project risks. Mailing list A list of users who will receive project email notifications when a new comment to the project is added or the project status is changed. Project files A list of files associated with this project Project field 3 A custom project text field. Project field 4 A custom project text field.

This object is responsible for the project task management process. It allows setting both planned and actual taks deadlines and effort, task responsible and taks status. Object Fields: Project A project to which the task belongs. Priority Priority Status A task status. Type Task type. Responsible A responsible person. Planned deadline A planned task deadline. Planned effort A planned task effort. Actual deadline An actual deadline. Actual effort An actual effort. Mailing list A task mailing list. Task files A list of task files. Task mailing lists A task mailing list. Title hlp tasks title

The risk object used to simplify the project Risk Management process. Object Fields: Type Risk Type. This attribute is especially useful at the time of risk indentificaiton, as it holds a risk taxonomy, which allows to consider all possible risk sources. Status Risk Status. Allows to manage the project risk lifecycle. Impact Risk Impact. Use this field to indicate how important the risk is. Object owner A project team member responsible for risk handling Strategy This project rist attribute allows to indicate how to handle the risk. Probability A risk probability. High or low. This attribute is very useful when it is necessary to review the project budget and schedule. Project A project to which the risk belongs. Risk description Risk definition. Mitigation plan Risk mitigation plan description. It is always better to plan mitigation actions upfront. Mailing list The list of people who should be notified if something is changed. Risk mailing lists The list of people who should be notified if something is changed. Title hlp risks title

Main object to store project team member profile information. The object has four custom fields allowing its tuning different project team needs. The User Field 1 and User Field 2 fiels are links to database objects and are very useful for list attributes such as statuses and types. Object Fields: First name First name Last name Last name. Role User’s role. This field is not the same to project roles. While project roles are about which kind of work a project member performs, User Role rather defines general access rules to iProjectWeb interface. Admins have full access to everything. Guests do not have any accesses to anything. Project Managers have wider access rights to Risks objects and Project lists. People having a Project Manager role have a special project list view. It is essential to note that iProjectWeb highly relies on the ‘ownership’ model. This means that once a person becomes an ‘owner’ of project objects (project, task or file) he or she gets a full access to these items. Site user Allows linking a site user profile to the project team member profile. In order to establish the link just begin typing a site user name. This field is a suggestion list, so sooner or later it will find the necessary site user profile to connect with. Object owner A user who has rights to change this profile information (but admins). By default, it should be the user himself. Date of Birth Date of birth. This field may be changed to have a kind of ‘Employed from’ meaning. Email User’s email address. This address is used to send project-related email notifications. Email 2 User’s secondary email address. Mobile User’s mobile phone number. Phone User’s phone number. Skype id User’s Skype id. About Several words about the user. This text is displayed in the read only user profile view, which is accessible PM and Team member roles. User type A type of user. Another field which can be easily customized to suit particular project types. Photo This field allows to upload a photo as well any other image of JPG format to the profile. Thumbnail By default thumbnails are generated from the Photo images. They also may be downloaded separately. User field 1 A custom user profile field. Genders are given as a sample. This field takes its value from the database and is linked to the User Field 1 database object. User field 2 A custom user profile field. This field takes its value from the database and is linked to the User Field 2 database object. User field 3 A custom user profile text field. User field 4 A custom user profile text field. Project teams A list of project teams which the user is a member of. Project mailing lists A list of project mailing lists the user belongs to. Task mailing lists A list of task mailing lists to which the user belongs. Risk mailing lists A list of risk mailing lists to which the user belongs.

File management view. Provides direct access to project files, task files, and user images. Allows to remove files from the file storage. Object Fields: Documents A type of a document associated with the file. File type A document field associated with the file. Doc. id An id of a document associated with the file. Name A file name used when the file is being uploaded or downloaded. Size A file size. Web Indicates whether the file is accessed directly from the web server directory. The direct access to files is useful when a file content is not sensitive and it is better to allow browsers to store the file in cache. Photo pictures is a good example. Real Name A filesystem file name. Object owner A person who uploaded/owns the file.

The Priority object is indented to simplify Task prioritization and to share the same priority understanding across the project teams.

Project field 1 – a custom project field object. This object may be used as: – Project type: internal or external. – Project size: big, medium or small. – Project priority: high, medium, or low.

Project field 2 – a custom project field object. This object may be used as: – Project type: internal or external. – Project size: big, medium or small. – Project priority: high, medium, or low.

Files associated with a project. These may be: – Product requirements specifications. – Business cases. – Project status reports. – Project contracts. Object Fields: Object owner A file submitter or a file owner. Date A file upload date. Project A project to which the file belongs.

An object representing a project role. The final project role lists highly depend on business you run.

A list of project lifecycle phases. Good life cycle examples may be found in the following articles: – Systems development life-cycle – Product lifecycle management

The first part of the Risk probability/Risk impact dimensions. See the Composite Risk Index wikipedia article to read what this is about.

The second part of the Risk probability/Risk impact dimensions. See the Composite Risk Index wikipedia article to read what this is about.

Risk statuses reflect the Risk management method you are going to apply in your organization.

Risk management strategies. All techniques to manage the risk fall into one or more of these four major categories: – Avoidance (eliminate, withdraw from or not become involved) – Reduction (optimize – mitigate) – Sharing (transfer – outsource or insure) – Retention (accept and budget) See the Potential risk treatments wikipedia section for more information.

Risk types highly depend on the busines you run. The main goal of this object is to simplify Risk identification

Files associated with a task. These may be: – Task specifications. – Client reports. – Defect reports. Object Fields: Date File upload date. Object owner A file submitter or a file owner. Task A task the file object belongs to. File A file download link.

A list of Task lifecycle steps.

A list of Task Activities

A custom user attribute.

A custom user attribute.

This is a custom attribute which just allows having an addtional paramenter of user segmentation.