Ticket #899 (closed enhancement: duplicate)
Opened 7 years ago
Last modified 17 months ago
[PATCH] Allow hints for custom fields in tickets
| Reported by: | pkou <pkou at ua.fm> | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | devel |
| Severity: | normal | Keywords: | patch |
| Cc: | ryano@… | ||
| Release Notes: | |||
| API Changes: | |||
Description
Custom fields often require additional explanations for developers. It is possible to resolve this problem by adding popups that will appear when user points mouse over a custom field.
Attached patch provides a solution for this problem:
- In trac.ini, new property field.hint can be used;
- In generated HTML, hints are implemented using HTML title attribute.
Attachments
Change History
Changed 7 years ago by pkou <pkou at ua.fm>
- Attachment patch-customtitle-r1036.diff added
comment:1 Changed 7 years ago by pkou <pkou at ua.fm>
Note that TracTicketsCustom needs to be edited when this ticket is closed.
comment:2 Changed 5 years ago by sid
comment:4 Changed 5 years ago by cboos
- Milestone changed from 0.11 to 0.12
0.12 I meant (i.e. not necessarily for 0.11, but why not if done part of the workflow changes...)
Changed 3 years ago by rblank
- Attachment 899-custom-field-hints-r7495.patch added
Patch against trunk adding optional hints to custom ticket fields
comment:5 Changed 3 years ago by rblank
- Keywords patch added
- Milestone changed from 0.13 to 0.12
- Owner changed from jonas to rblank
The patch above adds the .hint option to custom ticket fields, and if present, adds a title attribute to the control corresponding to the field. Radio buttons are grouped in a <span> to set the title for all at once.
comment:6 Changed 3 years ago by rblank
I forgot to update the unit tests. Here's the complete patch.
Changed 3 years ago by rblank
- Attachment 899-custom-field-hints-r7495.2.patch added
Complete patch including unit tests
comment:7 Changed 3 years ago by osimons
I like the idea of hints - they are useful. However, I'm very unsure about adding features for custom fields until we have an idea about what the future holds for fields in general (0.13+ seems to have field refactoring on the agenda):
- We would then have hints for custom fields, but not for regular fields.
- 0.12 translates labels for regular fields, but not custom fields.
- Hints (as all help) should be translatable in some way...
comment:8 Changed 3 years ago by rblank
- Milestone changed from 0.12 to 0.13
Re-scheduling for 0.13, as this could be in the way of i18n.
comment:9 Changed 20 months ago by rblank
- Milestone changed from next-major-0.1X to unscheduled
- Owner rblank deleted
comment:10 Changed 18 months ago by Adrian Fritz <adrian@…>
#925 may be related, and maybe a solution using javascript at http://trac-hacks.org/wiki/BlackMagicTicketTweaksPlugin
comment:11 Changed 18 months ago by Ryan J Ollos <ryano@…>
- Cc ryano@… added
comment:12 follow-up: ↓ 13 Changed 17 months ago by Sebastian Krysmanski <sebastian@…>
I've created a more general version of this patch (usable for all ticket fields, not just for custom fields). It's tracked here: #9648
comment:13 in reply to: ↑ 12 Changed 17 months ago by rblank
- Milestone unscheduled deleted
- Resolution set to duplicate
- Status changed from new to closed
Replying to Sebastian Krysmanski <sebastian@…>:
I've created a more general version of this patch (usable for all ticket fields, not just for custom fields). It's tracked here: #9648
This is indeed a much improved version of the patch here. Closing as a duplicate of #9648.
Patch for the changes