...

Issue

...

Activity

Changes to issues are registered in the Issue Activity, but it is not known in advance how many changes are going to be made.

...

You can iterate a section over all the

...

activities of an issue. This allows you to create a table that dynamically grows according to the number of

...

existing activities. The notation is:

...

Exportable Data

The notation is:

#{for historyEntriesactivityEntries}
   ${fullname:HistoryEntriesActivityEntries[n].AuthorTitle}
 made changes ${dateformat("dd-MM-yyyy HH:mm:ss"):HistoryEntriesActivityEntries[n].CreatedSummary}
  #{for ch=HistoryEntries ${ActivityEntries[n].ChangedItemsCountContent}
	Field  Name: ${HistoryEntriesActivityEntries[n].ChangedItems[ch].FieldAuthor}
	Old Value:  ${HistoryEntriesActivityEntries[n].ChangedItems[ch].From}
	New Value:  ${HistoryEntries[n].ChangedItems[ch].To}
  #{end} AuthorEmail}
   ${dateformat("dd-MM-yyyy HH:mm:ss"):ActivityEntries[n].Published}
   ${dateformat("dd-MM-yyyy HH:mm:ss"):ActivityEntries[n].Updated}
   ${ActivityEntries[n].Categories}
#{end}
 
or
 
#{for h<VariableName>=HistoryEntriesCountActivityEntriesCount}
    ${fullname:HistoryEntries[h].Author} made changes    ${dateformat("dd-MM-yyyy HH:mm:ss"):HistoryEntries[h].Created}
   #{for ch=HistoryEntries[h].ChangedItemsCount}
	Field Name: ${HistoryEntries[h].ChangedItems[ch].Field}
	Old Value:  ${HistoryEntries[h].ChangedItems[ch].From}
	New Value:  ${HistoryEntries[h].ChangedItems[ch].To}
   #{end} 
#{end}

Issue Links

Content and Issue Mappings. Example: ${ActivityEntries[VariableName].Field}
#{end}

Below are two examples of using the Activity iteration in a Word and Excel template:

Image Added Iterating_Activity_Entries.docx

Image Added Iterating_Activity_Entries.xlsx

Issue History

You Because it is not known in advance how many linked issues exist for an issue, you can iterate a section over all the linked issues history entries of an issue. This allows you to create a table that dynamically grows according to the number of existing linked issueschanges done. 

Exportable Data

Note:  When the link you are iterating is of AppTypes External Jira or Confluence, the name is obtained using the Summary property.

The notation is:

#{for linkshistoryEntries}
   ${Linksfullname:HistoryEntries[n].AppTypeAuthor}
 made changes ${Linksdateformat("dd-MM-yyyy HH:mm:ss"):HistoryEntries[n].LinkTypeCreated}
   ${Links#{for ch=HistoryEntries[n].KeyChangedItemsCount}
	Field Name:  ${LinksHistoryEntries[n].Summary}
 ChangedItems[ch].Field}
	Old Value:  ${HistoryEntries[n].ChangedItems[ch].From}
	New Value:  ${LinksHistoryEntries[n].ChangedItems[ch].URL}To}
  #{end} 
#{end}
  
or
 
#{for <VariableName>h=LinksCountHistoryEntriesCount}
   Content and Linked Issue Mappings. Example: ${Links[VariableName].Field}
#{end}

The image below demonstrates an example of a Word template that iterates over linked issues.

Image Removed

or

Image Removed

The image below demonstrates an example of an Excel template that iterates over linked issues.

Image Removed

or

...

${fullname:HistoryEntries[h].Author} made changes    ${dateformat("dd-MM-yyyy HH:mm:ss"):HistoryEntries[h].Created}
   #{for ch=HistoryEntries[h].ChangedItemsCount}
	Field Name: ${HistoryEntries[h].ChangedItems[ch].Field}
	Old Value:  ${HistoryEntries[h].ChangedItems[ch].From}
	New Value:  ${HistoryEntries[h].ChangedItems[ch].To}
   #{end} 
#{end}

Issue Links

Because it is not known in advance how many comments linked issues exist for an issue, you can iterate a section over all the comments on linked issues of an issue. This allows you to create a table that dynamically grows according to the number of existing comments. The notation is:linked issues. 

Exportable Data

Note:  When the link you are iterating is of AppTypes External Jira or Confluence, the name is obtained using the Summary property.

The notation is:

#{for commentslinks}
   ${CommentsLinks[n].AuthorAppType} 
   ${CommentsLinks[n].AuthorFullNameLinkType} 
   ${CommentsLinks[n].BodyKey} 
   ${dateformat("dd-MM-yyyy HH:mm:ss"):Comments[n].CreatedLinks[n].Summary}
   ${CommentsLinks[n].GroupLevelURL}
#{end}
 
or
 
#{for <VariableName>=CommentsCountLinksCount}
   Content and Linked Issue Mappings. Example: ${CommentsLinks[VariableName].Field}
#{end}

...

The documents below

...

demonstrates an example of a

...

template that iterates over

...

linked issues.

Image Removed

or

Image Removed

The image below demonstrates an example of an Excel template that iterates over issue comments.

Image Removed

or

Image Removed

Issue Worklogs

Image Added Iterating_Issue_Links.docx

Image Added Iterating_Issue_Links.xlsx

Issue Comments

Because it is not known in advance how many comments exist for an Because it is not known in advance how many worklogs exist for an issue, you can iterate a section over all the worklogs of comments on an issue. This allow allows you to create a table that dynamically grows according to the number of existing worklogscomments. The notation is:

#{for worklogscomments}
   ${WorklogsComments[n].Author} 
   ${WorklogsComments[n].AuthorFullName}  
   ${WorklogsComments[n].CommentBody} 
   ${dateformat("dd-MM-yyyy HH:mm:ss"):WorklogsComments[n].Created}
   ${dateformat("dd-MM-yyyy HH:mm:ss"):Worklogs[n].Date Started} 
   ${Worklogs[n].Time Spent}
   ${Worklogs[n].TimeSpentFormatted} 
#{end}
 
or
 Comments[n].GroupLevel}
#{end}
 
or
 
#{for <VariableName>=WorklogsCountCommentsCount}
   Content and WorklogIssue Mappings. Example: ${WorklogsComments[VariableName].Field}
#{end}

Issue Sub-Tasks

Because it is not Because it is not known in advance how many subtasks worklogs exist for an issue, you can iterate a section over all the subtasks worklogs of an issue. This allows allow you to create a table that dynamically grows according to the number of existing subtasksworklogs. The notation is:

#{for subtasksworklogs}
   ${SubtasksWorklogs[n].KeyAuthor} 
   ${SubtasksWorklogs[n].SummaryAuthorFullName} 
   ${SubtasksWorklogs[n].AssigneeUserDisplayName}
#{end}
 
or
 
#{for <VariableName>=SubtasksCount}
   Content and Issue Mappings. Example: ${Subtasks[VariableName].Field}
#{end}

Image Removed

The image below demonstrates an example of an Excel template that iterates over issue subtasks.

Image Removed

or

Image Removed

For an example of how to iterate the details of a subtask Parent issue, please check the Iterating JQL Queries area below.

Issue Components

Because it is not known in advance how many components exist for an issue, you can iterate a section over all the components of an issue. This allows you to create a table that dynamically grows according to the number of existing components. The notation is:

...

#{for components}
   ${Components[n].Name}Comment}
   ${dateformat("dd-MM-yyyy HH:mm:ss"):Worklogs[n].Created}
   ${dateformat("dd-MM-yyyy HH:mm:ss"):Worklogs[n].Date Started} 
   ${ComponentsWorklogs[n].DescriptionTime Spent}
   ${fullname:ComponentsWorklogs[n].LeadTimeSpentFormatted} 
#{end}
 
or
  ${Components[n].Id}
   ${Components[n].ProjectId}
   ${Components[n].AssigneeType
#{for <VariableName>=WorklogsCount}
   Content and Worklog Mappings. Example: ${Worklogs[VariableName].Field}
#{end}

 The image below demonstrates an example of a Word template that iterates over issue components.

Image Removed

 The image below demonstrates an example of an Excel template that iterates over issue components.

Image Removed

...

Issue Sub-Tasks

Because it is not known in advance how many Status Transitions subtasks exist for an issue, you can iterate a section over all the Status Transitions subtasks of an issue. This allows you to create a table that dynamically grows according to the number of existing status transitionssubtasks. The notation is:

#{for statusTransitionssubtasks}
   ${StatusTransitionsSubtasks[n].AuthorKey}
   ${dateformat("dd-MM-yyyy HH:mm:ss"):StatusTransitionsSubtasks[n].Created}
   ${StatusTransitions[n].OldStatusSummary}
   ${StatusTransitionsSubtasks[n].NewStatusAssigneeUserDisplayName}
#{end}
 
or
  
#{for <VariableName>=StatusTransitionsCountSubtasksCount}
   Content and StatusTransitionsIssue Mappings. Example: ${StatusTransitionsSubtasks[VariableName].Field}
#{end}

...

Image Added Iterating_Issue_Subtasks.docx

Image Added Iterating_Issue_Subtasks.xlsx

For an example of how to iterate the details of a subtask Parent issue, please check the Iterating JQL Queries area below.

Issue Components

Because it is not known in advance how many Images can components exist for an issue (as an attachment), you can iterate a section over all the attached images components of an issue to get some metadata about them. This allows you to create a table that dynamically grows according to the number of existing imagescomponents. The notation is:

#{for components#{for images}
   ${Images[n].Image|maxwidth=150|maxheight=150}
   ${Images[n].Name}
   ${Images[n].ID}
   ${Images[n].Size}
   ${ImagesComponents[n].HumanReadableSizeName}
   ${ImagesComponents[n].AuthorDescription}
   ${dateformat("dd-MM-yyyy HH:mm:ss"):Imagesfullname:Components[n].CreatedLead}
   ${ImagesComponents[n].MimeTypeId}
   ${ImagesComponents[n].ThumbnailURL}
 #{end}
 
or
 
#{for <VariableName>=ImagesCount}
   Content and Images Mappings. Example:ProjectId}
   ${ImagesComponents[VariableNamen].FieldAssigneeType}
#{end}

The image below demonstrates an example of a Word template that iterates over attached images. 

Image Removed 

or

Image Removed

...

 The documents below demonstrate an example of a template that iterates over issue components.

Image Added Iterating_Issue_Components.docx

Image Added Iterating_Issue_Components.xlsx

Issue Status Transitions

Because it is not known in advance how many Status Transitions exist for an issue, you can iterate a section over all the Status Transitions of an issue. This allows you to create a table that dynamically grows according to the number of existing status transitions. The notation is:

...

#{for statusTransitions}
   ${StatusTransitions[n].Author}
   ${dateformat("dd-MM-yyyy HH:mm:ss"):StatusTransitions[n].Created}
   ${StatusTransitions[n].OldStatus#{for images}
   ${ImagesStatusTransitions[n].Image|width=150|height=150NewStatus}
 #{end}

These values are in pixels and if you only define one of them the image will be rescaled.

The image below demonstrates an example of an Excel template that iterates over attached images. 

Image Removed 

or

Image Removed

...

#{end}
 
or
 
#{for <VariableName>=StatusTransitionsCount}
   Content and StatusTransitions Mappings. Example: ${StatusTransitions[VariableName].Field}
#{end}

Issue Attached Images

Because it is not known in advance how many attachments Images can exist in for an issue (as an attachment), you can iterate a section over all the attachments of attached images of an issue to get some metadata about them. This allows you to create a table that dynamically grows according to the number of existing attachmentsimages. The notation is:

#{for attachments images}
   ${Images[n].Image|maxwidth=150|maxheight=150}
   ${Images[n].Name}
   ${AttachmentsImages[n].ID}
   ${AttachmentsImages[n].NameSize}
   ${AttachmentsImages[n].AuthorHumanReadableSize}
   ${AttachmentsImages[n].AuthorFullNameAuthor}
   ${dateformat("dd-MM-yyyy HH:mm:ss"):AttachmentsImages[n].Created}
   ${AttachmentsImages[n].SizeMimeType}
   ${Attachments[n].HumanReadableSize}
   ${AttachmentsImages[n].MimeTypeThumbnailURL}
# #{end}
 
or
  
#{for <VariableName>=AttachmentsCountImagesCount}
   Content and IssueImages Mappings. Example: ${AttachmentsImages[VariableName].Field}
#{end}

The image below demonstrates an example of a Word template that iterates over

...

attached images.

...

Image Removed

or

Image Removed

The image below demonstrates an example of an Excel template that iterates over attachments.

...

Image Added Iterating_Issue_Images.docx

#{for images}
   ${Images[n].Image|width=150|height=150}
 #{end}

These values are in pixels and if you only define one of them the image will be rescaled.

The documents below demonstrate an

Image Removed

Issue Labels

Because it is not known in advance how many labels exist in an issue, you can iterate a section over all the labels of an issue. The notation is:

...

#{for labels}
   ${Labels[n].Name}
#{end}
 
or
 
#{for <VariableName>=LabelsCount}
  ${Labels[VariableName].Name}
#{end}

The image below demonstrates an example of a Word template that iterates over labels.

Image Removed

or

Image Removed

The image below demonstrates an example of an Excel template that iterates over labelsattached images.

Image Removed

or

Image Removed

Issue Activity

...

Image Added Iterating_Issue_Images.xlsx

Issue Attachments

Because it is not known in advance how many

...

attachments exist in an issue, you can iterate a section over all the

...

attachments of an issue. This allows you to create a table that dynamically grows according to the number of existing

...

attachments. The notation is:

#{for activityEntries attachments}
   ${Attachments[n].ID}
   ${Attachments[n].Name}
   ${Attachments[n].Author}
   ${Attachments[n].AuthorFullName}
   ${ActivityEntries${dateformat("dd-MM-yyyy HH:mm:ss"):Attachments[n].TitleCreated}
   ${ActivityEntriesAttachments[n].SummarySize}
   ${ActivityEntriesAttachments[n].ContentHumanReadableSize}
   ${ActivityEntriesAttachments[n].AuthorMimeType}
#{end}
 
or
 
#{for <VariableName>=AttachmentsCount}
   ${ActivityEntries[n].AuthorEmail}
   ${dateformat("dd-MM-yyyy HH:mm:ss"):ActivityEntries[n].Published}
   ${dateformat("dd-MM-yyyy HH:mm:ss"):ActivityEntries[n].Updated}
   ${ActivityEntries[n].Categories}
#{end}
 
or
 
#{for <VariableName>=ActivityEntriesCount}
   Content and Issue Mappings. Example: ${ActivityEntries[VariableName].Field}
#{end}

Below is an example of using the Activity iteration in a Word template:

Image Removed

or

Image Removed

Below is an example of using the Activity iteration in an Excel template:

Image Removed

or

...

Content and Issue Mappings. Example: ${Attachments[VariableName].Field}
#{end}

Image Added Iterating_Issue_Attachments.xlsx

Issue Labels

Because it is not known in advance how many labels exist in an issue, you can iterate a section over all the labels of an issue. The notation is:

#{for labels}
   ${Labels[n].Name}
#{end}
 
or
 
#{for <VariableName>=LabelsCount}
  ${Labels[VariableName].Name}
#{end}

The documents below demonstrate an example of a template that iterates over labels.

Image Added Iterating_Issue_Labels.docx

Image Added Iterating_Issue_Labels.xlsx

Project Versions

You can iterate over all project versions to which the issue belong to. The notation is:

...

#{for projectVersions}
   ${ProjectVersions[n].Name}
   ${ProjectVersions[n].Description}
   ${dateformat("dd-MM-yyyy"):ProjectVersions[n].Start date}
   ${dateformat("dd-MM-yyyy"):ProjectVersions[n].Release date}
#{end}
 
or
 
#{for <VariableName>=ProjectVersionsCount}
   ${ProjectVersions[VariableName].Name}
   ${ProjectVersions[VariableName].Description}
   ${dateformat("dd-MM-yyyy"):ProjectVersions[VariableName].Start date}
   ${dateformat("dd-MM-yyyy"):ProjectVersions[VariableName].Release date}
#{end}

The image The documents below demonstrates an demonstrate an example of a Word template that iterates over project version.

Image Removed

or

Image Removed

The image below demonstrates an example of an Excel template that iterates over project version.

Image Removed

or

Image Removed

Image Added Iterating_Issue_ProjectVersions.docx

Image Added Iterating_Issue_ProjectVersions.xlsx

Iterating JQL Queries

You can iterate issues that are the result of a JQL Query. The syntax is similar to the other iterations, but there is a clause parameter that will receive the JQL Query. A few examples are provided below.

a simple example iterating the details of issues from a specified Project:
 
#{for i=JQLIssuesCount|clause=project = DEMO}
   ${JQLIssues[i].Key}
   ${JQLIssues[i].Summary} 
#{end}

or a more advanced example iterating the details of issues linked with the current Issue:
 
#{for m=JQLIssuesCount|clause=issuekey in linkedIssues (${Links[j].Key})}
   Linked Issue ${JQLIssues[m].Summary} has ${JQLIssues[m].LinksCount} links
#{end} 
 
or an also advanced example iterating the details of the Parent issue from the current Subtask:
 
#{for i=JQLIssuesCount|clause=issuekey = ${ParentIssueKey}}
	${JQLIssues[i].Key}
	${JQLIssues[i].Id}
	${JQLIssues[i].Description}
#{end}

The image below demonstrates an example of an Excel template that iterates over issue subtasks.

Image Added Iterating_JQLIssues.xlsxImage Removed 
 

...

Links Bugs with High Priority:Image Removed

Image Added Links_Bugs_HighPriority.docx

Nested Iterations:Image Removed

Image Added Links_Nested_Iterations.docx

Iterating in the same line of the document

...