...

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 is an example of using the Activity iteration in a Word template:

Image Added

or

Image Added

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

Image Added

or

Image Added

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

...

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 image below demonstrates an example of a Word template that iterates over

...

linked issues.

...

Image Added

or

...

Image Added

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

...

linked issues.

...

Image Added

or

...

Issue

...

Comments

Because it is not known in advance how many worklogs comments 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} 
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

Comment}
   ${dateformat("dd-MM-yyyy HH:mm:ss"):Worklogs[n].Created}
   ${dateformat("dd-MM-yyyy HH:mm:ss"):Worklogs[n].Date Started} 
   ${Worklogs[n].Time Spent}
   ${Worklogs[n].TimeSpentFormatted} 
#{end}
 
or
 
#{for <VariableName>=WorklogsCount}
   Content and Worklog Mappings. Example: ${Worklogs[VariableName].Field}
#{end}

Issue Sub-Tasks

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

#{for componentssubtasks}
   ${ComponentsSubtasks[n].NameKey}
   ${ComponentsSubtasks[n].DescriptionSummary}
   ${fullname:ComponentsSubtasks[n].LeadAssigneeUserDisplayName}
   ${Components[n].Id}
   ${Components[n].ProjectId#{end}
 
or
 
#{for <VariableName>=SubtasksCount}
   ${Components[n].AssigneeTypeContent and Issue Mappings. Example: ${Subtasks[VariableName].Field}
#{end}

...

...

Image RemovedImage Added

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

Image Added

or

Image Removed

...

Image Added

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 Status Transitions components exist for an issue, you can iterate a section over all the Status Transitions components of an issue. This allows you to create a table that dynamically grows according to the number of existing status transitionscomponents. The notation is:

#{for statusTransitionscomponents}
   ${StatusTransitionsComponents[n].AuthorName}
   ${dateformat("dd-MM-yyyy HH:mm:ss"):StatusTransitionsComponents[n].CreatedDescription}
   ${StatusTransitionsfullname:Components[n].OldStatusLead}
   ${StatusTransitionsComponents[n].NewStatusId}
#{end}
 
or
 
#{for <VariableName>=StatusTransitionsCount}
   Content and StatusTransitions Mappings. Example: ${StatusTransitions[VariableName].Field   ${Components[n].ProjectId}
   ${Components[n].AssigneeType}
#{end}

...

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

...

issue components.

Image Removed

or

Image Removed

...

Image Added

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

...

issue components.

...

Image Added

...

Image Removed

Issue

...

Status Transitions

Because it is not known in advance how many Images can Status Transitions exist for an issue (as an attachment), you can iterate a section over all the attached images Status Transitions 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 imagesstatus transitions. The notation is:

#{for imagesstatusTransitions}
   ${ImagesStatusTransitions[n].Image|maxwidth=150|maxheight=150Author}
   ${Images[n].Name}
   ${Images[n].ID}
   ${Images[n].Size}
   ${Images[n].HumanReadableSize}
   ${Images[n].Author}
   ${dateformat("dd-MM-yyyy dateformat("dd-MM-yyyy HH:mm:ss"):ImagesStatusTransitions[n].Created}
   ${ImagesStatusTransitions[n].MimeTypeOldStatus}
   ${ImagesStatusTransitions[n].ThumbnailURLNewStatus}
 ##{end}
 
or
 
#{for <VariableName>=ImagesCountStatusTransitionsCount}
   Content and ImagesStatusTransitions Mappings. Example: ${ImagesStatusTransitions[VariableName].Field}
#{end}

...

...

...

Image Removed

#{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 image below demonstrates an example of an Excel template that iterates over attached images. 

Image Removed 

or

Image Removed

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:

Issue Attached Images

Because it is not known in advance how many Images can exist for an issue (as an attachment), you can iterate a section over all the 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 images. The notation is:

#{for attachmentsimages}
   ${AttachmentsImages[n].IDImage|maxwidth=150|maxheight=150}
   ${AttachmentsImages[n].Name}
   ${AttachmentsImages[n].AuthorID}
   ${AttachmentsImages[n].AuthorFullNameSize}
   ${dateformat("dd-MM-yyyy HH:mm:ss"):AttachmentsImages[n].CreatedHumanReadableSize}
   ${AttachmentsImages[n].SizeAuthor}
   ${Attachmentsdateformat("dd-MM-yyyy HH:mm:ss"):Images[n].HumanReadableSizeCreated}
   ${AttachmentsImages[n].MimeType}
#   ${Images[n].ThumbnailURL}
 #{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 Added 

or

Image Removed

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

...

Image Added

#{for images

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}
   ${LabelsImages[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

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 image below demonstrates an example of an Excel template that iterates over labelsattached images. 

Image RemovedImage Added 

or

Image RemovedImage Added

Issue Activity

...

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 activityEntriesattachments}
   ${ActivityEntriesAttachments[n].TitleID}
   ${ActivityEntriesAttachments[n].SummaryName}
   ${ActivityEntriesAttachments[n].Content}
   ${ActivityEntries[n].Author}
   ${ActivityEntriesAttachments[n].AuthorEmailAuthorFullName}
   ${dateformat("dd-MM-yyyy HH:mm:ss"):ActivityEntriesAttachments[n].PublishedCreated}
   ${dateformat("dd-MM-yyyy HH:mm:ss"):ActivityEntriesAttachments[n].UpdatedSize}
   ${ActivityEntriesAttachments[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

...

HumanReadableSize}
   ${Attachments[n].MimeType}
#{end}
 
or
 
#{for <VariableName>=AttachmentsCount}
   Content and Issue Mappings. Example: ${Attachments[VariableName].Field}
#{end}

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

Image Added

or

Image Added

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

Image Added

Image Added

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 Added

or

Image Added

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

Image Added

or

Image Added

Project Versions

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

...