Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×I have just upgraded from 6.1.2 to 6.1.3.1, specifically for the new Issues in Epic section of the issue detail view for epic type issues. After the upgrade and a re-index, I see the following error message inside the Issues in Epic section:
Error rendering WebPanel (templates/greenhopper/web/issue/panels/issues-in-epic-panel.vm): org.apache.velocity.exception.ResourceNotFoundException: Unable to find resource 'templates/greenhopper/web/issue/panels/issues-in-epic-panel.vm'
What should I try next?
The error (Unable to find resource 'templates/greenhopper/web/issue/panels/issues-in-epic-panel.vm') is related to a missing package on the JAR file of your Greenhopper plugin. Somehow your plugin have this missing .vm file which seems to be root cause of the problem.
This problem can be solved by following the steps below:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, have not found an answer yet. In contact with support trying to figure it out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have the excat same problem after upgrading to 6.1.3.2. Any chance you found a solution?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It might be worth trying upgrading to v6.13.2, just released today. This introduces the ability to:
Create Issue when viewing an Epic in JIRA
..so you know that the Epic section that concerns you has been touched by the new release. If you do not come right then you can submit a support request referencing "current GH version", and if you do come right then you have scored a bit of extra functionality as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, I upgraded to 6.1.3.2 but still have the same issue. In touch with support now!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.