Hi,

In Odoo, properties on tasks are stored as a JSON dictionary where the key is an internal identifier (like ec679a2a7188466a) and the value is what you entered (like "alia"). When exporting, Odoo doesn’t flatten this structure, so you see both the internal key and the value instead of just the user-friendly text.

Option 1 – Use custom fields instead of properties:

If you create a real custom field on the project.task model (using Studio or development), the data is stored directly in that field. This means when you export, you’ll get clean values such as "alia" without the extra technical identifiers. Properties are flexible but less reporting-friendly, so custom fields are the better long-term choice if reporting and exporting matter.

Option 2 – Add a computed field for export:

You can add a new computed field that pulls the property’s value out of the JSON. For example, a field like Employee (Property Value) can read from the property dictionary and return only the value. When exporting, you simply select this field instead of the raw properties. This works well if you want to keep using properties but need clean exports.

Option 3 – Reporting view or server action:

If you don’t want to modify the model itself, another option is to create a reporting SQL view or a server action that processes the JSON and extracts only the values. This way, you can generate reports or exports that ignore the internal IDs and only show readable values, without changing how properties are stored.

Hope it helps