|
I understand that I can select a default value, but I explicitly don't want
to do that. I want the developer to fill that value in. _____ From: Anton Mazkovoi (JIRA) jira@atlassian.com Issue (View <http://jira.atlassian.com/browse/JRA-7320 <http://jira.atlassian.com/images/bluepixel.gif Key: JRA-7320 <http://jira.atlassian.com/browse/JRA-7320 Type: <http://jira.atlassian.com/browse/JRA-7320 Status: Open <http://jira.atlassian.com/images/icons/status_open.gif Priority: Major <http://jira.atlassian.com/images/icons/priority_major.gif Assignee: Unassigned Reporter: Anders Operations <http://jira.atlassian.com/images/bluepixel.gif <http://jira.atlassian.com/images/icons/bullet_creme.gif <http://jira.atlassian.com/images/icons/bullet_creme.gif <http://jira.atlassian.com/images/icons/bullet_creme.gif Allow me to <http://jira.atlassian.com/browse/JRA-7320 The following comment has been added to this issue: [ Permlink Author: Anton You can actually pick a defult value for a custom field such that 'yes' or Thank you for the suggestion. Anton Project: JIRA <http://jira.atlassian.com/browse/JRA Components: Custom Fields Affects Versions: 3.2.2 Enterprise Description I have a custom field, called "Doc Impact" with two values: "Yes" and "No" Before a user has chosen one of the two values, it display "None" as the I would like to be able to change the "no value selected" for custom fields. <http://jira.atlassian.com/images/border/spacer.gif This message was automatically generated by Atlassian JIRA Anders,
This can't be done in JIRA itself. Though, you can edit the language file: with common.words.none = Though this will have the effect of having a blank everywhere "None" usually appeared. Another opttion is to edit the file: <option value="-1">$i18n.getText("common.words.none")</option> with <option value="-1"></option> Though this will cause all select lists to have a blank instead of the word "None". The only solution that will not effect other things is to create your own Custom Field Type that is a complete duplicate of the Select Custom Field except it uses another view template with the changes I mentioned above. Hope this helps. Cheers, This work around is terrible. We should have the option for custom fields to not have the "none" put into the list by default. Please fix this as soon as possible.
Aaron,
With limited resources we must select which features/improvements and bugs we are going to implement  .
As this improvement does not have many votes and does have a workaround (albeit an ugly one) this did not go into 3.4. Cheers, Hi Nick,
We need a custom field called "Impact on User Experience". We want the values to be:
And we need this to be a required field. But when we did this, we got the following listbox: Impact on User Experience: - None - No visible change - Change to existing feature - New feature Everyone was confused by the "None" option, because within the context of the words of the prompt, the word "None" had an implied meaning that we don't intend. How do you suggest we work around this? I think the workaround is given above, to edit the file edit-select.vm
But doesn't that mean we have to re-make that change every time we apply a patch? Is there a way to keep some of the config file customizations permanent?
Yes - any customizations you make would have to be re-done every time you upgrade. That's why this is still an open issue.
|
||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
Allow me to change the "None" in custom fields
You can actually pick a defult value for a custom field such that 'yes' or 'no' is selected by default. This way, unless the user specifically chosses 'none' the field will have a value.
Thank you for the suggestion.
Anton