Could you provide some details as to what aspects you don't think scale well? We know of databases with 10,000 issues and thousands of users.

I might have not been clear, or am not fully concerned about mantis features. Suppose we have scalation procedures, meaning that whn a help desk atetndant can not solve the issue, the issue must be scaled to its superior, so that a person with higher hierarchy can solve the problem.

If I understand correctly, you are looking for a method to reassign an issue to someone higher up in the development chain, if no actions are taken in a specified time. Another term for this is escalation.

We currently don't have an automated process for this. You could set up additional access classes, but you would still need the time based, and possibly a manual escalation process.

We'll keep this as a feature request.

Any chance that this will be added as a feature?

I'm also interested. I've been asked to custom-modify our implementation to support escalation. Suggestion: each project/severity combination would drive WHO to escalate to and the TIME elements of how escalated:

Project X, Severity Crash: After 1 hour escalate to ManagerJoe, after 4 hours escalate to DirectorSue, after 8 hours escalate to CEO_Wilma

Project X, Severity Trival: Do not escalate

Any feedback yet re: this request?

Also, it should be linked to 6008.