See attached file for complete trace.
Re-Index stops in NullPointerException after a Evaluation version of Zephyr for Jira 220.127.116.114 was installed and used for a few days. Disabling Zephyr let's the indexing go through but even reinstalling Z causes odd behaviour in Jira (filters show no issues for example) even when the "test" issue type is removed.
Caused by: java.lang.NullPointerException at com.thed.zephyr.je.config.customfield.TeststepCFType.getValueFromIssue(TeststepCFType.java:89)
Now I know this is probably a plugin problem (and will ask the provider), suspicion of a custom field that is mandatory in Jira is not in Zephyr but is there any way to narrow it down a little?
Just faced the same problem. Installed Zephyr (latest for now, 18.104.22.1684) with a trial period on JIRA 5.0.6 and after the middle of the following night (right after 00:00) indices started to behave strange. For example, a search for "project = X and status = Open" shows some issues in 'open' status, but when you go into the issue, you see that status is different. So I've thought, that there is a problem with indexes and I've issued re-indexing from administrator panel. Reindexing had not progressed from 0% for 4 minutes and 41 seconds and after that it gave me NullPointerException with the same message and backtrace. Well, at least it did not stuck forever :)
Disabling Zephyr allowed me to re-index JIRA issues. But reindexing much slower than before I've installed Zephyr (eight minutes instead of two), I don't know if this is related to this problem. I'm looking forward for a solution of this issue :) Thanks in advance.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot