Syncing of fixes from JDK17 to 17.0.1 (17u-cpu) brings in the same 'resolved in build' value from 17 to 17.0.1 backport. Say if a bug is resolved in JDK17-b27 (for ex: JDK-8268716) , the corresponding 17.0.1 backport also shows resolved in build as b27 until next RE promotion where RE script updates it to the correct promoted build. So even though this discrepancy is interim, it still causes confusion until next RE promotion as the specified build is non-existent for 17.0.1.

Few more examples from 17.0.1-b03-
JDK-8270702 (changed from b30 to b03)
JDK-8270730 (changed from b31 to b03)

List of all such bugs (corrected on 07/21): issue in linked-subquery("issue in masterbug(\"project = JDK AND fixVersion = 17\")", Backport, outward) AND fixVersion in (17.0.1) ORDER BY updated DESC, summary ASC