Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Tue, 13 Sep 2011 12:43:08 +0000 (UTC)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <771067294.21810.1315917788985.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <187580346.6046.1299012036924.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (DERBY-5080) Utilize JQL to fetch JIRA issue list
 for release notes generation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristian Waagan closed DERBY-5080.
----------------------------------


Closing issue.

> Utilize JQL to fetch JIRA issue list for release notes generation
> -----------------------------------------------------------------
>
>                 Key: DERBY-5080
>                 URL: https://issues.apache.org/jira/browse/DERBY-5080
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.8.1.2
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.9.0.0
>
>         Attachments: derby-5080-2a-utilize_jql.diff, derby-5080-2a-utilize_jql.stat, derby-5080-3a-report_disqualifications_knob.diff
>
>
> DERBY-4857 made it possible to use the JIRA SOAP API to fetch a list of issues fixed in a release. However, the release manager have to manually create a JIRA filter and feed the filter id to the tool.
> Now that the Apache JIRA instance has been updated to 4.x, we can use the JIRA Query Language (JQL) to avoid that manual step.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira