Tracker item data in Codebeamer is not stored in a single “tracker items” table. Instead, it’s spread across multiple tables because of the flexible data model that supports both standard and custom fields.
-
The main tracker item definitions and metadata (IDs, relationships, etc.) are stored in tables like tracker_item.
-
Field values (including custom fields) are stored in simple_field_value, which is why you saw your summary text there. Each field is tied back to a tracker item by ID, with separate rows for each field.
-
Lookup or reference fields can point to other tables depending on the type (for example, users, projects, or enums).
There isn’t a public “one-stop” schema document, but the key to navigating the database is to start with tracker_item, then join through simple_field_value (and related lookup tables) to extract the data you need.
If you’re working heavily at the database level, it’s usually best practice to use Codebeamer’s APIs instead of going directly against the database. That way, you avoid schema changes between versions and you get properly resolved values instead of raw IDs.
Thanks
