|
thanks for the fast help, the subtasks are now properly displayed.
Justin,
Is there any plans to fix this permanently? Can I apply the attached fix to 3.6.2 or would I need another patch? Thank-You Maurice Hi Maurice,
This patch will work with a later release of JIRA just fine (the change is rather small). I am setting the fix for 3.7, the reason why this has not been implemented yet is that I believe there should be a little bit of configuration around whether or not to include sub-tasks in the notes. Since some sub-task's may be trivial a Project Manager may not want to show them in the release notes for a project version (or course you could always manually delete them). If you have any insight or comments on this please post them below. Cheers, Justin,
Thanks for the response. In our Agile environment we use JIRA to define our Stories (Defined just like a Task) and within each story we create all of the subtasks to complete the Story. However, as we plan these stories for each Iteration (Version), reality is that some of the subtasks are completed and some are not. Every iteration that is released is testable by the QA team. So the QA team will start to test these sub-tasks before the Story is actually complete, hence the need for showing the sub-tasks that were completed by Version. However, I can see your point that in some environments the Project Manager may not want to see them so yes adding an option to not show sub-tasks is a good idea. KEEP UP THE GREAT WORK WITH JIRA!! Maurice I think that release notes need to be rewritten as search request views, to allow people to make them pluggable.
If anyone else cares:
We use this patch and we also have made custom changes to the code, so having these 2 class files is a real pain trying to keep everything synced up... so, I diffed the decompile of these files and the original source The only code change is in the getTemplateVariables method change the line that calls constantsManager.getIssueTypes() Hi,
We upgraded to 3.7.2 from 3.6.2. This patch was working in 3.6.2 but putting it in 3.7.2 doesn't seem to work. Can someone confirm that it should work. If it should work, any ideas why it is not? Thanks for the help. Hi Maurice,
This patch will not work if you upgrade. For patched things it is best to verify that the bug is fixed in the version to which you upgrade before going ahead with the upgrade. I recommend going back to 3.6.2 if this is something that is possible for you. Thanks, Sorry Mario, but are you kidding?
There is a known bug which is almost 1 year old, you already have a patch for it and you ask your paying customers to waive their upgrades and lots of improvements goodbye because you didn't fix it yet in your release code? I understand where your recommendation comes from, but Atlassian should not make their customers pay when they screw up. Please fix this as soon as possible and deliver the functionality we pay for. Mario,
Of course rolling back to 3.6.2 is not an option especially considering that your upgrade procedure says that going once you go to 3.7, going back to your previous release is not trivial. Regardless of that we are running a company that relies heavily on JIRA. All the indications from the notes on this issue indicate that it will work with newer versions, the only item would be to make it configurable. There was never any indication that it wouldn't work with newer versions. I need a fix and I need it ASAP. Please provide the correction! Okay guys,
Just talked with the developers and they are taking a look at putting a new patch up for 3.7. It might require upgrading to the latest 3.7.3 but not sure yet. Mario Added a patch for JIRA 3.7.x.
Please download the ZIP file and replace the included .class files in your JIRA instance. This will make the sub-tasks to be included on release notes. Cheers, Thank-you for the quick turn around. We will install it and if there is any issue I will follow-up with some notes. If you don't hear from me, then it worked!
Dushan,
We replaced the files you provided and restarted JIRA but it doesn't seem to work. The Sub-Tasks still do not display. We placed the files here .../webapp/WEB-INF/classes/com/atlassian/jira/project/util It is a Linux install. Any ideas? Maurice,
Are you running standalone? or your own version of JIRA? If you are running standalone the classes you are replacing are: <Jira install directoty>/atlassian-jira/WEB-INF/classes/com/atlassian/jira/project/util/ReleaseNoteManager.class <Jira install directoty>atlassian-jira/WEB-INF/classes/com/atlassian/jira/project/util/ReleaseNoteManager$IssuesByType.class If you are running you own version of Tomcat and running it exploded under a directory called jira: <Tomcat directoty>/webapp/jira/WEB-INF/classes/com/atlassian/jira/project/util/ReleaseNoteManager.class <Tomcat directoty>/webapp/jira/WEB-INF/classes/com/atlassian/jira/project/util/ReleaseNoteManager$IssuesByType.class Can you check these for me? Cheers, Sorry for the delay. I was on vacation.
Here is the directory that it is installed in. It is a Tomcat 5.5 installation /logs/jira/JIRA3/webapp/WEB-INF/classes/com/atlassian/jira/project/util Any ideas why it is not working? |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Reopened
Minor
Subtasks are not displayed in the ReleaseNotes
These two classes will fix the current problem by showing sub-tasks. This is just a patch and not a permanent fix.
Steps:
Cheers,
Justin