Bug Tracker Cleanup

Please suggest what can be improved, removed, replaced, etc.

Fields to stay (reordered)

ID - renamed Ticket ID
Reporter - renamed Submitted by
Created
Last modified by - renamed Lastmod by
Last modified - renamed LastModif
Subject
Category
Version
Feature
Status - renamed Resolution status
Description
Linked items - renamed Related-to
Demonstration - maybe we would need to be able to add several show intance to be able to show the bug in different versions?
Resolution

Rating
Status (open/pending/closed) - workflow is more complex than this, lets use categories instead
Workaround
WishList Team - Workflow State
WishList Team - TODO - Confirm Bug on Trunk
WishList Team - TODO - Find on 9x
WishList Team - TODO - Find Culprit
WishList Team - Info for Review & Culprit
WishList Team - If Culprit Found - REVISION
WishList Team - Additional Info for DEV Team
WishList Team - Notes to Self
WishList Team - Last Reviewed
Rating-old
Status - "Do not use. Data here will be merged into the other categories."

Sprint (or Project?) - it would be nice to be able to group issues for sprints (eg: tasks dervide from a Tikifest) or internal projects. Categories could be used
Tags - allow tagging
Files - consider dropping attachments tab and use Files field type instead. Problem: what to do wit items with attachments, how to migrate them
Assigned to - the idea is not to assign to individual but to a certain "Development Crew" (group similar to Teams but more Development focused), e.g. bug related to UI should be first assigned to "UI Developers", a wish related to blogs should be assigned to "Blog Developers", etc. It should be probably multiselect field so more crews like "PHP Developers" and "Performance" crew can be assigned at the same time. After saving the item, the members of the crew(s) receive notification by email. As the people are members of the crew they are probably more interested in fixing or enhancing the feature than receiving and scanning all notifications of whole Tiki bug reports and wishes. A member of the crew should take care of the Resolution status (workflow) step and when done the same volunteer from the crew passes it further to another crew or team until last step is done and the item gets closed...
Taken by - a developer assigns the item to him/herself so we know if someone is working on it and who it is

would be better to have comments below the details of the issue, not on a separate tab
reduce explanation text for demonstration section or move it to a popup, it takes too much space