I can reproduce the first part (not possible to set fields to False, using bulk edit), but can not reproduce the second part. Can you describe steps to reproduce that? It seems to me that now unchecked checkbox means "don't change field value", and checked means "set it to True".
If we change uncheked checkbox meaning to "set to False" we would have problems with keeping field's old value. For example, when you edit some other field and leave checkbox untouched, you set all boolean fields in affected tickets to False. I think, we should consider UI changes for this. For every boolean field show radio-group with three options: Don't change (default), True, False. Any thoughts on this? --- ** [tickets:#4429] ticket bulk-edit forcibly always sets all custom boolean fields to True [26300]** **Status:** open **Labels:** support p3 42cc **Created:** Thu Jun 21, 2012 02:20 PM UTC by Chris Tsai **Last Updated:** Mon Oct 14, 2013 02:03 PM UTC **Owner:** nobody https://sourceforge.net/apps/trac/sourceforge/ticket/26300 >This is on a project using the Beta Allura platform. >I was trying to use bulk-edit to set some custom boolean fields to 'False'. I >left the corresponding boxes unchecked and hit the 'Save' button. The fields >got set to 'True' instead. This seems reliably reproducible. >In fact, it appears that there's no option to leave boolean fields unchanged >during a bulk edit. As far as I can tell, any bulk-edited tickets get all of >their custom boolean fields set to True. Confirmed exactly as described. --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
