Re: issues shown as "no priority set"

Vladimir G. Ivanovic writes: > I think it's unintuitive and surprising for the issue editor view to > show a value that is, in fact, not present. OK, I'll see if I can find a way to set the value without this unintuitive behavior.

> (Is this the default Roundup behavior?) No, as I said, this is an easy hack that ensures priority is set without forcing the user to do it. Priority is the property primarily of the assigned developer, so users should normally not be setting it. Severity is the field that the user can set.

> Why not label unselected but required fields in red? We do. Since users in general should not be setting priority, it can not be a required field. > If the user tries to save the issue, then an error message can pop > up asking the user to fill in all fields marked with a red label. As a user, I hate programs that behave that way. I want to keep fields that require user action to a bare minimum. Currently that minimum is title and module (severity, type, and platform all have plausible defaults).