Ticket #202 (closed enhancement: fixed)
add 'state' and 'votes' fields to bug report form
Reported by: | slyfox | Owned by: | winnie |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | adm | Version: | |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Branch state: | Votes for changeset: |
Description (last modified by styx) (diff)
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!
Change History
comment:3 Changed 16 years ago by slavazanko
review, approved and cleanup - it's a part of workflow and need add to standart trac workflow. Like this:
conf/trac.ini:
[ticket-workflow] ... review = new,assigned,accepted,reopened -> accepted review.permissions = TICKET_MODIFY review.operations = none approved = * -> * approved.permissions = TICKET_MODIFY approved.operations = none cleanup = * -> * cleanup.permissions = TICKET_MODIFY cleanup.operations = none
Also, some additional fields may be add:
[ticket-custom] vote = text vote.label = Votes by patch branches = text branches.label = Branches for this ticket commited_master = checkbox commited_master.label = Commited to master commited_master.value = 1 commited_stable = checkbox commited_stable.label = Commited to stable commited_stable.value = 1
More info:
https://projects.math.leidenuniv.nl/trac/howto/wiki/TracTicketsCustomFields
also, some more fields can be added:
conf/trac.ini:
[ticket-custom] vote = text vote.label = Votes by patch branches = text branches.label = Branches for this ticket commited_master = checkbox commited_master.label = Commited to master commited_master.value = 1 commited_stable = checkbox commited_stable.label = Commited to stable commited_stable.value = 1
And, of course, need to change trac-reports
comment:4 Changed 16 years ago by slavazanko
Ups... sorry, in previous comment I wrote twice some thinks... with different translate to English :)
comment:5 Changed 16 years ago by slavazanko
- Owner set to winnie
- Status changed from new to assigned
comment:6 Changed 16 years ago by slavazanko
BTW, if we need to close tickets with resolution 'invalid','wontfix' or 'duplicate' without 'testing' stage, need to add in trac.ini:
[ticket-workflow] ... close = new -> closed close.operations = set_resolution close.set_resolution=invalid,wontfix,duplicate close.permissions = TICKET_MODIFY
comment:10 Changed 15 years ago by styx
- Status changed from assigned to testing
- Resolution set to fixed
- severity set to no branch
comment:12 Changed 15 years ago by slavazanko
- Version 4.6.1 deleted
- Type changed from defect to enhancement
- Milestone future releases deleted