API Version History Update

Hey,

No — Codebeamer doesn’t let you update or import version history through the API or any import tool.

Here’s the reason and your real options:

Version history in Codebeamer is system-generated. Each version is created automatically when an item is saved, updated, or changed through the UI or via an API update call. Because of this, older versions (like historical baselines or edits) can’t be recreated or injected — they’re tied to database transaction timestamps and internal revision tracking.

If you import items through the API (for example, using /tracker/items or the CSV importer), Codebeamer will treat them as new records or as new versions of existing records, but not as historical ones.

What you can do instead:

• Use the tracker item import API to create current versions and then attach any old revision data as an attachment or a rich text field (e.g., “Legacy Version History”).

• Suppose you need the true historical versions to be visible in the system. In that case, you’d have to replay updates in order, through the REST API, so each change generates a new version — but that only builds sequential history, not back-dated versions.

Thanks,