Modify ↓
Opened 18 years ago
Closed 17 years ago
#2306 closed enhancement (duplicate)
Patch for Smarter Checkboxes
| Reported by: | Owned by: | Jonas Borgström | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | 0.9 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Currently, checkbox fields display themselves elsewhere (ticket summaries, ticket changelogs) as either 1 or 0. The attached patch modifies this behavior, to instead display Yes or No.
Attachments (1)
Change History (6)
by , 18 years ago
| Attachment: | smarter_checkboxes.diff added |
|---|
comment:2 by , 18 years ago
Should we make this configurable, e.g.
- checkbox: A boolean value check box.
- label: Descriptive label.
- value: Default value (yes or no, defaults to no).
- order: Sort order placement.
- yes: Value to use when the checkbox is checked (defaults to Yes)
- no: Value to use when the checkbox is not checked (defaults to No)
comment:3 by , 18 years ago
That wouldn't be a bad idea. I'm setting up a trac testbed to play with this further. Also, there may be problems with the diff I posted, so be careful.
comment:5 by , 17 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Right, I think it's the same issue.
Note:
See TracTickets
for help on using tickets.
aforementioned patch