View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004469||mantisbt||feature||public||2004-09-02 12:07||2016-04-06 09:36|
|Summary||0004469: "Reply To Feedback" Button|
This could be a usefull feature.
It should also be possible to assign every user to an issue - so the user knows that he have to act with the issue now.
|Tags||No tags attached.|
|has duplicate||0006592||closed||grangeway||my view and feedback|
|related to||0003378||new||who's feeding back to who?|
|related to||0003730||closed||vboctor||Change status upon feedback|
|related to||0002442||closed||vboctor||better handling of status FEEDBACK (status change after feedback by bugnote)|
|related to||0006061||closed||cproensa||Issues being put back to "Assigned" if assignment changes (to another user) when on different status.|
|related to||0016454||assigned||dregad||Missing something with $g_reassign_on_feedback|
The question is whether we need another status, or whether we can use an existing status like 'new'. Any thoughts?
I think "feedback" is not a normal status in the status workflow because it "jumps out" the normal workflow. "Feedback" should be reachable from every other status.
So, after the reply it should be jump back to the old status before the "feedback".
Humm, that's not a bad idea. We just have to be able to figure out the last status, possibly from the history.
I would appreciate a simple solution (a predefined exit status, new or assigned) to, in contrast to no solution.
I found a patch somewhere. Perhaps someone is interested. If someone is assigned to the bug, than giving feedback popÂ´s back to ASSIGNED, if not to NEW.
Before bug_update_date in bugnote_add in core/bugnote_api.php
Sorry for the layout, but preformatted text is still misbehaving (word wrapping), dispite of 0004762 being closed, sigh...
+1 (I was going to enter this feature request myself, then found this)
I think there should be "Provide Feedback" button in Feedback state, treated same way as "Reopen Issue" button -- with config variables for who it's available to and what state the issue should transition to (possibly with a special value of "previous").
Any chance of adding this simple but very effective option into the 1.2.0 version ?
I have improved my patch from 3.5 years ago... :-)
The different workflow requires some other patches, but I find this very useful. If there is interest in the patch, I can try to extract one.
The changes for the behaviour descripted in the last bugnote:
if ( ( bug_get_field($p_bug_id, 'status') == FEEDBACK ) &&
somewhere, e.g. in history_api.php:
I wrote a patch that implement the following workflow:
I have it against 1.1.8, but could port it to 1.2.X if there is interest.
Changing the "assigned to" is a tradeoff:
See also 0008140, reply to note, which works very good together with this.
I've just checked in 0003730 which does the following:
The fix doesn't however pop the status from the history.
History popping is easy, see 0004469:0022183.
Work-in-progress fix for this can be found at https://github.com/dregad/mantisbt/tree/feedback-prev-stat
|2004-09-02 12:07||bpfennig||New Issue|
|2004-09-02 15:03||jlatour||Note Added: 0007409|
|2004-09-02 15:03||jlatour||Status||new => feedback|
|2004-09-03 04:07||bpfennig||Note Added: 0007421|
|2004-09-03 06:23||jlatour||Note Added: 0007422|
|2005-04-05 10:47||polzin||Note Added: 0009711|
|2005-05-17 11:22||ryandesign||Relationship added||related to 0003378|
|2005-05-17 15:22||polzin||Note Added: 0010160|
|2005-05-17 15:26||polzin||Note Edited: 0010160|
|2006-02-27 16:27||ryandesign||Relationship added||related to 0006592|
|2006-03-02 06:41||ryandesign||Relationship added||related to 0003730|
|2006-03-02 06:41||ryandesign||Relationship added||related to 0002442|
|2008-07-28 14:20||grangeway||Status||feedback => acknowledged|
|2008-07-28 15:22||grangeway||Relationship replaced||has duplicate 0006592|
|2008-11-13 15:02||olegos||Note Added: 0019877|
|2009-01-23 04:52||cas||Note Added: 0020692|
|2009-01-23 05:14||polzin||Note Added: 0020693|
|2009-06-17 10:55||polzin||Note Added: 0022183|
|2009-06-17 10:57||polzin||Note Edited: 0022183||View Revisions|
|2009-07-21 07:32||polzin||Note Added: 0022542|
|2009-10-14 01:20||vboctor||Note Added: 0023172|
|2009-10-14 03:29||polzin||Note Added: 0023175|
|2014-10-10 05:40||dregad||Relationship added||related to 0006061|
|2014-10-10 05:41||dregad||Note Added: 0041522|
|2016-04-06 09:36||dregad||Relationship added||related to 0016454|