Ticket #9405 (closed enhancement: fixed)
Opened 20 months ago
Last modified 17 months ago
[patch] add reminder to keep priority order for proper ticket coloring
| Reported by: | hasienda <hoff.st@…> | Owned by: | hasienda <hoff.st@…> |
|---|---|---|---|
| Priority: | low | Milestone: | 0.12.1 |
| Component: | admin/web | Version: | |
| Severity: | normal | Keywords: | admin web_ui bitesized |
| Cc: | |||
| Release Notes: | |||
| API 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
Change History
comment:1 Changed 20 months ago by hasienda <hoff.st@…>
comment:2 Changed 20 months ago by rblank
- Keywords bitesized added
- Milestone set to unscheduled
Maybe use "Note:" instead of "Reminder:" for consistency.
Changed 20 months ago by hasienda <hoff.st@…>
- Attachment 9405_add_color-on-priority_note.patch added
conditional hint on priority order affecting ticket coloring
comment:3 Changed 20 months ago by hasienda <hoff.st@…>
- Summary changed from add reminder to keep priority order for proper ticket coloring to [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 Changed 20 months ago by rblank
- Milestone changed from unscheduled to 0.12.1
- Owner set to rblank
comment:5 Changed 20 months ago by cboos
- Owner changed from rblank to hasienda <hoff.st@…>
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.
comment:6 follow-up: ↓ 7 Changed 19 months ago by 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 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 in reply to: ↑ 6 Changed 19 months ago by hasienda <hoff.st@…>
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 Changed 17 months ago by rblank
- Resolution set to fixed
- Status changed from new to 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.