I would like users of my site when changing status of a case from Open to Closed also to be able to close commenting of the case's page. I know it can be done by going to Edit tab of the case node page and changing Comment settings to Read only. But not all the users have access to edit nodes. Moreover it would be much more comfortable to close commenting at the time of submission of last comment of the closed case.

Or if this is not possible why not to implement auto close after some time of inactivity on a page as it is done on Drupal.org project tracker? It is very odd when users find some old cases, which status were Closed long time ago, and start commenting them.

Comments

zero2one’s picture

zero2one commented
Status: Active » Closed (won't fix)

But what if a person thinks that the case is ok, but it is not, and closes it?

Should the case creator be able to change the status back to open, not fixed, ... or should he create a new case?

Won't fix this.

yngens’s picture

yngens commented

he could open new case. that is how it is done almost in all trouble ticket systems of, let say, hosting companies. the opposite way is a must for software issues discussing systems like here on drupal.org, since one issue could change its status continuously. but you should keep in mind that this module also used in service offerer - consumer relation systems, where any trouble is opened and closed once. if there is any other trouble, even it is similar, new ticket should be opened.

and i don't request to make functionality of this feature explicitly one or another way. the feature could be added as an option. why limit the possibilities of such a great module, instead of extending boundaries and reaching out more users?! i don't dare to change the issue's status respecting will of the maintainer, but if possible please make it active again. i really don't think that my request is for worse of the module.

mfb’s picture

mfb
they or he
commented

This is the kind of feature request that could be implemented via a small custom module exercising nodeapi.

But I think http://drupal.org/node/241692 should first be fixed such that all case modifications go thru nodeapi.