Actually, it now shows 2.2(3) and 3.0 as fixed versions, however, the release notes for the brand new 3.0, don't mention this bug as fixed (it doesn't mention the bug as an open caveat either):
http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/3-0/release/notes/cpi_rn.html#pgfId-90757