ALM Field Mapping
Configure how test result fields map to HP ALM custom fields using alm-mappings.xml.
Required ALM fields must be specified in the XML configuration. ALM will reject API calls that are missing required fields.
Overview
Most ALM projects contain custom fields (optional or mandatory) on Test, TestSet, and Run entities. Bumblebee's web portal provides a simple way to configure these mappings server-side.
Finding Custom Fields in ALM
Navigate in ALM to Project Entities → [entity type] → User Fields to view available custom fields:


Configuring Field Mappings
Navigate to the Mappings menu in the Bumblebee portal and edit the XML configuration:

Basic alm-mappings.xml
Each <mapping> element:
alm_field— the actual field name in ALM (e.g.TS_USER_01)label— the name of the HTTP request parameter that carries the valuedefault_value— fallback value if no parameter is passed (omit if not needed)
Shared Fields Across Projects
Mappings can be defined at URL or domain level and inherited by all child projects: