All Products
Search
Document Center

Alibaba Cloud DevOps:Basic information management

Last Updated:Jul 10, 2026

Manage project fields, statuses, roles, and work item types at the organization level in Projex.

Basic settings

In Projex, navigate to Global Settings > Basic Settings to manage project fields, statuses, roles, and types. You can import organization-level configurations into project templates and projects.

The Project Fields page shows a list of existing fields, including their Field Name, Type, Creator, Creation Time, Description, and Actions. The default fields include Project Start Time (Date type), Project End Time (Date type), and Root Cause (Single-select List type). Click New Field in the upper-right corner to add a custom project field.

Project

  • Project fields store basic project information and are primarily used in project templates. You can create, edit, set default values for, and delete fields. System fields cannot be edited or deleted.

    • When creating a field, you must provide a Field Name (required) and Field Type (required). You can also add a Field Description and an English Name for internationalization.

    • When you delete a field, the system checks if it is in use by any project or template. If it is, a notification indicates the reference count and prevents deletion. Click View Details to see which templates or projects are using the field. You must remove these references before you can delete the field.

  • Project roles: Roles define specific responsibilities in project collaboration. You can edit, delete, and configure permissions for roles, but system roles cannot be edited or deleted. Default roles include administrator, product, development, test, O&M, and project manager.

    • To create a new role, click New Role. In the dialog box, enter a Role Name (required, max 20 characters), a Role Description (max 40 characters), and an English Name (for internationalization, max 100 characters). Then, click Create.

    • When you delete a role, the system checks if it is referenced by any project or template. If it is, a notification indicates the reference count and prevents deletion. Click View Details to see where the role is being used. You must remove these references before deleting the role.

    • To configure permissions, see Project Permission Operations.

  • Project status indicates the current stage of a project in its lifecycle. You can edit and delete custom statuses, but system statuses cannot be modified.

    • To create a new status, click New Status. In the dialog box, enter a Status Name (required, max 32 characters) and select a Status Phase (required), which can be Not Started, In Progress, Completed, or a custom phase. You can also provide a Status Description (max 40 characters) and an English Name (for internationalization, max 32 characters). Click Create to finish.

    • Deleting a status is irreversible. To delete the "Delayed" status, for example, click the Delete icon in the Actions column of the status list. A Delete Status confirmation dialog appears, stating that the action cannot be undone. Click Delete to confirm or Cancel to abort.

  • A project set role is an individual or team with specific responsibilities within a project set. These roles are defined based on the project set's needs and organizational structure. You can edit, delete, and configure permissions for project set roles, but system roles cannot be modified. Default roles include Administrator and Participant. The procedures for creating, deleting, and configuring permissions for project set roles are the same as for project roles.

Work item

  • Work item fields are attributes of work items such as requirements, bugs, and tasks. They can be referenced by project templates and project settings. You can view field details, but system default fields cannot be deleted.

    • To create a new field, click New Field. In the dialog box, enter a Field Name (max 32 characters) and select a Field Type. Available types include: Single-select List, Multi-select List, Date, Date Time, Integer, Decimal, Single-line Text, and Multi-line Text. After configuration, click Create.

    • When you delete a field, a prompt shows which work item types are using it. You must remove these references before you can delete the field. To do this, click the Delete icon for the field. If the field is in use, the dialog box shows where it is being referenced. Remove the references, then click Delete to complete the action.

  • Work item status indicates the current progress of a task or issue in its lifecycle. Different project management methodologies may define statuses differently. Default work item statuses cannot be edited or deleted.

    • To create a new status, click New Status. In the dialog box, enter a Status Name (max 32 characters) and select a Status Phase. Available phases include Confirmation, Analysis, Processing, Design, Development, Testing, Validation, and Release. Click Create to finish.

    • When you delete a status that is in use by a project template or project, the Delete Status dialog box indicates where it is being used (e.g., template name and referenced item). You must remove these references before you can click Delete to complete the action.

  • Work hour type categorizes the time that project members spend on tasks or activities. This helps project managers understand resource allocation, optimize workflows, and keep projects on schedule and within budget.

    • Create work hour types that suit your team. On the work hour type management page, click New Category in the upper-right corner. In the dialog box, enter a category name (up to 100 characters) and click Create. You can drag and drop existing work hour types to reorder them.

    • Deleting a category is irreversible. To delete a category, click the delete icon next to it. In the Confirm Deletion dialog box, click OK.

Type settings

The operations for managing custom work item types—such as editing, configuring, copying, and deleting—are generally consistent. System default types cannot be edited or deleted. The following sections use the original requirement type as an example.

  • Original requirement: Centrally collects raw requests from customers, such as default user feedback and client requests. It supports adding dependencies and tracking progress, including the delivery process. The following operations are available:

    • Editing a type allows you to modify its name, icon, description, and English name. When editing, you can configure the Type Name, Icon, Type Description, and English Name. System default types cannot be edited.

    • Configuring a type involves managing its field template, workflow, and description. On the type details page, switch to the Field Template tab to manage work item fields. The field list includes Status (single-select list, required, default: "--"), assignee (single-user select), priority (single-select list, required, default: "Medium"), Parent Project (single-select list), Feedback Type (single-select list), Participants (multi-user select), CC (multi-user select), tags (multi-select list), and due date (date). For each field, you can set whether it is Required, whether to Show on Creation, and its default value. The page also provides an Add Field button and an entry for Field Hidden Settings in the upper-right corner.

    • To copy a type, click Copy in the Actions column. In the Copy Type dialog box, enter a new Type Name and click OK. This creates a duplicate of the existing type configuration.

    • You can delete custom types, but system default types cannot be deleted.

  • epic: An epic groups scattered requirements into a single collection for assessing their collective value and cost. To create a new epic type, click New Type. In the dialog box, enter a Type Name (required), select an icon, and provide a Type Description and an English Name. Then, click Create.

  • requirement: Records and tracks requirements. You can define a workflow and add custom fields for management. Default requirement types include business, technical, and product requirements. When you create a new requirement type in the New Type dialog box, you must also select an icon from a predefined set to represent it.

  • task: A task tracks daily to-do items and progress as a related item within a requirement. In the New Type dialog box, in addition to entering a Type Name, Type Description, and English Name, you can select an icon from 8 preset options (lightbulb, code, list, triangle, document, file, link, and lightning) to represent the type. Click Create when finished.

  • bug: Manages bugs and can be linked to code changes for easier tracking by developers and testers. Default bug types include production failures and general bugs. Click New Type to create a custom bug type, which includes selecting an Icon from 10 available options.

  • risk: Manages project risks, sends timely notifications, and handles escalations. To create a new risk type, click New Type. In the dialog box, enter a Type Name (required), select an icon, and provide a Type Description and an English Name. Then, click Create.

Relationship settings

Configuring type relationships defines how team members collaborate and affects project efficiency. For more details, see How to customize work item relationships.