Opened 16 years ago
Closed 9 years ago
#8812 closed enhancement (duplicate)
Text field with post-label and right alignment
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | none |
| Severity: | normal | Keywords: | fieldrefactoring |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
The TH:TimingAndEstimation plugin uses text fields as number fields.
Either allow for a proper number inputfield or extend the text field to allow for:
- a right alignment of the value
- an post-label that can be used as an unit
Attachments (2)
Change History (8)
by , 16 years ago
| Attachment: | TracCustomNumberField.jpg added |
|---|
comment:1 by , 16 years ago
| Component: | general → ticket system |
|---|---|
| Description: | modified (diff) |
| Keywords: | fieldrefactoring added |
| Milestone: | → next-major-0.1X |
by , 16 years ago
| Attachment: | TicketSystem_CustomField_Align_PostLabel_DisplaySize_ChangeSet.patch added |
|---|
comment:2 by , 16 years ago
With the attached change-set custom fields have the following attributes added:
- align: optional alignment (left(default), right)
- post_label: optional, a label after the field. This can be used as a unit notation.
- display_size: optional, the size or number of characters the field displays.
comment:3 by , 16 years ago
Oh well, next time I should be more precise about what kind of patch would be welcomed ;-)
I was more expecting something along the line of the first solution allow for a proper number inputfield rather than the second, which looks a bit too hackish… (not the patch which is fine, but the approach).
Sorry for the inconvenience, in the meantime I'm sure the patch could be useful for other people having the same immediate needs.
comment:4 by , 15 years ago
| Milestone: | next-major-0.1X → unscheduled |
|---|
comment:6 by , 9 years ago
| Milestone: | unscheduled |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
Closing as duplicate of #10040.



Patch welcomed ;-)