All Project Settings Explained

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.

Task types

Task types (formerly "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.

Task priorities

Task priorities are defined globally in Administration >> Categories >> Task priorities. In Project settings >> Task priorities, you can select which of these priorities are available in the project. This lets you show each team or customer only the priorities that are relevant to them, for example the ones defined in their contract.

How it behaves:

No priority selected (default): all globally active priorities are available, the same as before the feature. All existing projects start in this state after the upgrade.
Some priorities selected: only the selected priorities are offered in:

new task and edit task forms,
inline and quick edit,
bulk edit,
the priority filter in the task list,
Help Desk SLA settings.

Validation: saving a task with a priority that is not allowed in the project is rejected, including via the API.
Existing tasks: a task that already has a priority the project no longer allows stays valid until you change the priority. The dropdown then offers only the allowed priorities, so the old value cannot be selected again.
Bulk edit across projects: only priorities allowed in all selected projects are offered. A project with no selection does not narrow the list.
Subprojects: the priority filter on a parent project includes priorities allowed in the parent project and all its active subprojects.
Help Desk SLA: if an SLA uses a priority that is no longer allowed, the SLA shows the priority field as empty. The saved value is kept until you edit the SLA.
Project copy: the priority selection is copied with the project.
Tags: administrators can tag priorities. In project settings, click a tag to filter the list; Check all and Uncheck all then apply only to the filtered priorities.

The Task priorities section is visible only when the Task tracking module is enabled in the project.

Difference from filtering tasks by priority: a task list filter only hides tasks from a view. The project setting limits which priorities can be selected at all.

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.

Custom Fields for Issues – Available values

Custom fields and their values are defined globally in Administration >> Custom fields. In Project settings >> Custom fields, you can choose which values of a list-type custom field are available in the project. Each project then offers only the values that are relevant to it, while the field stays defined in one place.

How it behaves:

Scope: applies to task custom fields of the List or Key/value list format.
No value selected (default): all globally active values of the field are available, the same as before the feature. All existing projects start in this state after the upgrade.
Some values selected: only the selected values are offered in:

new task and edit task forms,
inline edit on the task detail,
bulk edit,
the custom field filter in the task list.

Order of values: values keep the order defined globally on the custom field. The project selection only filters them.
Validation: saving a task with a value that is not allowed in the project is rejected, including via the API.
Existing tasks: a task that already has a value the project no longer allows stays valid until you change the field. The dropdown then offers only the allowed values, so the old value cannot be selected again.
Bulk edit across projects: only values allowed in all selected projects are offered. A project with no selection does not narrow the list.

The Custom fields section is visible only when the Task tracking module is enabled in the project.

Difference from filtering tasks by a custom field: a task list filter only hides tasks from a view. The project setting limits which values can be selected at all.

Project Workflow

By default, every project uses the global workflow defined in Administration >> Workflow. From version 15.10, you can override it for a single project. The project then has its own status transitions and field permissions, while the global workflow stays unchanged.

You can use the same task type (for example Epic) in all projects, with a different workflow in some of them. Filters and reports across projects still work with one task type. You no longer need duplicate task types such as Epic 1 and Epic 2 to get different workflows.

Where to find it: Project settings >> Workflow. A status message in this section shows whether the project uses the global workflow or a project-specific one.

Available actions:

Edit workflow: Set status transitions and field permissions per role and tracker for this project only
Copy from project: Use the workflow settings of another project as a starting point
Copy to projects: Apply this project's workflow settings to several other projects at once
Reset to global: Remove the project-specific settings; the project uses the global workflow again

The override affects only the project where you set it. Other projects and the global workflow stay as they are.

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.