0004649: Why available statuses are sorted on "bug view" page in "change status to" dropdown? - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0004649	mantisbt	customization	public	2004-10-01 04:23	2004-11-06 06:27

Reporter	astax	Assigned To	thraxisp
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	fixed
Product Version	git trunk
Fixed in Version	0.19.1

Summary	0004649: Why available statuses are sorted on "bug view" page in "change status to" dropdown?
Description	In 19.0 these values were not sorted and this is very convenient as you could affect which one appear pre-selected, just bu changing order of statuses when defining a workflow in config file. For example, I have the following in config file: $g_status_enum_workflow[RESOLVED] = '90:closed,20:feedback,80:resolved'; As in most cases issue should be closed after being resolved, I've put "closed" status first, so it appears as default action that can be done in one click. (Moreover there is a separate "reopen" button, so I even will never need to select "feedback" and click on "change status to")
Tags	No tags attached.

thraxisp 2004-10-01 11:13 reporter ~0007862	Will remove sorting from statuses. Note that the items may not appear in order, but will be in the order listed in the workflow.

thraxisp 2004-10-01 11:56 reporter ~0007865	Sorting removed in CVS Note that feedback may be a valid status outside the context of reopen. We use it here to punt a question back to the originator of the issue (i.e., "Request Feedback").