Hey Gary,
This is an idea that has been floated in the past. I don't think there is any "quick fix" for this with the current version of BugLog since the only unique "ID" available for a bug report would be its primary key on the database table, however given how BugLog works, this ID is not generated until AFTER the report has been submitted and the response sent back to the client app.
However, the good news is that this is something that has already been addressed on a development branch of BugLog.
This is a feature scheduled for the 2.0 release, but I am considering porting this feature and releasing it ahead of time as 1.9 release if this is something folks may want.
As developed, each report received will have a unique UUID that will be generated as soon as the bug is received, and will then be saved to the database.
Let me know if you have any thoughts,
Oscar