issues shown as "no priority set"

Vladimir G. Ivanovic writes: What it says: there is no priority set. Good question, though. Actually, I don't think that #374 does have a priority set. What you are seeing is the "issue editor" view. In the nature of an editor interface, the values you see are not the current values, but the values that the attributes will get if you press "submit changes". Of course, for most issues those "default edited values" will be initialized to the current values. When priority is currently "--unselected--", the default edited value is forced to "normal" to ensure that priority would automatically get a sane value as soon as the issue is edited, even though those fields are marked as "not interesting to ordinary users". This could be implemented to show the current value in the "issue editor" view, but automatically force it to "normal" if set to "--unselected--". It would take a fair amount of effort, though, because I haven't learned to hack that part of Roundup yet. The implementation I used just required a 40-byte Python expression. :-) Now that it's been explained, do you think it would help other users if I changed it? _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta