ReqIF Import - Access to the report

[MJ_14295943]

Hi,

I really need to raise this again because I honestly can't believe this is still the case. I’m fairly certain I mentioned it about two years ago, but I hadn’t run into it again until now – and I’m genuinely shocked.

After completing an import, I receive an email notification. However, in order to view the associated warnings and failures, I’m required to upload the same REQIF file again just to access the report. This feels incredibly counterintuitive and inefficient.

Is there any plan to improve this? It’s hard to understand why the system can’t directly link to the report from the import itself.

Duration	9:49.008min
Changes	Tracker created updated deleted failures/warnings .... 71 2169 0 15 ... 83 1876 0 18 ... 0 1988 0 0 ...  236 2621 0 0

You can find more information about this ReqIF import, e.g. the configuration settings or individual item changes, by

1. Clicking on the Target Project link above
2. Going to Admin → General → Import → ReqIF sources …
3. Clicking on the Source XXXX
4. Locating and expanding the Import by mjeanren at Nov 04 2025 08:24

[pshashipreetham]

Hey,

You’re running into a known limitation of the current ReqIF Import implementation in Codebeamer. The platform does not persist the detailed ReqIF Import Report so it can be accessed via the notification link. The notification email always points to the import-source object, but the actual report is generated only during the import session and is not stored.

Where things stand today:
The product team is aware of this gap. Persistent import reports and direct links from notification emails are on the internal improvement backlog, but not yet scheduled for a release. As of CB 2.21.1, this behaviour is expected.

Practical path forward:
Use the Import Source (Admin → General → Import → ReqIF sources) as the entry point. Open the specific source, locate the timestamped import under “Import History,” and download the report directly. This is the only supported method until the product team ships a persistent-report enhancement.

If your environment requires long-term traceability of import results, there are two viable workarounds:
• Automate the ReqIF import via Swagger API, capture the return payload, and archive the result on your side.
• Wrap the import in a small external service that stores the ReqIF report and provides your own direct link.

Thanks,