Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 36356 invoked from network); 2 Feb 2011 19:53:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Feb 2011 19:53:09 -0000 Received: (qmail 53297 invoked by uid 500); 2 Feb 2011 19:53:09 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 53261 invoked by uid 500); 2 Feb 2011 19:53:08 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 53254 invoked by uid 99); 2 Feb 2011 19:53:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Feb 2011 19:53:08 +0000 X-ASF-Spam-Status: No, hits=3.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of akssps011@gmail.com designates 74.125.82.172 as permitted sender) Received: from [74.125.82.172] (HELO mail-wy0-f172.google.com) (74.125.82.172) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Feb 2011 19:53:00 +0000 Received: by wyf23 with SMTP id 23so355966wyf.31 for ; Wed, 02 Feb 2011 11:52:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:from:date:message-id:subject:to :content-type; bh=hiFi/9AFAaKtz2DtWn4K5oawrRN+a/bkG62mZ8w/fF8=; b=jUqJfwIPO6i1USYX+WIVW/s8sNARG4dW+qbGJHIwx06p9UnpOrUQjU0QT68ByuTVEU 6IHGuBu9KwB4rIiQOhreOW2M70vyP8krwUn733j2maE609gX/7R+wKAlzWDOCWtbw9BA qZUCVXH5R2JjesREte2+4xpRw7S+7zXlO56uM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=gsduZDuQCFnny/VxhaQkhGC5LNQLq6rWFJfg00wa0hINoKGqk53k7i356wriqyKxnQ nTECgKcoha6ZvwF47oZILt3PUaOTK0/CAxfwpG+djr/7U53KurqbaFawx24ZwBOoDTAH PIdPOiZuN3s1ycaIn2EVSi270tBHc+4ENhB8A= Received: by 10.216.184.139 with SMTP id s11mr2292273wem.13.1296676360432; Wed, 02 Feb 2011 11:52:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.90.10 with HTTP; Wed, 2 Feb 2011 11:52:20 -0800 (PST) From: siddharth srivastava Date: Thu, 3 Feb 2011 01:22:20 +0530 Message-ID: Subject: Jira related issues To: derby-dev@db.apache.org Content-Type: multipart/alternative; boundary=0016367b5e1eda2eab049b51fde0 X-Virus-Checked: Checked by ClamAV on apache.org --0016367b5e1eda2eab049b51fde0 Content-Type: text/plain; charset=ISO-8859-1 Hi I was trying out the new jira. Though I am still unable to attach files to the issue, I was wondering if these kind of issues with jira need to be reported to some apache specific jira maintainer(if any) or they need to be reported to the general jira module ? I am facing problems uploading files, watching issues or I must say every other option in More Actions menu. I have tried things with Firefox, chrome and Internet Explorer (with Compatibility view also) Thanks -- Regards Siddharth Srivastava --0016367b5e1eda2eab049b51fde0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi

I was trying out the new jira. Though I am still unab= le to attach files to the issue, I was wondering if these kind of issues wi= th jira need to be reported to some apache specific jira maintainer(if any)= or they need to be reported to the general jira module ?

I am facing problems uploading files, watching issues o= r I must say every other option in More Actions menu.

<= div>I have tried things with Firefox, chrome and Internet Explorer (with Co= mpatibility view also)

Thanks

--
Regards
Si= ddharth Srivastava


--0016367b5e1eda2eab049b51fde0--