|
Similar changes as shown in the text template can be made to your other veolcity templates (such as the standard HTML tempalte shipped with JIRA).
Keith,
In our JIRA installation, I have replaced the original files with the ones you provided. However, when trying to generate the releasenotes, I only get an empty page. I found the original files in ${JIRA}/atlassian-jira/WEB-INF/classes/... and have restarted JIRA afterwards. Where did you place the attached files?
Did you restart after replacing the old files with the new files? ReleaseManager.class was placed into ${JIRA_HOME}\atlassian-jira\WEB-INF\classes\com\atlassian\jira\project\util
releasenotes-text.vm was placed into ${JIRA_HOME}\atlassian-jira\WEB-INF\classes\templates\jira\project\releasenotes And yes, I have restared the server after replacing the files. Where there any errors in the logs when running the templates that returned empty pages?
My collegue Dylan van Iersel is away for three weeks. I will replace him the coming weeks.
I've installed the files again today (same procedure as described by Dylan). There were no errors in the logs. When you create release notes for a unreleased version, Jira opens: http://foo.bar/secure/ReleaseNote.jspa?version=10100&styleName=Text&projectId=10000&Create=Create which is empty, and only contains the standard footer: Powered by Atlassian JIRA™ (Professional Edition, Version: 2.6-#64)
I've attached the logfiles. Note that some of the messages in these logs might be related to I have tried the patch provided and get the same result - an empty page.
Apologies for the delay in responding - we very busy getting ready to release version 3.0 over the next couple of weeks.
I have attached two classes ReleaseNoteManager.class and ReleaseNoteManager$IssuesByType.class. I think the problem may have occurred due to the fact that I omitted the IssuesByType inner class previously. I have tested these classes and the updated template on JIRA 2.6 and the release notes correclty show the status and resolution. JIRA will need to be restarted once these classes and templates have been replaced. If further problems are encountered, please increase the logging level in the log4j.properties file by modifiying the following setting to DEBUG: log4j.rootLogger=WARN, console and attaching the output. The issue status and resolution is retrieved through the ConstantsManager. In the next release, the ConstantsManager will be passed to the velocity template so as users can customize their templates and reference the ConstantsManager as shown in the attached tempalte. Keith,
Thanks a lot for adding the files. We have installed: ReleaseManager.class and ReleaseNoteManager$IssuesByType.class are placed into ${JIRA_HOME}\atlassian-jira\WEB-INF\classes\com\atlassian\jira\project\util and it does exactly what we want (for the text-template). Thanks a lot! Issue can be closed. Can you also remove our logfiles of your system? Pieter Glad it's resolved. I have removed your logs.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Major
Releasenotes show all issues
I have attached a number of files that should generate a release note including the status and resolution. Please replace these files with those in your current JIRA instance.
The velocity template code is a little cramped - but this is so as the final formatting is correct - but this can be edited as suitable.
Let me know if this solution is viable - otherwise - I can attach a class with a modified search that will return only closed/resolved issues for the selected version.
Cheers,
Keith