[jira] [Comment Edited] (MCHANGES-357) Cannot include Unresolved issues
[ https://issues.apache.org/jira/browse/MCHANGES-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14695153#comment-14695153 ] Franck Malartic edited comment on MCHANGES-357 at 8/13/15 12:36 PM: Sorry for the delay. Here is the patch for not resolving Unresolved status with REST downloader. Tested with Jira 5.2.11. was (Author: graham2071): Here is the patch for not resolving Unresolved status with REST downloader. Tested with Jira 5.2.11. Cannot include Unresolved issues Key: MCHANGES-357 URL: https://issues.apache.org/jira/browse/MCHANGES-357 Project: Maven Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.11 Environment: Jira 5.2.11 Reporter: Franck Malartic Attachments: RestJiraDownloader.java.patch Using the jira-report goal, it is impossible to get Unresolved issues. Unresolved is not managed by Jira server like other resolution statuses. The REST API does not return the Unresolved status thus the plugin throws the following exception: org.apache.maven.plugin.MojoFailureException: Could not find resolution Unresolved. at org.apache.maven.plugin.jira.RestJiraDownloader.resolveOneItem(RestJiraDownloader.java:265) at org.apache.maven.plugin.jira.RestJiraDownloader.resolveList(RestJiraDownloader.java:246) at org.apache.maven.plugin.jira.RestJiraDownloader.resolveIds(RestJiraDownloader.java:212) at org.apache.maven.plugin.jira.RestJiraDownloader.doExecute(RestJiraDownloader.java:131) at org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute(AdaptiveJiraDownloader.java:47) at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:372) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:210) at org.apache.maven.plugin.changes.AbstractChangesReport.execute(AbstractChangesReport.java:207) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) at org.codehaus.classworlds.Launcher.main(Launcher.java:46) Note that you won't have the same error with the https://issues.apache.org/jira/ server, because the Unresolved status is redefined (id 9) https://issues.apache.org/jira/rest/api/2/resolution/ This is explicitly not recommended in Jira documentation: https://confluence.atlassian.com/display/JIRA/Defining+Resolution+Field+Values The redefinition of Unresolved shall lead to incorrect Jira status report. JQL with id=Unresolved is correct: https://issues.apache.org/jira/browse/MCHANGES-240?jql=project%20%3D%20MCHANGES%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC but with id=9 it is not (result is empty): https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCHANGES%20AND%20resolution%20%3D%209%20ORDER%20BY%20priority%20DESC And in that case, setting configuration resolutionIds to Unresolved will lead to the second sample
[jira] [Updated] (MCHANGES-357) Cannot include Unresolved issues
[ https://issues.apache.org/jira/browse/MCHANGES-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Franck Malartic updated MCHANGES-357: - Attachment: RestJiraDownloader.java.patch Here is the patch for not resolving Unresolved status with REST downloader. Tested with Jira 5.2.11. Cannot include Unresolved issues Key: MCHANGES-357 URL: https://issues.apache.org/jira/browse/MCHANGES-357 Project: Maven Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.11 Environment: Jira 5.2.11 Reporter: Franck Malartic Attachments: RestJiraDownloader.java.patch Using the jira-report goal, it is impossible to get Unresolved issues. Unresolved is not managed by Jira server like other resolution statuses. The REST API does not return the Unresolved status thus the plugin throws the following exception: org.apache.maven.plugin.MojoFailureException: Could not find resolution Unresolved. at org.apache.maven.plugin.jira.RestJiraDownloader.resolveOneItem(RestJiraDownloader.java:265) at org.apache.maven.plugin.jira.RestJiraDownloader.resolveList(RestJiraDownloader.java:246) at org.apache.maven.plugin.jira.RestJiraDownloader.resolveIds(RestJiraDownloader.java:212) at org.apache.maven.plugin.jira.RestJiraDownloader.doExecute(RestJiraDownloader.java:131) at org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute(AdaptiveJiraDownloader.java:47) at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:372) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:210) at org.apache.maven.plugin.changes.AbstractChangesReport.execute(AbstractChangesReport.java:207) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) at org.codehaus.classworlds.Launcher.main(Launcher.java:46) Note that you won't have the same error with the https://issues.apache.org/jira/ server, because the Unresolved status is redefined (id 9) https://issues.apache.org/jira/rest/api/2/resolution/ This is explicitly not recommended in Jira documentation: https://confluence.atlassian.com/display/JIRA/Defining+Resolution+Field+Values The redefinition of Unresolved shall lead to incorrect Jira status report. JQL with id=Unresolved is correct: https://issues.apache.org/jira/browse/MCHANGES-240?jql=project%20%3D%20MCHANGES%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC but with id=9 it is not (result is empty): https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCHANGES%20AND%20resolution%20%3D%209%20ORDER%20BY%20priority%20DESC And in that case, setting configuration resolutionIds to Unresolved will lead to the second sample query. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHANGES-357) Cannot include Unresolved issues
[ https://issues.apache.org/jira/browse/MCHANGES-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14618271#comment-14618271 ] Franck Malartic commented on MCHANGES-357: -- Yep, i'll do that this weekend if I find some time ! Cannot include Unresolved issues Key: MCHANGES-357 URL: https://issues.apache.org/jira/browse/MCHANGES-357 Project: Maven Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.11 Environment: Jira 5.2.11 Reporter: Franck Malartic Using the jira-report goal, it is impossible to get Unresolved issues. Unresolved is not managed by Jira server like other resolution statuses. The REST API does not return the Unresolved status thus the plugin throws the following exception: org.apache.maven.plugin.MojoFailureException: Could not find resolution Unresolved. at org.apache.maven.plugin.jira.RestJiraDownloader.resolveOneItem(RestJiraDownloader.java:265) at org.apache.maven.plugin.jira.RestJiraDownloader.resolveList(RestJiraDownloader.java:246) at org.apache.maven.plugin.jira.RestJiraDownloader.resolveIds(RestJiraDownloader.java:212) at org.apache.maven.plugin.jira.RestJiraDownloader.doExecute(RestJiraDownloader.java:131) at org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute(AdaptiveJiraDownloader.java:47) at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:372) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:210) at org.apache.maven.plugin.changes.AbstractChangesReport.execute(AbstractChangesReport.java:207) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) at org.codehaus.classworlds.Launcher.main(Launcher.java:46) Note that you won't have the same error with the https://issues.apache.org/jira/ server, because the Unresolved status is redefined (id 9) https://issues.apache.org/jira/rest/api/2/resolution/ This is explicitly not recommended in Jira documentation: https://confluence.atlassian.com/display/JIRA/Defining+Resolution+Field+Values The redefinition of Unresolved shall lead to incorrect Jira status report. JQL with id=Unresolved is correct: https://issues.apache.org/jira/browse/MCHANGES-240?jql=project%20%3D%20MCHANGES%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC but with id=9 it is not (result is empty): https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCHANGES%20AND%20resolution%20%3D%209%20ORDER%20BY%20priority%20DESC And in that case, setting configuration resolutionIds to Unresolved will lead to the second sample query. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHANGES-357) Cannot include Unresolved issues
[ https://issues.apache.org/jira/browse/MCHANGES-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14615182#comment-14615182 ] Franck Malartic commented on MCHANGES-357: -- Hi Michael, The ECSS software standard (ECSS stands for European Cooperation for Space Standards) states that the release document shall list known problems and on-going changes (in addition to what have been fixed in the release). Since the information is available in Jira (opened issues), i would like to generate a report with Unresolved issues (as well as a report with Closed issues in this version). Best regards, Franck Cannot include Unresolved issues Key: MCHANGES-357 URL: https://issues.apache.org/jira/browse/MCHANGES-357 Project: Maven Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.11 Environment: Jira 5.2.11 Reporter: Franck Malartic Using the jira-report goal, it is impossible to get Unresolved issues. Unresolved is not managed by Jira server like other resolution statuses. The REST API does not return the Unresolved status thus the plugin throws the following exception: org.apache.maven.plugin.MojoFailureException: Could not find resolution Unresolved. at org.apache.maven.plugin.jira.RestJiraDownloader.resolveOneItem(RestJiraDownloader.java:265) at org.apache.maven.plugin.jira.RestJiraDownloader.resolveList(RestJiraDownloader.java:246) at org.apache.maven.plugin.jira.RestJiraDownloader.resolveIds(RestJiraDownloader.java:212) at org.apache.maven.plugin.jira.RestJiraDownloader.doExecute(RestJiraDownloader.java:131) at org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute(AdaptiveJiraDownloader.java:47) at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:372) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:210) at org.apache.maven.plugin.changes.AbstractChangesReport.execute(AbstractChangesReport.java:207) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) at org.codehaus.classworlds.Launcher.main(Launcher.java:46) Note that you won't have the same error with the https://issues.apache.org/jira/ server, because the Unresolved status is redefined (id 9) https://issues.apache.org/jira/rest/api/2/resolution/ This is explicitly not recommended in Jira documentation: https://confluence.atlassian.com/display/JIRA/Defining+Resolution+Field+Values The redefinition of Unresolved shall lead to incorrect Jira status report. JQL with id=Unresolved is correct: https://issues.apache.org/jira/browse/MCHANGES-240?jql=project%20%3D%20MCHANGES%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC but with id=9 it is not (result is empty): https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCHANGES%20AND%20resolution%20%3D%209%20ORDER%20BY%20priority%20DESC And in that case,
[jira] [Updated] (MCHANGES-357) Cannot include Unresolved issues
[ https://issues.apache.org/jira/browse/MCHANGES-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Franck Malartic updated MCHANGES-357: - Description: Using the jira-report goal, it is impossible to get Unresolved issues. Unresolved is not managed by Jira server like other resolution statuses. The REST API does not return the Unresolved status thus the plugin throws the following exception: org.apache.maven.plugin.MojoFailureException: Could not find resolution Unresolved. at org.apache.maven.plugin.jira.RestJiraDownloader.resolveOneItem(RestJiraDownloader.java:265) at org.apache.maven.plugin.jira.RestJiraDownloader.resolveList(RestJiraDownloader.java:246) at org.apache.maven.plugin.jira.RestJiraDownloader.resolveIds(RestJiraDownloader.java:212) at org.apache.maven.plugin.jira.RestJiraDownloader.doExecute(RestJiraDownloader.java:131) at org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute(AdaptiveJiraDownloader.java:47) at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:372) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:210) at org.apache.maven.plugin.changes.AbstractChangesReport.execute(AbstractChangesReport.java:207) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) at org.codehaus.classworlds.Launcher.main(Launcher.java:46) Note that you won't have the same error with the https://issues.apache.org/jira/ server, because the Unresolved status is redefined (id 9) https://issues.apache.org/jira/rest/api/2/resolution/ This is explicitly not recommended in Jira documentation: https://confluence.atlassian.com/display/JIRA/Defining+Resolution+Field+Values The redefinition of Unresolved shall lead to incorrect Jira status report. JQL with id=Unresolved is correct: https://issues.apache.org/jira/browse/MCHANGES-240?jql=project%20%3D%20MCHANGES%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC but with id=9 it is not (result is empty): https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCHANGES%20AND%20resolution%20%3D%209%20ORDER%20BY%20priority%20DESC And in that case, setting configuration resolutionIds to Unresolved will lead to the second sample query. was: Using the jira-report goal, it is impossible to get Unresolved issues. Unresolved is not managed by Jira server like other resolution statuses. The REST API does not return the Unresolved status thus the plugin throws the following exception: org.apache.maven.plugin.MojoFailureException: Could not find resolution Unresolved. at org.apache.maven.plugin.jira.RestJiraDownloader.resolveOneItem(RestJiraDownloader.java:265) at org.apache.maven.plugin.jira.RestJiraDownloader.resolveList(RestJiraDownloader.java:246) at org.apache.maven.plugin.jira.RestJiraDownloader.resolveIds(RestJiraDownloader.java:212) at org.apache.maven.plugin.jira.RestJiraDownloader.doExecute(RestJiraDownloader.java:131) at
[jira] [Created] (MCHANGES-357) Cannot include Unresolved issues
Franck Malartic created MCHANGES-357: Summary: Cannot include Unresolved issues Key: MCHANGES-357 URL: https://issues.apache.org/jira/browse/MCHANGES-357 Project: Maven Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.11 Environment: Jira 5.2.11 Reporter: Franck Malartic Using the jira-report goal, it is impossible to get Unresolved issues. Unresolved is not managed by Jira server like other resolution statuses. The REST API does not return the Unresolved status thus the plugin throws the following exception: org.apache.maven.plugin.MojoFailureException: Could not find resolution Unresolved. at org.apache.maven.plugin.jira.RestJiraDownloader.resolveOneItem(RestJiraDownloader.java:265) at org.apache.maven.plugin.jira.RestJiraDownloader.resolveList(RestJiraDownloader.java:246) at org.apache.maven.plugin.jira.RestJiraDownloader.resolveIds(RestJiraDownloader.java:212) at org.apache.maven.plugin.jira.RestJiraDownloader.doExecute(RestJiraDownloader.java:131) at org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute(AdaptiveJiraDownloader.java:47) at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:372) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:210) at org.apache.maven.plugin.changes.AbstractChangesReport.execute(AbstractChangesReport.java:207) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) at org.codehaus.classworlds.Launcher.main(Launcher.java:46) Note that you won't have the same error with the https://issues.apache.org/jira/ server, because the Unresolved status is redefined (id 9) https://issues.apache.org/jira/rest/api/2/resolution/ This is explicitly not recommended in Jira documentation: https://confluence.atlassian.com/display/JIRA/Defining+Resolution+Field+Values The redefinition of Unresolved shall lead to incorrect Jira status report. JQL with id=Unresolved is correct: https://issues.apache.org/jira/browse/MCHANGES-240?jql=project%20%3D%20MCHANGES%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC but with id=9 it is not (result is empty): project = MCHANGES AND resolution = 9 ORDER BY priority DESC And in that case, setting configuration resolutionIds to Unresolved will lead to the second sample query. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
