Return-Path: Delivered-To: apmail-struts-dev-archive@www.apache.org Received: (qmail 97376 invoked from network); 10 Jan 2007 17:47:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Jan 2007 17:47:44 -0000 Received: (qmail 94499 invoked by uid 500); 10 Jan 2007 17:47:49 -0000 Delivered-To: apmail-struts-dev-archive@struts.apache.org Received: (qmail 94161 invoked by uid 500); 10 Jan 2007 17:47:48 -0000 Mailing-List: contact dev-help@struts.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Struts Developers List" Reply-To: "Struts Developers List" Delivered-To: mailing list dev@struts.apache.org Received: (qmail 94150 invoked by uid 99); 10 Jan 2007 17:47:48 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jan 2007 09:47:48 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of mfncooper@gmail.com designates 66.249.92.175 as permitted sender) Received: from [66.249.92.175] (HELO ug-out-1314.google.com) (66.249.92.175) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jan 2007 09:47:39 -0800 Received: by ug-out-1314.google.com with SMTP id u40so157156ugc for ; Wed, 10 Jan 2007 09:47:08 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=p1wP4RdhCElE7NFreYCOSZucOoHn1xHsWtL/1XXSLN2AWxzuCcwWOVaMpq1kM1zfZNIGyp8KCiVKQ42mlWOu9sT9Z4X6qZJpqql91dWXtBru9A9Xa3zfnMZ1LlV/v/U8YjILzaxC0kjzZqZeEqV3t6JoRgvKoRCjIg+feu6bjFI= Received: by 10.82.152.16 with SMTP id z16mr122487bud.1168451228455; Wed, 10 Jan 2007 09:47:08 -0800 (PST) Received: by 10.82.161.4 with HTTP; Wed, 10 Jan 2007 09:47:08 -0800 (PST) Message-ID: <16d6c6200701100947x4146fac6y2547eb5aa2bd7362@mail.gmail.com> Date: Wed, 10 Jan 2007 09:47:08 -0800 From: "Martin Cooper" Sender: mfncooper@gmail.com To: "Struts Developers List" Subject: Re: Tiles Jira In-Reply-To: <91478db0701100934u4ec61f66gc3406e0287dd5e14@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_8939_31684556.1168451228166" References: <91478db0701100726i550d2adbr82bba08db057dbc9@mail.gmail.com> <45A5105F.4060709@apache.org> <91478db0701100934u4ec61f66gc3406e0287dd5e14@mail.gmail.com> X-Google-Sender-Auth: aae6cf41c937c26b X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_8939_31684556.1168451228166 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 1/10/07, Greg Reddin wrote: > > On 1/10/07, Antonio Petrelli wrote: > > > > Greg Reddin ha scritto: > > > See the INFRA > > > ticket for the Tiles TLP for info about porting existing tickets. > > > > What experimental tool? > > And anyway, is it really necessary? Since they are in the same JIRA > > instance, the tickets could be ported with a bulk change, moving them to > > the new JIRA project. > > > > IIUC a huge missing piece in Jira is the capability to move issues > around. > So, for example, when Shale went TLP we couldn't create a new Jira > instance > for Shale and move tickets to it. I think there's an experimental way to > move an issue from SB-* to TILES-* if we wanted to do that, but I don't > know > anything about it. I'm afraid I don't either. ;-( I was just trying to do _something_ last night to at least get the ball rolling, since nothing seemed to be happening. One thing I noticed when I set up the project is that, when I set one of the schemes to Struts, JIRA seemed to be looking for issues to move and didn't find any. It made me wonder if it would actually move issues as you wanted if we had the appropriate scheme set up correctly. However, this is going to need someone who understands these scheme thingies much better than I do... -- Martin Cooper Greg > > ------=_Part_8939_31684556.1168451228166--