This issue applies to the New User Experience in CA PPM 15.3 and newer releases.
Here are reasons fields can be missing from Blueprints:
1. Any attribute that has a API Attribute ID that is blank and read only. This can be checked by the following steps:
2. The following attribute data types:
Adding the API Attribute ID to these attribute not supported and these field types are not able to be added to Blueprints. This is referenced in the Blueprint documentation at: Edit Blueprint Details, Visuals, and Modules
3. See the Blueprint Project Fields section in Edit Blueprint Details, Visuals, and Modules for a list of named attributes that are not available to be included from the Project object.
4. In 15.3, custom attributes (outside the above exclusion of Custom time-scaled value (TSV), Attachments, and URL) cannot be added due to a defect fixed in 15.3 patch 1. See: KB000092718 - In the New UX, Unable to add Custom Attributes to Blueprints for more details.
NOTE: Parameterized lookup attributes are not supported, so while this attribute may show as available on the Blueprint list, it won't show any values in the New UX. See KB000095938 for more details, including how to remove this attribute type from the blueprint list.
For detailed information on getting started with Blueprints, reference New User Experience: Configure Project Blueprints
Reference KB000092718 - In the New UX, Unable to add Custom Attributes to Blueprints for information due to a defect fixed in 15.3 patch 1 (and higher)
Reference KB000092719 - How can I add a Custom Attribute to a Blueprint in the New UX?
Reference KB000093171 - What are the known New User Experience (UX) defects?
Reference KB000093166 - Where can I find New User Experience (UX) knowledge documents?
For 15.8.1, some functionality changes were introduced which helped to introduce more attributes that were previously unavailable:
Review the section on "Custom Master Objects, Subobjects, and Custom Virtual Attributes are Available in Clarity"