What I mean is that it makes sense to have a permission that would allow the issue reporer to update the discription of issues they reported. without giving them permission to update all the descriptions.
What I'm trying to solve by this suggestion is a usability issue, when a person logged an issue, realized that the spelling was not correct ( or that a specific part of key information is missing that should reside in the description and not in the comments ) and wants to correct their own error. And they can't.
While I agree that in certain scenarious this makes perfect sense, in many it doesn't. That's why I'm suggesting to add a permission to allow editing 'own' issues to the person who repoeted them.
This may be improving by added an 'owner' fields. And making the reporer the owner by default. In this case if an owner has permission to update their own issues the problem is solved. Later in the issue lifecycle the project administrator can change the issue owner.
In the bug tracking system our company uses (in-house) we do have the "owner" fields and it's quite useful to me.
I'm writing it here and not as a feature request in the issue tracking system because it's up Davin to decied if this makes sense (and in what degree) to his implementation.