[allura:tickets] Re: #4429 ticket bulk-edit forcibly always sets all custom boolean fields to True [26300]

[Dave Brondsema <br...@users.sf.net>]

I haven't reproduced this myself, so can't describe the steps.

But I do agree with using radio buttons or drop-down with 3 options, as you suggest.


---

** [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:** Tue Oct 15, 2013 11:17 AM 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.