Include only specific issues in maven-changes-plugin JIRA report

I am currently using the maven-changes-plugin to generate a JIRA report for a given fixVersionId file like this:

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-changes-plugin</artifactId>
    <version>2.9</version>
    <configuration>
        <fixVersionIds>16355</fixVersionIds>
    </configuration>
</plugin>

      

However, what if, instead of specific fixVersionIds, I want to be able to include specific problems? Is there a way to do this? I don't see the possibility in the usage documentation .

I can use JQL on an actual Jira site " issueKey=ISSUE-10 OR issueKey=ISSUE=11

", but putting it in a filter attribute doesn't work (I have useJql for true). Even using a simple type " resolution=1

" does not work (the example on the documentation site does not work either). I see in the logs that both of these attributes are set correctly, but when it makes an API call in JIRA it just uses the default settings and doesn't use the filter attribute at all:

Payload: {"jql": "project = RESONANCE AND status in (6) AND resolution in (1) ORDER BY priority DESC generated by DESC", "maxResults": 100, "fields": ["* all"]}

What can I lose?

+3


source to share


1 answer


Unfortunately this seems to be a bug. The RestJiraDownloader that the plugin uses does not use the filter property at all.

I have filed an issue: https://issues.apache.org/jira/browse/MCHANGES-353 . I did check the local copy and fix it and it works as expected. Hopefully I will have time to submit the patch.



If you want to fix this yourself, go to the doExecute method in RestJiraDownloader and bind the filter method to the jqlQuery string string, like this:

    String jqlQuery = new JqlQueryBuilder( log ).urlEncode( false ).project( jiraProject ).fixVersion(
        getFixFor() ).fixVersionIds( resolvedFixVersionIds ).statusIds( resolvedStatusIds ).priorityIds(
        resolvedPriorityIds ).resolutionIds( resolvedResolutionIds ).components( resolvedComponentIds ).typeIds(
        resolvedTypeIds ).sortColumnNames( sortColumnNames ).filter(filter).build();

      

0


source







All Articles