Introduction
This reference article explains all the configurable project settings available in Easy8. These settings define the structure, visibility, roles, workflows, and behavior of each project. Understanding these fields helps project managers and administrators maintain consistency and ensure accurate tracking.
Target Audience
- Project Managers
- Administrators
Definition of Project Settings
| Setting | Description |
|---|---|
| Name | The official name of the project. Required field (up to 255 characters). |
| Subproject of | Assigns this project under a parent project. Useful for organizing work in a hierarchy. |
| Description | A short summary or note about the project, visible to users who open the project. |
| Author | The user who originally created the project (read-only). |
| Project Manager | The person responsible for leading and managing the project. Can be changed. |
| Project Owner | A higher-level stakeholder or portfolio manager accountable for project delivery. |
| Default Milestone | A milestone automatically assigned to new tasks, if defined. Optional. |
| Default Assignee | The user who will be assigned by default to new tasks in the project. Optional. |
| Currency | The default currency used for budgets and financial tracking in this project. |
| Tags | Labels to help categorize or filter the project across views and reports. |
| Public | When enabled, the project is visible to all logged-in users, even if they are not members. |
| Planned | When checked, no email notifications are sent for this project. Used for draft/preparation mode. |
| Inherit Members | Automatically includes members from the parent project (if applicable). |
| Comments on Tasks Are Private by Default | When enabled, task comments are created as private unless changed manually. |
| Enable Copying of Task Comments to Parent Task | If enabled, comments from sub-tasks are copied to their parent tasks. |
| Priority | The importance level of the project (e.g., Regular, High). |
| Managed in Agile RM | Indicates the project is managed using Agile Resource Management tools. |
| Product | Associates the project with a specific product (if using product-based structuring). |
| Department | Indicates the department responsible for the project (e.g., PMO). |
| Phase | Optional field to specify the current phase or stage of the project lifecycle. |
Project Custom Fields
Project-specific fields defined by the administrator. Example custom fields may include:
- Product
- Country
- Department
You can select which custom fields are active per project.
Trackers
Trackers define the types of records (Tasks) used in the project. Available options include:
- Bug
- Deliverable
- Issue
- Task
You can enable only the relevant trackers based on the project’s purpose.
Custom Fields for Issues
These are custom fields added to tasks or issues within the project. Examples include:
- Backlog Refinement
- Required Skills
These fields appear in the task detail view and help with specialized project workflows.
Usage Notes
- Many of these settings can be edited any time during the project lifecycle.
- Changes to visibility, notification behavior, and trackers can impact team collaboration and data access.
- Using consistent naming, tagging, and custom fields helps improve project organization and reporting.
