0002442: better handling of status FEEDBACK (status change after feedback by bugnote) - MantisBT - Signup temporarily disabled due to spam

ID	Project	Category	View Status	Date Submitted	Last Update

0002442	mantisbt	bugtracker	public	2002-08-30 06:04	2010-04-23 23:22

Reporter	brody	Assigned To	vboctor
Priority	normal	Severity	feature	Reproducibility	N/A
Status	closed	Resolution	duplicate
Product Version	0.17.3

Summary	0002442: better handling of status FEEDBACK (status change after feedback by bugnote)
Description	when a bug needs feedback (either by reopening it or by setting it to state 'feedback'), the normal way to give feedback is to add a bugnote. After this has been done (the bugnote sent), the state should be changed to: ASSIGNED, if a handler exists, otherwise to NEW or CONFIRMED.
Tags	No tags attached.

jfitzell 2002-08-30 12:01 reporter ~0003212	Hmm... no I disagree on this one. NEW should only be for new bugs and CONFIRMED should only be when you have actually confirmed that the bug is a problem. If you were awaiting feedback you presumably have not confirmed that it is a problem. I think the correct behaviour is appropriate, the handler can decide whether they have enough feedback to continue with the work or not.

brody 2002-09-02 01:37 reporter ~0003225	In general I understand your objection. Do you think a solution could be to not use the state FEEDBACK, when a bug gets reopened. It's not necessarily that reopening a bug needs a feedback. Maybe the reopener can decide the state from a list of valid states.

jfitzell 2002-09-03 02:09 reporter ~0003227	I never really understood why it went to feedback either so I have no objections... have to see what other developers say...

Luebbe 2002-09-03 03:09 reporter ~0003229	I suggest to eliminate the workflow from the code and to put it into the database. Implement something like a state machine that pulls the allowed states connected to an action from the database and puts them into a combobox. This way anyone can implement his own workflow. Greetings Lübbe

Matt_wc 2004-09-12 22:45 reporter ~0007535	'I suggest to eliminate the workflow from the code and to put it into the database.' - I agree with this. We reworked the code/config to revamp our workflow. It seems to me that putting the workflow into the DB would make it easier to change (via web vs config file) and produce reports.

bpfennig 2004-09-13 04:09 reporter ~0007536	Take a look at 0004469