[#526] Tracker custom fields not generally usable due to addition of “None” choice



Detailed description

It’s currently impossible to make a drop-down, checkbox or radiobuttons without FF adding the “None” choice. This implies it’s impossible to make a simple yes/no extra field, too.

This makes the extra field functionality unusable for many tasks, even though there are indeed some for which this is needed.

Forwarded from: https://evolvis.org/tracker/t_follow.php/3502

General Information
Submitted by:
Thorsten Glaser
Date Submitted: 2013-01-24 10:27
Last Modified by: Nobody
Last Modified: 2017-11-02 20:00
Date Closed: 2014-01-23 09:18
Permalink: https://fusionforge.org/tracker/a_follow.php/526
Votes: 0/1 (0%)
Internal Fields
Data Type: Bugs
Assigned to: Franck Villaume (nerville)
State: Closed
Priority: 3
Extra Fields
Target Release:
Found in Version:
Follow-up tabs
Message  ↓
Date: 2014-01-23 09:18
Sender: Franck Villaume

fix in commits : bc9c1836e88531f13c9cc4f31828a59fe53c96f6 22189a0d624247adf4865bf8ebf87686b9d94e7c 0063459effc5c0836ff2276f6146a2c4b15261de 5534acd5384e1f723eae1f44fe0d6455bcec8654 756c26099d1b7fa9dd10f0fdd567469ef6695806

Date: 2014-01-09 12:37
Sender: Franck Villaume

To fix this issue, we need to extend the way we deal with the '100' value. Currently, the '100' value is used by default. An easy way would be to set a parameter activating or not the '100' value in the custom fields. A more friendly way would be to implement a configuration per custom field. This second option is more complex to implement.

No attached documents

No related commits.

Field Old Value Date By
Target ReleaseNone2014-01-23 09:18
Franck Villaume
SeverityNone2014-01-23 09:18
Franck Villaume
ResolutionNone2014-01-23 09:18
Franck Villaume
status_idOpen2014-01-23 09:18
Franck Villaume
close_dateNone2014-01-23 09:18
Franck Villaume
assigned_tonone2014-01-23 09:18
Franck Villaume

No relations found.