Opened 14 years ago
Closed 14 years ago
#9405 closed enhancement (fixed)
[patch] add reminder to keep priority order for proper ticket coloring
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | low | Milestone: | 0.12.1 |
| Component: | admin/web | Version: | |
| Severity: | normal | Keywords: | admin web_ui bitesized |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Add a conditional note to trac/admin/templates/admin_enums.html, that will display a hint/warning like follows, if enum = 'priority':
"Reminder: Keep high-to-low order regardless of label names here, because it affects ticket coloring in queries and reports."
Attachments (1)
Change History (9)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
| Keywords: | bitesized added |
|---|---|
| Milestone: | → unscheduled |
Maybe use "Note:" instead of "Reminder:" for consistency.
by , 14 years ago
| Attachment: | 9405_add_color-on-priority_note.patch added |
|---|
conditional hint on priority order affecting ticket coloring
comment:3 by , 14 years ago
| Summary: | add reminder to keep priority order for proper ticket coloring → [patch] add reminder to keep priority order for proper ticket coloring |
|---|
Did so, please find this patch done on top of trunk SVN r9824. This is certainly for 0.12.1, since it creates another msgid.
comment:4 by , 14 years ago
| Milestone: | unscheduled → 0.12.1 |
|---|---|
| Owner: | set to |
comment:5 by , 14 years ago
| Owner: | changed from to |
|---|
Looks good to me. It's more a bit of polishing and documentation enhancement than a real new feature, therefore I'm OK to keep it for 0.12.1.
Will apply.
follow-up: 7 comment:6 by , 14 years ago
Dunno but wouldn't be a hint like for example:
'based on the assigned order of the <priority, severity…>, tickets will be displayed in different colours…'
more like it?
I mean, the user can reorder and redefine existing resolutions, severities etc. to his or her wishes and define a specific display for them.
The rest is purely cosmetic, everbody is free in changing/overriding the css styles…
comment:7 by , 14 years ago
Replying to Carsten Klein <carsten.klein@…>:
Dunno but wouldn't be a hint like for example:
'based on the assigned order of the <priority, severity…>, tickets will be displayed in different colours…'
more like it?
I've just done a patch as per request, not thought too much about a perfect wording. I'll welcome a more straight forward/clearer hint, so your suggestion is ok to me.
I mean, the user can reorder and redefine existing resolutions, severities etc. to his or her wishes and define a specific display for them.
The rest is purely cosmetic, everbody is free in changing/overriding the css styles…
Cosmetic it is, but that's exactly the thing, what a user wanted: as a pure reminder to document the connection between definition here and later display over there. It's just for the casual adjustment or testing in web-UI.
If someone is changing CSS, he/she will be well aware of the implications, I guess - a different case and not the target group.
comment:8 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Slightly different wording applied in [10043].
This came up as a minor issue at #trac this evening and might be easy enough to implement by extending the mentioned template.