We have added XRAY as a plug-in to our JIRA.
Part of XRAY is the ability go generate Reports using the Doc Generator feature. We have configured to generate our reports from the "Test Plan" issue.
Currently, we are unable to Export any of the reports. Once we initiate the "Generate Report" option, the progress bar is stuck at 0% and will not move. This is specifically only affecting Test Plan issues that were created on June 23 or later.
Here is a snapshot of part of the logs in which we identified the error.
2022-06-29 11:43:39,503-0400 DocGenUpdateProcess-9e818443-9713-40c0-8c8c-2b11c936e36d ERROR denesh.parthipan 113x222645x1 11r3mrn 10.133.136.92 /rest/raven/1.0/docgen/export/background [c.x.r.d.g.engine.impl.DocumentBuildLookupImpl] sleep interrupted
2022-06-29 11:43:39,503-0400 xray-docgen-export-executor:thread-2 DEBUG denesh.parthipan 113x222645x1 11r3mrn 10.133.136.92 /rest/raven/1.0/docgen/export/background [c.x.raven.repository.i] It took 0 ms to UPDATE a row of the table com.xpandit.raven.model.document.generator.Process
2022-06-29 11:43:39,550-0400 xray-docgen-export-executor:thread-2 INFO denesh.parthipan 113x222645x1 11r3mrn 10.133.136.92 /rest/raven/1.0/docgen/export/background [c.x.j.c.d.b.i.aspose.word.AsposeWordConverter] Word export document started...
2022-06-29 11:43:39,550-0400 xray-docgen-export-executor:thread-2 ERROR denesh.parthipan 113x222645x1 11r3mrn 10.133.136.92 /rest/raven/1.0/docgen/export/background [c.x.j.c.d.b.i.aspose.word.AsposeWordConverter] An error has occurred while Xporter was generating the Word report.
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(ArrayList.java:659)
at java.util.ArrayList.get(ArrayList.java:435)
at com.xpandit.jiraxporter.commons.document.builder.impl.aspose.word.utils.AsposeWordUtils.resolveProperties(Unknown Source)
at com.xpandit.jiraxporter.commons.document.builder.impl.aspose.word.AsposeWordConverter.convert(Unknown Source)
at com.xpandit.raven.queue.ExportRunner.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Please let us know if you have any feedback on how to resolve this issue, as it is a SHOWSTOPPER on our end and a CRITICAL issue.
