XCA 0.8.1, may be related to bug 3047029
After completing the 'create key pair, create CSR, export CSR, import CSR, sign CSR into Cert, export Cert, import Certs' cycle we have a user repository with a signed user certificate and CA certificate(s).
Now we 'rinse, repeat' this cycle: we create a new CSR, with the same CN and for the same key, just different purposes.
This new CSR is added to the list (with Name <subject>_1) and instantly marked as signed, just as the first CSR.
This can't be of course, the new CSR wasn't presented to the CA yet. Also if you look at the Certificates page only the Cert of the first CSR is present, which can be determined from the Cert extensions.
Close the database and open the database again. Now only the new CSR is marked signed, the first is now marked unhandled. This is the inverse of the real situation.
Removing the new CSR, closing and opening the database shows the correct situation again.