[ https://issues.jboss.org/browse/TOOLSDOC-622?page=com.atlassian.jira.plug... ] Martin Malina commented on TOOLSDOC-622: ---------------------------------------- Based on our discussion on IRC, I suggest we use this for Known Issues: {code} (project in (JBDS) AND affectedVersion >= "7.0.0.GA" AND affectedVersion <= "8.1.0.GA" AND (resolution in (Unresolved) OR resolution in (Done) AND fixVersion > "8.1.0.GA") OR project in (JBIDE) AND affectedVersion >= "4.1.0.Final" AND affectedVersion <= "4.2.3.Final" AND (resolution in (Unresolved) OR resolution in (Done) AND fixVersion > "4.2.3.Final")) AND type in (Bug) {code} As described in the JIRA, the problem with the above query is that it also returns JIRAs that have multiple fixVersion, such as JBIDE-19377 - this JIRA is fixed in both 4.2.3.x and 4.3.x, so it's already fixed in JBDS 8.0.0.GA. But even if we filtered these out, there would still be a number of JIRAs that were cloned for the second version - one jira for 4.2.x and one for 4.3. So this query would still show a jira that was fixed in e.g. 4.3.0.Alpha1 as a known issue in 4.2.3.Final even though there might be a second (cloned) jira with the same fix for 4.2.3.x. At this point I'm not sure what we can do other then going one by one in the list of jiras and manually selecting the ones that are relevant and then include them in the release notes directly. In any case, we concluded that it's too late to fix this for this release, so this will have to be looked at for next time. -- This message was sent by Atlassian JIRA (v6.3.11#6341)