Organizing Issues and Issue Types by Component in Release Notes Template

I'm attempting to organize my Release Notes template so that it looks something like this:

Component

Bug
- Issue 1
- Issue 2...

Improvement
- Issue 1
- Issue 2...

Task/SOP
- Issue 1
- Issue 2...

Sub-task
- Issue 1
- Issue 2...

Bug

Component A
- Issue 1
- Issue 2...
Component B
- Issue 1...

Improvement

Component A
- Issue 1
- Issue 2...

...

Is this possible? I know you can get all the Issues from an IssueType - but is there any way to say 'component.issueType.issues', or even 'issuetype.component.issues'.

If you have a suggestion for another direction that would be great as well.

Thanks!

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

3 votes

The code below works for me (Jira 4.4). It's of course not the cleanest way, so feel free to refactor in the next answers.

## GET COMPONENTS FOR THE CURRENT PROJECT
#set ($components = [])
#foreach ($issueType in $issueTypes)
	#if ($issueType.issues.size() &gt; 0)
		#foreach($issue in $issueType.issues)
			#if ($issue.componentObjects.size() &gt; 0)
				#foreach($component in $issue.componentObjects)
					#if ($components.contains($component.name) == false)
						#set( $echoOf = $components.add($component.name))
					#end
				#end
			#end
		#end
	#end
#end
##
##
#foreach ($component in $components)
	&lt;h3&gt;$component&lt;/h3&gt;
	&lt;ul&gt;
	#foreach ($issueType in $issueTypes)
		#if($issueType.issues.size() &gt; 0)
			#set ($tmpIssuesArray = [])
			#foreach ($issue in $issueType.issues)
				#if ($issue.componentObjects.size() &gt; 0)
					#foreach($issuecomponent in $issue.componentObjects)
						#if ($issuecomponent.name == $component)
							#set( $echoOf = $tmpIssuesArray.add($issue))
						#end
					#end
				#end
			#end
			
			#if ($tmpIssuesArray.size() &gt; 0)
				&lt;li&gt;
				&lt;h4&gt;$textUtils.htmlEncode($issueType.name)&lt;/h4&gt;
				&lt;ul&gt;
				#foreach ($issue in $tmpIssuesArray)
					&lt;li&gt;[&lt;a href='$requestContext.canonicalBaseUrl/browse/$issue.key'&gt;$issue.key&lt;/a&gt;] - $textUtils.htmlEncode($issue.summary)&lt;/li&gt;
				#end
				&lt;/ul&gt;
				&lt;/li&gt;
			#end
			
		#end
	#end
	&lt;/ul&gt;
#end

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

This worked great for me in Jira 7. Exactly what I was looking for. All I had to do was replace the < and > notation with < and > respectivly. Thanks @[deleted]

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

I was not able to get this to work for our JIRA v.6.4.6 instance. I followed the instructions to "Add a new custom style for Jira release notes" and added header formatting from the Text release notes but this component report shows a blank page. Has anyone confirmed that the above template works, or does is it missing something?