Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1B09010DF0 for ; Tue, 15 Oct 2013 13:49:26 +0000 (UTC) Received: (qmail 11764 invoked by uid 500); 15 Oct 2013 13:49:25 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 11745 invoked by uid 500); 15 Oct 2013 13:49:25 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 11737 invoked by uid 99); 15 Oct 2013 13:49:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Oct 2013 13:49:25 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Oct 2013 13:49:21 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:In-Reply-To:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=/0TC1DBv7+kVSv46A7I17ULv58RtFZ0DjffzF/VBECI=; b=n2zwJQZsIZQRNq0DwSGTajijrEMcJ5UMI92MqEH5h9dfLpnVuDQC24+FTB7gq7YBH55QSPuyztKECsbCpFzmMimu0JdQYPgDNyb60fBhop694YhPkIFhBCjn5Y7l+wx1vnk8lbNs63H9AUKYfa67IokTWxJee5Qe0uWdkmmRqB4=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-2.v29.ch3.sourceforge.com) by sfs-alluradaemon-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VW4zc-0005W9-85 for allura-dev@incubator.apache.org; Tue, 15 Oct 2013 13:49:00 +0000 Content-Type: multipart/related; boundary="===============9109064627803676173==" MIME-Version: 1.0 To: "[allura:tickets] " <4429@tickets.allura.p.re.sf.net> From: "Dave Brondsema" Reply-To: "[allura:tickets] " <4429@tickets.allura.p.re.sf.net> Subject: [allura:tickets] Re: #4429 ticket bulk-edit forcibly always sets all custom boolean fields to True [26300] Message-ID:

In-Reply-To: <5bb77025dc53238fd8754e9b0a22ace6f8497226.tickets@allura.p.sourceforge.net> Date: Tue, 15 Oct 2013 13:49:00 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============9109064627803676173== Content-Type: multipart/alternative; boundary="===============3835418883533885758==" MIME-Version: 1.0 --===============3835418883533885758== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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. --===============3835418883533885758== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

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.

--===============3835418883533885758==-- --===============9109064627803676173==--