When trying to create a new issue we receive the above error.
After reindexing we are able to create new issues exactly once - then the error occurs again.
Any idea how to fix that problem?
Hmm. I'm not sure then. I think you're going to have to go into the log file in detail.
Two places to look - when you get the error, and then again as you create a new issue just after re-indexing.
Also, what's the pattern? Is it every issue doing this?
Sounds like you've got a plugin providing a post-function or listener that is breaking something rather badly.
Look at your list of listeners - do you have anything catching "create issue" and doing something with it?
Look at the workflow - what post-functions do you have on the "create issue" transition?
I tried the log files already - not helpful to me :(
We only have stories and Zephyr test cases as main issue types. Tasks and Bugs are sub issues of the stories.
When I use the "Create Issue" button the error appears. When I use the Zephyr specific menu the "create issue" popup appears.
The logs should be throwing errors after creation, telling us a bit more about what they're trying to do. They're utter garbage for the end users, quite handy for developers, and they usually do have something an experienced Jira admin can get stuck into (you get class names, which can say a lot)
However, you've not mentioned Zephyr or different issue types before.
I think you need to do some structured testing - create an issue of each type, without Zephyr, doing the reindexing etc to provoke the error each time. Then try the same, creating through Zephyr.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs