when user has no ability to change status, we seem to pick the first status in alphabetical order and just show that. i suggest we use the lowest CaseStateID (until a weight mechanism is in place) and that we don't show this field on the case form when it isn't editable. can only confuse the user. similarly, if there is only one project then remove that field from the case form.

Comments

morbus iff’s picture

morbus iff
they/them
commented
Title: default status on case form and remove under certain circumstances » Add weight to case state options
Assigned: Unassigned » morbus iff

moshe: both of these were actually implemented as part of my goldplating to casetracker:

* admins have the ability to set default status, priority, and type.
* project dropdown is not shown if pid is passed through the URL.

I do plan to implement weight on state options, but that will be after my goldplating is complete.

morbus iff’s picture

morbus iff
they/them
commented

Actually, I'm sorry: "if only one project, remove dropdown" is NOT implemented.

morbus iff’s picture

morbus iff
they/them
commented

moshe: tonight's commit to HEAD will contain "if one project, no dropdown".

zero2one’s picture

zero2one commented
Assigned: morbus iff » zero2one
Status: Active » Fixed
zero2one’s picture

zero2one commented
Status: Fixed » Closed (fixed)