[MCHANGES-369] announcement-generate not include fixVersion filter in JQL

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.11, 2.12
• Fix Version/s: 3.0.0, 3.0.0-M1
• Component/s: announcement
• Assignee: Slawomir Jaranowski
• Reporter: Rubén Sans Mudoy
• Created: 30/Mar/16 10:28
• Updated: 07/Dec/24 12:07
• Resolved: 04/Dec/24 14:19

Description

I'm trying this plugin and when I use mvn changes:jira-report generates that JQL:

Payload:

{"jql":"project = API AND fixVersion = m3 AND status in (6, 5) AND resolution in (1, 7) ORDER BY priority DESC, created DESC","maxResults":500,"fields":["*all"]}

but when I use mvn changes:announcement-generate generates a JQL without the fixVersion filter.

Payload:

{"jql":"project = API AND status in (6, 5) AND resolution in (1, 7)","maxResults":500,"fields":["*all"]}

In both cases the plugin configuration is the same. I need to generate release notes in plain text.

This is the plugin configuration:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-changes-plugin</artifactId>
<version>2.11</version>
<executions>
<execution>
<id>include-announcement-file</id>
<phase>generate-resources</phase>
<goals>
<goal>announcement-generate</goal>
</goals>
<configuration>
<announcementFile>CHANGES.txt</announcementFile>
<announcementDirectory>${project.build.outputDirectory}/META-INF</announcementDirectory>
</configuration>
</execution>
</executions>
<configuration>
<announcementFile>CHANGES.txt</announcementFile>
<announcementDirectory>${project.build.outputDirectory}/META-INF</announcementDirectory>
<developmentTeam>The Team</developmentTeam>
<maxEntries>500</maxEntries>
<issueManagementSystems>
<issueManagementSystem>JIRA</issueManagementSystem>
</issueManagementSystems>

<useJql>true</useJql>
<onlyCurrentVersion>true</onlyCurrentVersion>
<resolutionIds>Fixed,Done</resolutionIds>
<statusIds>Closed,Resolved</statusIds>
<columnNames>Type,Key,Summary,Priority,Status,Resolution,Fix Version,Assignee</columnNames>
<webUser>*****</webUser>
<webPassword>*****</webPassword>
</configuration>
</plugin>

Issue Links

• links to: GitHub Pull Request #91