id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	blockedby	blocking	branch_state	votes
202	add 'state' and 'votes' fields to bug report form	slyfox	winnie	"State:

Bugtrackers usually have separate combobox field to assign bug status (from what i see keywords field is used currently for this fragile semantic :]).

I, pesonally, thought 'keyworgs' field is a tag field to extend 'component' for search engine, but not a state of bug and I tried to fill them in :]

http://hackage.haskell.org/trac/ghc/ticket/2038 - keywords are used as tags. Very helpful when try to search existing bug or group interesting bugs (there's yet more fields to consired for inclusion).

http://bugs.xmms2.xmms.se/my_view_page.php - one of state tracking bug trackers out of the box.

Mantis states are (states are added/modifiable in SQL table, not very hard):
 * new
 * feedback
 * acknowledged
 * confirmed
 * assigned
 * resolved
 * closed

Those states reflect policy of closed-source companies :]
We can talk about our states a little more here and add our states.

From what i observe we need at least following states:
* new
* confirmed (we know the bug/feature, but no solution)
* yet-patch
* rework-patch
* resolved/committed
* closed
* what-i've-forgot

Votes:
Votes can be kept in (newly created) separate field: (like assign to) 'votes',
where devels and reporters, who tested patches can leave their names.

Thanks!"	enhancement	closed	major		adm		fixed