Opened 13 years ago
Last modified 3 years ago
#10040 new enhancement
Support for integer/float custom fields — at Initial Version
| Reported by: | pipern | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-dev-1.7.x |
| Component: | ticket system | Version: | |
| Severity: | normal | Keywords: | patch |
| Cc: | osimons, leho@…, Ryan J Ollos | Branch: | |
| Release Notes: | |||
| API Changes: |
Adds a 'datatype' key to the TicketSystem.fields list, which can contain string:
|
||
| Internal Changes: | |||
Description
See http://article.gmane.org/gmane.comp.version-control.subversion.trac.devel/6561 for some discussion.
We'd like to be able to mark some custom fields as "contains integer" or "contains floating number". This would then let us sort numerically, validate user input, add an aggregation/summing feature, and so on.
We're not thinking of changing the storage type, nor, currently, the Python type that exists in the ticket.fields list. Instead, we just validate the user input and then later we can also attempt to convert the field value to the numeric type if we want to do sorting or summing.
This can fix #3080, but walks in the wrong way for FieldRefactoring.
