The rdbms_common.Class.create_inner code now creates a new issue, after an initial check that an issue with the requested key doesn't exist.

However, if two such requests arrive simultaneously, a race condition may result where both sessions report the key as not existing, and then both continue creating the item.

Some backends lock the database during issue creation, but not all.
We are using the mysql backend, and we just found multiple user items with the same username. This is a critical problem.

Thanks,