Issue Codes Tag Issues, Not Activities

What a planner means

Issue codes classify issues, not activities. Oracle: they are enterprise-level. Assign a code value to issues across multiple projects so you can search and view issues by that criterion.

Oracle example: code Severity with values High, Medium, Low. Same idea for responsibility, subproject, or any other classification you need. Email notification can fire when an issue is assigned a specific issue code.

This is not the issue itself (PROJISSU), not a threshold (PROJTHRS), not an activity code, not a project/resource/role/assignment code, and not a generic issue UDF. The Enterprise Data page has separate options for issue codes and issue user-defined fields. See Issues and Thresholds — Not Schedule Logic, Activity Codes Are a Pick-List, Not a UDF, Project Codes Tag Projects, Not Activities, UDFs Are Typed Extra Fields, Not Activity Codes.

Create (EPPM): Administration → Enterprise Data → Issues → Issue Codes → Add Code. Name must be unique. Optional Secure makes the code read-only for users without the privilege (the option appears only if you have that privilege).

Values: select a code or a value → Add Code Value → unique Name, Description; Move Up / Move Down. Oracle UI: values at the same level are siblings; subordinate values are children. The Issue Codes page is a hierarchical list (Expand All / Collapse All).

Assign: Projects → Issues → select an issue → Codes detail window → Assign… → select a code → Save. Oracle: you can assign only one issue code at a time; click Assign… again to assign another. Also from the My Issues portlet. That is a UI step, not a “zero or one per type” rule. REST/API does not state zero-or-one for issue codes. Do not invent that cardinality.

XER

Oracle’s project XER data map lists PROJISSU (Issues), PROJTHRS, ISSUHIST, UDFTYPE, and UDFVALUE. The cited TOC has no issue-code type, value, or assignment table. PROJISSU has no issue-code column. Do not invent ISSUETYPE / ISSUCODE / ISSUCAT (or any other name) on a project XER parse.

Issue codes are enterprise data (Enterprise Data → Issue Codes), not a project-map %T.

API (not XER column names). Do not write these as %T columns.

REST/Integration API: UDF codes, also known as issue codes. Their UDF type is Code. Code-type UDFs may only be assigned to ProjectIssues. Assign with the UDFValue service (ForeignObjectId = the issue). REST: UDF codes are stored in a non-hierarchical list. That contradicts the UI sibling/child wording; write both. Do not invent a parent column on a missing XER table.

UDFCode: CodeTypeObjectId, CodeTypeTitle, CodeValue (“short ID that uniquely identifies the code within the code type”), Description, SequenceNumber, ObjectId (plus Create/LastUpdate user and date).

UDFTYPE / UDFVALUE on the project map are the general UDF tables (see UDFs Are Typed Extra Fields, Not Activity Codes). UDFVALUE.udf_code_id is labeled Code. Do not treat every UDFVALUE row as an issue-code assignment, and do not invent that udf_code_id is an ISSUETYPE FK.

Microsoft Project

Desktop Project has no issue-code dictionary. Do not map a P6 issue code to an outline code, a WBS code, a custom field, or a Project Online / SharePoint issue list.

Don't

• Treat an issue code as PROJISSU, PROJTHRS, or ISSUHIST.
• Treat an issue code as an activity, project, resource, role, or assignment code.
• Invent an issue-code table in a project XER parse.
• Invent a “zero or one per type” rule (Oracle did not say that here).
• Map an issue code to an MSP outline code, WBS code, or TextN field.
• Collapse issue codes into ordinary issue UDFs without saying the API calls Code-type UDFs issue codes.
• Treat the UI hierarchy as an XER parent column.