Predefined and Custom Field and Converting Item Types

Published Date: July 19, 2026
Validated: Yes
Audience: Everyone
Products and Versions Covered:

Jama Connect® version(s)
- Cloud/CVC
- Self-hosted

Summary

This article explains the difference between predefined and custom fields in Jama Connect and how each affects item type conversion. Readers will learn that predefined fields help preserve values when an item changes type, while custom field values may be lost during conversion. The article also explains how consistent field choices across item types can improve data retention and make it easier to manage and report information.

Resolution

Best Practices

When designing item types, use predefined fields whenever possible. Predefined fields are supported consistently across Jama Connect and help preserve field values when items are converted from one item type to another.

Use custom fields only when the required information cannot be captured with an existing predefined field.

If you expect similar information to be used across multiple item types, configure custom fields consistently by using the same field type, the same pick list (when applicable), and the same field label (each highlighted in yellow below).

By following these conditions, it helps to provide a consistent user experience and allows the field to appear in the same columns across different item types (see below).

Before introducing new item types or converting existing items, validate the behavior in a test project. Confirm that important field values are retained and that reporting, filters, and views continue to meet your organization's needs.

Planning your field strategy early can reduce administrative effort, improve data consistency, and help avoid unexpected data loss during item type conversion.

Field Type Comparison

Topic	Predefined Fields	Custom Fields
Item Type Conversion	Values are retained when converting between item types using the same predefined fields	Values are not automatically retained during conversion
Search	Indexed and searchable without the database field name	Search relies on the field name
Reporting & Extracting Data	Provide a standardized schema that can simplify reports and integrations spanning multiple item types.	Offer great flexibility but may require additional mapping when different item types use different custom fields for similar information.
Flexibility	Limited predefined field set	Supports additional field types such as rollup, calculated, URL, and Item of Type fields.

Additional Resources

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement below.

Related to