= Freezing Bugs =

In some cases, the project team may decide that a bug has received as much input as is necessary from the users, and that it this point it would be best to 'freeze' it and disallow any further comments.


== User Interface ==

On the bug page, the project owner and bug supervisor see an extra action link - 'Freeze this bug'. If clicked, the user is taken to a confirmation page, where they can either go back for confirm that they would like to freeze the bug. Once the bug is frozen, the action link changes function to 'unfreezing'.

For all other users, frozen bugs appear just like normal bugs, but the section for adding new comments is removed, and an informational message appears at the top, announcing that this bug is frozen, and no longer accepts new comments.


== Schema Changes ==

Add a new column to the Bug table - frozen, BOOLEAN, which deaults to FALSE.

== Code Changes ==

 * Add the frozen field to IBug and Bug.
 * In Bug.newMessage(), throw an 'Unauthorized' error if we try to add a user that isn't a project owner or bug supervisor tries to add a new comment to a frozen bug.
 * In the email interface, don't attempt to add new comments to frozen bugs. Instead send a message back to the user, letting them know that the bug is frozen and their message couldn't be added.
 * In the view / template for bugs, don't display the add comment section in frozen bugs, and add an informational message about the bug being frozen.
 * In the view / template for bugs, add a new action for freezing / unfreezing bugs, which is displayed to users who can change that flag.