Modify ↓
Opened 8 years ago
Closed 7 years ago
#12590 closed enhancement (fixed)
Max size attribute for ticket custom fields
| Reported by: | Ryan J Ollos | Owned by: | Ryan J Ollos |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.3.2 |
| Component: | ticket system | Version: | |
| Severity: | normal | Keywords: | custom fields |
| Cc: | Branch: | ||
| Release Notes: |
Added |
||
| API Changes: | |||
| Internal Changes: | |||
Description
There exists a max size option for several fields: comment, description, summary (TracIni#ticket-section).
We could add a max_size attribute for ticket custom fields, applicable to types text and textarea. That would leave Keywords and Cc as default fields which don't have a max size, so we may also want a way to specify a max size for those fields as well.
Attachments (0)
Change History (2)
comment:1 by , 7 years ago
| Milestone: | next-major-releases → 1.3.2 |
|---|---|
| Owner: | set to |
| Release Notes: | modified (diff) |
| Status: | new → assigned |
comment:2 by , 7 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Committed to trunk in [15493:15494].
Note:
See TracTickets
for help on using tickets.
Proposed changes in log:rjollos.git:t12590_ticket_custom_max_size.
I continued the existing pattern of validating every field, rather than just validating the modified fields. This could lead to odd behavior for users if an admin modifies
max_size(ormax_summary_size,max_description_size, …) and a field of an existing ticket exceeds the new max size. The validation warning will be seen when modifying the ticket even if the field is not changed. I'm unsure if we should modify the behavior, but let me know if you have any thoughts on it.DONE Update 1.3.1/TracTicketsCustomFields.