Renaming.
Adding fields.
Renaming.
Change belongs-to.
Added relationships.

Based on new design, Tickets are related to one another, children, and
can have a parent.
Time Functions.

Get a Ticket's Age, Time to Resolution (if resolved), and Idle (if
unresolved); all returns are as a Duration for better flexibility.
Comment Updates.

Aesthetics.

Changed Task to Ticket.

Added constraint that comment not be blank, and set it up so Grails will
use the textArea widget in scaffold views (if used).
Tickets have many Comments.

Comments is a SortedSet based on Timestamp.

Removed closingComment and detailedDescription, because really I think a
slick GitHub like interface where a Close & Comment button would be
nicer, lending to the Comments being more uniform.

The Comments relationship requires a minimum of 1, implying the first
comment is the description.
isClosed implied by dateClosed.

Unless there is need for a "soft-close" system, or for allowing Tickets
to be re-opened, dateClosed not being null is sufficient for determining
if the Ticket is closed or not.
Procrastination perterbation.

Added a method for determing if the due date was met.

Yes / No, or null if the Ticket isn't closed.
Added watchers.
Renaming.
Queue-Category relationships.
Removing ordering.

Ordering should be done by using a List with a Has-Many in the Queue.
More intuitive attribute.

Isn't 'hidden' a more inuitive attribute?
Subcategorization.
Altering Ticket.
Tweaking metrics.

Maybe an impact and priority at a fixed scale of 1..10 would work
better? I feel like it translates better, and would solve most
use-cases.
Added a QueueRole.

I dunno if it works the same, but should... right?

Supports many-to-many?
Statuses.