Page History
...
Field | Content |
---|---|
AffectedVersions | The project versions affected by the issue (a list with 1 version per line). |
AffectedVersionsList | The project versions affected by the issue (separated by commas). |
AggregateOriginalEstimate | The sum of the originally estimated time for issue completion, in seconds. |
AggregateOriginalEstimateFormatted | The sum of the originally estimated time for issue completion formatted as defined in the the Jira Time Tracking options. |
AggregateRemainingEstimate | The sum of the remaining estimated time for issue completion, in seconds. |
AggregateRemainingEstimateFormatted | The sum of the remaining estimated time for issue completion formatted as defined in the the Jira Time Tracking options. |
AggregateTimeSpent | The sum of time spent working on the issue, in seconds. |
AggregateTimeSpentFormatted | The sum of time spent working on the issue formatted as defined in the Jira Time Tracking options. |
AssigneeId | The issue assignee ID. |
AssigneeUserDisplayName | The issue assignee Jira display name. |
AssigneeUserEmailAddress | The issue assignee Jira email address. |
AssigneeUserName | The issue assignee Jira username. |
AssigneeGroups | The groups to which the issue assignee belongs. |
AttachmentsCount | Returns the number of attachments in the Issue. |
BelongsToEpic | Returns "true" if the current issue belongs to an Epic Issue; otherwise, it returns "false". |
BulkIssueIndex | The index/position of the current issue being mapped. Usable only in bulk export. 0 is the index for the first issue. |
BulkIssuesCount | The number of issues selected in a bulk export. Usable only in bulk export. |
CommentsCount | Returns the number of comments in the Issue. |
Components | The components to which an issue belongs. |
ComponentsCount | Returns the number of components in the Issue. |
Created | The issue creation date time in ISO Format. If you want to print only the date, you should use ${dateformat("yyyy-MM-dd"):Created}. If you want to print the date and time, you should use ${dateformat("dd-MM-yyyy HH:mm:ss"):Created} |
Current Date | Returns the current date. |
Current Date Time | Returns the current date time. |
Description | The issue description. |
DocumentId | Unique ID generated identifying the document. |
Due Date | The issue due date. |
Environment | The issue environment. |
EstimatedTime | The estimated time for issue completion. Do not use this field as it will become soon deprecated . Use RemainingEstimate . |
FilterJQL | Current JQL used to search Issues. |
FilterName | Current Filter Name used to search Issues. |
FixVersions | The versions an issue fixes. |
FixVersionsReleaseDate | The release date of the versions an issue fixes. |
FixVersionsList | The versions an issue fixes, separated by commas. |
FixVersionsReleaseDateList | The release dates of the versions being fixed by an issue, separated by commas. |
Id | The issue ID. For example, 1. |
Images | When used as a single field "${Images}", it renders the images List of images attached to the issue. Images are rendered in an order respecting the creation date. For this field, you are allowed to define extra attributes with the max image width, max image height and the sort order of the images. Examples: ${Images|maxwidth=100|maxheight=100} ${Images|maxwidth=100|maxheight=100|sortby=name} ${Images|maxwidth=100|maxheight=100|sortby=date} Note: You can iterate over images and get some metadata from them. |
ImagesCount | Returns the number of images attached to the Issue. |
IssueTypeDescription | The issue type description. |
IssueTypeDescriptionTranslated | The translated issue type description. |
IssueTypeName | The issue type. |
IssueTypeNameTranslated | The translated issue type. |
Issue Type | The Issues Type name. |
Issue Type.Id | The id of the issue type. |
Issue Type.Name | The Name of the issue type. |
Issue Type.Type | The Type of the issue type. |
Issue Type.IconURL | The Icon URL of the issue type. |
JQLIssuesCount | The number of the issues returned by the parent JQL Iteration. |
Key | The internal issue Key. For example, PROJECT-1. |
Labels | The issue labels. |
LinksCount | Returns the number of links to the Issue. |
OriginalEstimate | The originally estimated time for issue completion, in seconds. |
OriginalEstimateFormatted | The originally estimated time for issue completion formatted as defined in the Jira Time Tracking options. |
ParentIssueDescription | The parent issue description. |
ParentIssueId | The parent issue ID. |
ParentIssueKey | The parent issue key. |
Priority | The issue priority. |
PriorityTranslated | The issue priority translated into the language of the logged user. |
PriorityDescription | The issue priority description. |
PriorityDescriptionTranslated | The issue priority description translated into the language of the logged user. |
Project.Components | The project components an issue belongs. |
Project.Category | The issue project category. |
Project.Id | The issue project Id. |
Project.Key | The issue project key. |
Project.Name | The issue project name. |
Project.URL | The issue project URL. |
Project.Lead | The issue project leader. |
RemainingEstimate | The remaining estimated time for issue completion, in seconds. |
RemainingEstimateFormatted | The remaining estimated time for issue completion formatted as defined in the Jira Time Tracking options. |
ReporterId | The issue reporter ID. |
ReporterUserDisplayName | The issue assignee Jira display name. |
ReporterUserEmailAddress | The issue assignee Jira email address. |
ReporterUserName | The issue reporter Jira username. |
ReporterGroups | The groups to which the issue reporter belongs. |
Resolution | The issue resolution. |
ResolutionTranslated | The issue resolution translated into the language of the logged user. |
Resolved | The issue resolution date in ISO format. If you want to print only the date, you should use ${dateformat("yyyy-MM-dd"):Resolved} .If you want to print the date and time, you should use ${dateformat("dd-MM-yyyy HH:mm:ss"):Resolved}. |
ResolutionDescription | The issue resolution description. |
ResolutionDescriptionTranslated | The issue resolution description translated into the language of the logged user. |
ResolutionDesc | The Resolution Description |
SecurityLevel | The issue security level. |
SecurityLevelId | The issue security level ID. |
Status | The issue status. |
StatusTranslated | The issue status translated into the language of the logged user. |
StatusTransitionsCount | Returns the number of status transitions of the Issue. |
StatusDescription | The issue status description. |
StatusDescriptionTranslated | The issue status description translated to the language of the logged user. |
Sprint | The Issue Sprint Name. |
SubTasks | List of issue subtasks. |
SubtasksCount | Returns the number of subtasks of the Issue. |
Summary | The issue summary. |
Time Spent | The time spent working on the issue. |
Updated | The issue update timestamp. If you want to print only the date, you should use ${dateformat("yyyy-MM-dd"):Updated}. If you want to print the date and time, you should use ${dateformat("dd-MM-yyyy HH:mm:ss"):Updated}. |
Username | Username of the user that is requesting the export. If you want to get the fullname of the user please use de function ${fullname:Username} and to get the e-mail address of the user ${emailaddress:Username} |
URL | Returns the URL of the Issue detail screen. |
Votes | Prints the number of votes. |
Watches | The number of watches of the issue. |
Watchers | Returns a list of Users that are watching the Issue. Functions: fullname and emailaddress can be used with this field. |
Parent | Return fields from Parent issues. |
...
If you have Custom Fields with the same name, it is possible to explicitly indicate the custom field that you want to export using its internal Jira identifier. You can find the identifier of a custom field, by going to the Jira administration, section fields, and edit the custom field. The id ID will appear in the URL (ex: http://jiraserver/secure/admin/EditCustomField!default.jspa?id=10070). The notation to be used is:
...