It's not possible to add/edit attachments after the issues has been posted

Sorry, but I think there is a misunderstanding. This was not a change request for the drupal.org issue tracking DB. This issue appears in my test installations and i assume it has something in common with the module.

Yes the permission is set. I gave this permission temporary to all users - still the same behaviour.

Comment for comment #10:
So here is a comment for comment #10. I can add here a attachment and i can change the context for this thread afterwards completly only by editing this decriptional text. The following text has not directly something in common with the next comments until #9.

When I can edit comments completly, why i can't edit the issue?
- I'm the owner of the issue?
- I'm responsible for my issue?
- I'ld assume as long as there is no comment I could edit "My issue"?
- Why i can add/edit/delete the attachment in the comment ?
- How about "Don't make me think?" in web usability

I've got your point and I understand this handling on drupal.org. But in general it's not logic when I set the permission "edit own project issues" that I can only edit the description and not the attachments. Actually the attachments are also a part of the description. How do you think about that?

I'ld propose following code alignments to fit the module to the requirements for everyone concerning this issue:

1.) Add an additional permission "edit own project issues attachments' into the "project_issue_perm()" function

...
function project_issue_perm() {
  $perms = array(
    'create project issues',
    'access project issues',
    'edit own project issues',
    'edit own project issues attachments',
...

2.) Align the case if-clause in the project_issue_form_alter() function

...
 case 'project_issue_node_form':
      if (isset($form['attachments'])) {
        if (isset($form['project_info'])) {
...

to

...
 case 'project_issue_node_form':   	
      if (isset($form['attachments'])) {
        if (user_access('edit own project issues attachments')){
...

Simple use case:
User A should review a appliation as a client. He has general knowledge in using internet applications but he is no developer, etc. He knows the issue tracking system and he likes it because it's nice, not quite complex and easy to use. He has already posted many issues. It's 5 min. before closing time and he want to submit the "last" issue before he leaves work.

There are currently following premesis for the last "issue":
1. He wants to get the bus home in the 6 minutes
2. In his image folder is the screenshot called "picture1.jpg" and a image "image1.jpg" with a private photo with his family. (Thats the way how he handles imags)

Following happens:
1. He defines the issue. No big thing for him... (in his mind: "hurry up")
2. Just attach the screenshot "image1.jpg" (in his mind: "hurry up - common upload a bit faster")
3. Selects the "Submit" button
4. Oh my god ! My familiy is in the issue tracking system
5. I need to delete it, oh that's not possible
5. Calls the administrator, who is not at his desk...
6. He misses the bus... ;-)
etc. etc.

Hello aclight and dww,

I really appreciate your feedback. There are no other use cases. It's only the case if someone adds a file that has nothing in common with the issue (people do mistakes). The editor is the "owner" of the issue and he is responsible for the post and he should be able to edit "his" issue if it's necessary.

I understand your points but in my opinion this is a simple additional feature that gives an added value for the module in follwoing points:
- The editing functionality of comments/issues is consistent (see also comment #4)
- It gives to the administrator the flexibility to choose if he activates the feature
- Enhancement of the usability for the users**

** How about this:
The user can edit the issue as long as there is no comment. That will correspond to your idea and it will give to module the added value that i've mentioned before.

That's all what could say concerning this.
I like the project modules! Great job! At least it's your decision.

Ahh I understand! That means people who only follow issues via e-mail are not always up to date as user using the website => infomation gets lost for some users.

So there would be another feature request: "The e-mail communication channel needs to get synchronised with web communication channel"

What do you think about that?