For what it's worth, I think it's a bug alright:

It looks like when a required field has not been filled-in, the error degrades to a primary key violation. When making the concerned field optional, there's no error at all.

So maybe it's worth to have a look after all ?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira