FogBugz:Custom Fields - Hiranyaloka/Documentation GitHub Wiki

Feature requests for the custom fields.

• New “Types” :
  • Numeric Value
  • Rich text editor mode
  • Slider to specify the range of values
  • Color Picker
• Validate user input form values by the data types
• FogBugz 82388: Add ‘multiplicable’ attribute to custom fields
• FogBugz 103990: FB: Expand storage area of URL custom fields
• Case 104214 Requiring drop-down custom fields is meaningless
• Case 104215 It’s possible to set a drop-down custom field default value unintentionally
• Case 104216 Impossible to remove default value of radio custom fields

• Case 104072 Custom Fields’ display options and sorting by the blog administrator
• FogBugz 100771: Support custom fields reordering again
• FogBugz 102949: Sorting by arbitrary custom fields
• FogBugz 100632: Sorting by custom field doesn’t work with “limit” attribute
• FogBugz 102648: FB: Ability to specify sort order of comment customfield form on the published-blog side

• Case 101734 Search & Replace: Custom Fields

• FogBugz 102707: Add ability to add associate assets in custom fields with the list of entry assets
• FogBugz 102991: The custom field to add associate an “Asset” to another object should allow selection of ANY asset type.
• FogBugz 103832: Import entries with asset
• FogBugz 82129: Image Custom Fields don’t provide option to add title, description, & tags.
• FogBugz 65381: Custom field image should honor insert asset settings
• Case 104144 Asset-type custom fields should provide a “view/edit asset” link

• Case 103719 All the template custom fields are displayed

• Case 104072 Custom Fields’ display options and sorting by the blog administrator
• FogBugz 100380: Auto-filled template tag name should be lower case?
• Custom Field MT-tag helper widget

• Case 64553 Categories/Folders can be created even if required custom fields of them are not set

• FogBugz 100504: Permission denied error when blog admin click links of system-wide custom fields on blog-wide CF listing screen
• FogBugz 100741: Required custom field isn’t required on mt-comments.cgi
• FogBugz 100446: Date and Time CF displays “1970年1月 1日 00:00” on preview
• Case 101850 Custom field defaults are FALLBACKS and not actually stored
• Case 97058 Sorting on a Date custom field in a category archive is broken
• Case 103647 Custom fields’ data are always cloned even if custom fields are added to exclusions on Clone Blog dialog

• FogBugz 80097: Should Systemwide Custom Fields be displayed along with Blog-Specific Custom Fields?
• FogBugz 100524: FR: can specify custom fields in each entry
• FogBugz 103390: Remove system-wide custom fields for entry from website-wide custom field listing screen
• FogBugz 79774: Include custom fields when cloning a blog
• Remove requirement that custom fields must have unique basenames

• Case 104062 Scalable Custom Fields
• FogBugz 91392: Deleting Motion blog makes Orphaned CFs.