Jira Work Management Fields Reference

Field Name

Field ID

Field Type

Field Explanation

Example

Issues

Issue ID

Id

Int64

Issue ID is the internal ID of the Jira issue which is internally used in Jira database to refer to an issue. This is the unique ID for a Jira issue and does not change.

^{The fastest way to view the issue id — is to mouse-over the Edit  button on the Issue page, that you wanted to view the issue id, and you can view the issue id at the bottom of browser as shown in the screenshot.}

Issue Key

ISSUE_KEY

String

Issue Key is a unique identifier which assigned to an issue when it is added or registered in Backlog.

Issue Type Id

ISSUE_TYPE_ID

Int64

Issue types distinguish different types of work in unique ways, and help you identify, categorize, and report on your team’s work and to build more structure into your working process. Here's a list of the default issue types that come with each Jira product: Task, Subtask, Epic, Bug, Story.

Issue Type Id is a numeric code which uniquely identifies an issue type.

^{To view the issue type id — hover your mouse cursor over the Edit operation link of an issue type in the Issues section on the Issue Types page in the Administration menu.}

Issue Type Name

ISSUE_CURRENT_TYPE_NAME

String

Issue Type Name is an identifying name of the Issue Type (Task, Subtask, Epic, Bug, Story).

^{Besides default issue types you have an opportunity to create your own ones, by clicking on the Add Issue Type button in the Issues field of Administration menu.}

Resolved

ISSUE_RESOLVED

DateTimeOffset

The resolved date equals to the date, when you set the Resolution field for the issue. You can not modify this field.

Resolution

ISSUE_RESOLUTION

String

The Resolution field is an indicator of that the lifecycle of an issue has come to an end. It specifies the reason an issue is closed.

Due Date

ISSUE_DUE_DATE

DateTimeOffset

Due date is a desired date requested by initiator (e.g. project team requests to execute something by X due date).

Description

ISSUE_DESCRIPTION

String

Description is a field that contains, literally, the description of the issue.

Current Status Id

ISSUE_CURRENT_STATUS_ID

String

Current Status Id is a numeric code that uniquely identifies issue workflow status applicable to the issue right now.

Current Status Name

ISSUE_CURRENT_STATUS_NAME

String

Issue Status Name(1) is an indicator of issue’s current place in the project's workflow(Open, In Progress, Reopened, Resolved, Closed, To Do, Done).

^{Besides default issue types you have an opportunity to create your own ones, by clicking on the Add Issue Type button in the Issues field of Administration menu.}

Current Status Category Name

ISSUE_CURRENT_STATUS_CATEGORY_NAME

String

The Status Category Name(2) represented on a Status are reflective of the Status Category and allows for a team to have the most clear description of current issues statuses.

^{You can find a Status panel on the Issues page in Administration menu.}

Status Changed Date

ISSUE_STATUS_CHANGE_DATE

DateTimeOffset

The Status Changed Date is an indicator of the last time the issue moved from one status in one category to another.

Current Assignee ID

ISSUE_CURRENT_ASSIGNEE_ID

Int64

Current Assignee Id is a person who has the responsibility either to resolve the issue, or to take the next action.

^{Id is a numeric character code which you can find in your BI account' oData tables.}

Current Assignee Name

ISSUE_CURRENT_ASSIGNEE_NAME

String

Current Assignee Name is a full name of assignee in Jira.

Current Assignee Key

ISSUE_CURRENT_ASSIGNEE_KEY

String

Current Assignee Key is a username of assignee, via they log in to Jira.

^{You can find it in user’s profile by hovering the mouse on the Assignee name and then choosing the Profile field in the popup menu.}

Reporter ID

ISSUE_REPORTER_ID

Int64

The Reporter is a field that you can set during the creation of the issue. Basically it is the one that wants something to be done. The default value will be the person who is creating the issue.

^{Id is a numeric character code which you can find in your BI account' oData tables.}

Reporter Name

ISSUE_REPORTER_NAME

String

The Reporter Name is a name of the person that is raising the issue.

^{The reporter will be updated on all changes that happens to the issue they have reported.}

Reporter Key

ISSUE_REPORTER_KEY

String

Reporter Key is a username of the person, via they log in to Jira.

^{You can find it in user’s profile by hovering the mouse on the Reporter name and then choosing the Profile field in the popup menu.}

Creator ID

ISSUE_CREATOR_ID

Int64

The Creator is the person who created the issue. 

^{Id is a numeric character code which you can find in your BI account' oData tables.}

Creator Name

ISSUE_CREATOR_NAME

String

The Creator Name is a name of the person who created the issue. 

^{You can find it in Search for Issues page.}

Creator Key

ISSUE_CREATOR_KEY

String

Creator Key is a username of the person, via they log in to Jira.

^{You can find it in user’s profile by clicking on the Creator name.}

Project Id

ISSUE_PROJECT_ID

Int64

Project Id is an alphanumeric character code, based on the passed project and version name.

^{You can find it in a few steps:}

• ^{Choose the the right project in the Projects menu(1).}

• ^{Click the Project settings(2).}

• ^{Hover the mouse on the Details field(3).}

• ^{You can see the Project Id number(4) in the lower left corner of the page in a pop-up window.}

Project Key

ISSUE_PROJECT_NAME

String

Project key is the prefix of the issue number, based on your project name, that describe to people across your Jira site that some issues are related to your project.

Priority

ISSUE_PRIORITY

String

Priority is a relative importance of an issue in relation to other issues for the team, so it helps your users determine which issues should be tackled first.

^{Divided into: Highest, High, Medium, Low, Lowest.}

Security Level

ISSUE_SECURITY_LEVEL

Int64

Issue Level Security allows for even more granular access to a projects issues. You can assign Roles, Custom Field Values, Project Roles, and Groups. This level is helpful for a Security, Business, or HR related project.

^{Issue Security Level is set within the Issue security schemes in the Administration panel.}

Created

ISSUE_CREATED

DateTimeOffset

Created is a field that shows the time of the issue creation.

Updated

ISSUE_UPDATED

Created is a field that shows the time when changes were made to the issue last time.

Last Viewed

ISSUE_LAST_VIEWED

DateTimeOffset

Search for issues that were last viewed on, before, or after a particular date (or date range).

^{Note that the search results will be relative to your configured time zone (which is by default the Jira server's time zone).}

_{You can find it in Search for issues page.}

Environment

ISSUE_ENVIRONMENT

String

The hardware or software environment to which the issue is related.

Summary

ISSUE_SUMMARY

String

A Summary is a short phrase to give you an idea of what the issue is about.

Time at Current Assignee in hours

ISSUE_TIME_WITH_CURRENT_ASSIGNEE_HOURS

Double

Time at Current Assignee are an indicators which represent, how much time/date an issue was present with the current assignee.

^{Time in hours can be retrieved from the Time in Status section}

^{Time in days can be retrieved from the Time With Assignee section}

_{You can find them in your BI account' oData tables.}

Time at Current Assignee in days, decimal

ISSUE_TIME_WITH_CURRENT_ASSIGNEE_DAYS

Double

Time at Current Assignee in days, rounded

ISSUE_TIME_WITH_CURRENT_ASSIGNEE_DAYS_ROUNDED

Int64

Watchers

ISSUE_WATCHERS

Int64

Watchers is a number, shown how many people have signed up for notifications of any updates relating to a particular issue.

Votes

ISSUE_VOTES

Int64

Votes is the number of "voicing", indicates how many users communicate that a particular issue is important.

Work Ratio

ISSUE_WORK_RATIO

Double

Work Ratio is a percentage time tracking field which calculated Ratio of total work done to the total amount of work.

^{You can find it in Search for issues page. If it is not there, select the Progress item in the Columns drop-down menu.}

Issue Comment

ISSUE_COMMENT

String

Issue Comment is a field at the bottom of the issue page of updates, that let watchers know what's happening on the issue, to code snippets, images, tables, and more. 

^{The editor converts things like links, code, and markdown on-the-fly, so you can paste in your content and let the editor do the work.}

Issue Effort

Time Spent

ISSUE_TIME_SPENT

Double

Time Spent is a field that records the time you spend working on a current issue.

^{You can enable this function by going to Administration Settings > Issues > Issue Features > Time tracking field.}

Time Spent Including Sub-Tasks

ISSUE_TIME_SPENT_WITH_ST

Double

This is a possibility to view the time, person spent on a current issue, including sub tasks linked to it.

^{Note that for this feature to work, the sub task must have its own estimate.}

Original Estimate

ISSUE_ORIGINAL_ESTIMATE

Double

Original Estimate is a preliminary estimate of the total amount of time the person plans to complete a current issue in.

^{It may include also an estimate for sub tasks.}

_{By default, this is specified in minutes, but you can use hours, days, or weeks, depending on your Jira system configuration.}

Original Estimate Including Sub-Tasks

ISSUE_ORIGINAL_ESTIMATE_WITH_ST

Double

Remaining Estimate

ISSUE_REMAINING_ESTIMATE

Double

Remaining Estimate is the remaining amount of time it would take to complete this issue.

^{It may include also an estimate for sub tasks.}

Remaining Estimate Including Sub-Tasks

ISSUE_REMAINING_ESTIMATE_WITH_ST

Double

Issue Worklogs

Worklog Issue Key / Issue Key

WORKLOG_KEY

String

Worklog Issue Key is an identifier of an issue the time was logged for.

Name

WORKLOG_NAME

String

Worklog Name is a name of a person who logged time on a current issue page.

User ID

WORKLOG_USER_ID

Int64

Worklog User ID is a numeric character code of a person who logged time on a current issue page.

^{You can find in your BI account' oData tables.}

User Key

WORKLOG_USERKEY

String

Worklog User Key is a randomly generated identifier of the user, which doesn’t contain any personal information for on the one hand — to comply the GDPR, and on the other hand — to give an Administrator the opportunity to track the time that a particular user, who changed his username, has logged.

^{In older versions of Jira, the key and username have the same value.}

_{You can find User Key in your BI account' oData tables.}

Date / Start Date

WORKLOG_WORKLOG_DATE

DateTimeOffset

Worklog Start Date is the point in time, when user started current unit of work.

Description

WORKLOG_DESCRIPTION

String

Worklog Description is a description related to the achieved work.

Creation Date / Created

WORKLOG_CREATION_DATE

DateTimeOffset

Worklog Creation Date is a time when achieved part of work was logged.

Logged Time

WORKLOG_LOGGED_TIME

Int64

Logged Time is the amount of time spent on the issue.

Issue Id

WORKLOG_ISSUE_ID

Int64

Worklog Issue Id is the internal ID of the logged issue which is internally used in Jira database to refer to the current log in the general worklog.

^{The fastest way to view it — is to mouse-over the Edit icon on the Logged work field.}

User is Active

WORKLOG_USER_IS_ACTIVE

Boolean

User is Active is an indicator which shows whether the current user has the "Jira Software Users"-, or the "Jira Administrators" permission.

Username / Author Name

WORKLOG_USERNAME

String

Worklog Username is a username of the person, who logged time on a current issue page.

^{You can find it in user’s profile by clicking on the User Key name.}

User Email

WORKLOG_USER_EMAIL

String

User Email is exactly the user's email in Jira.

^{JIRA can be configured to automatically generate issues or comments on existing issues based on received emails. In addition, any attachments in emails can be automatically attached to the issue. This can be useful when communicating with a customer or for receiving notifications about changes in a task, or also for support work.}

_{Can be retrieved from the Users section after clicking the User’s Name.}

User Timezone

WORKLOG_USER_TIMEZONE

String

User Timezone is a geographic region with the corresponding standard time in which the user works.

_{Can be retrieved from the Users section after clicking the User’s Name.}

Update Date / Updated

WORKLOG_UPDATE_DATE

DateTimeOffset

Worklog Update Date is a point in time when the description, date, time, hours worked, or remaining estimate of the issue were changed.

^{You can check it by hovering the mouse on Edited field.}

Billable Seconds

WORKLOG_BILLABLE_SECONDS

Int64

Billable Seconds are those seconds worked directly related to the client’s projects that they get bill for and pay it directly.

_{You can find them in your BI account' oData tables.}

Issue Statuses

Name / Issue Status Name

ISSUE_STATUS_NAME

String

Issue Status Name is an indicator of issue's current place in the project's workflow.

Sequence

ISSUE_STATUS_SEQUENCE

Int64

Issue Status Sequence is an issue number position in its wokflow.

^{You can check statuses order by clicking on the View Workflow icon.}

_{If you have a large amount of statuses with a lot of connections between them, and need to know a number of each other —}

Description

ISSUE_STATUS_DESCRIPTION

String

Issue Status Description is a description of status properties.

^{The fastest way to view it — is to mouse-over the Status icon.}

Icon URL

ISSUE_STATUS_ICON_URL

String

Issue Status Icon URL is the address of a given icon on the Web.

Status Category / Category

ISSUE_STATUS_CATEGORY

Int64

Issue Status Category is an identifier of a logical group to which current status could be sent into: To Do (grey), In Progress (blue) or Done (green).

^{Status Categories placed into Issue Statuses menu on the Administration panel.}

Issue Status ID

Id

String

Issue Status Id is an alphanumeric character code uniquely identifies issue workflow statuses.

^{The fastest way to view the status id — is to mouse-over the View Workflow  field on the Issue page, that you wanted to view the id, and you can view the status id at the bottom of browser as shown in the screenshot.}

Issue Types

Name / Issue Type Name

ISSUE_TYPE_NAME

String

Issue Type Name is an identifying name of the Issue Type (Task, Subtask, Epic, Bug, Story).

^{Besides default issue types you have an opportunity to create your own ones, by clicking on the Add Issue Type button in the Issues field of Administration menu.}

Sequence

ISSUE_TYPE_SEQUENCE

Int64

Issue Type Sequence is a position number of available issue types in a current project.

^{You can find Issue Type Sequence in your BI account' oData tables.}

Description

ISSUE_TYPE_DESCRIPTION

String

Issue Type Description is a specification that distinguish different types of work in unique ways, and help you identify, categorize, and report on your team’s work across your Jira site.

^{To get acquainted with them at the Administration menu' Issue types section.}

Issue Links

Linked Issues

LINKID_ISSUES_ISSUES

String

Linked Issue is the key of an issue to which the link was made.

Link Type / Type

LINKID_ISSUES_LINK_TYPE

String

Link Type is a type of an association between issues on either the same or different Jira servers.

^{Default types of links:}

• ^{relates to / relates to}

• ^{duplicates / is duplicated by}

• ^{blocks / is blocked by}

• ^{clones / is cloned by}

_{You are able to add, edit or delete your own link types.}

Linked Issue Key

LINKID_ISSUES_ISSUE_KEY

String

Link Direction is the key of a linked issue.

Link Direction/ Direction

LINKID_ISSUES_DIRECTION

String

Link Direction is a type of direction attribute: inward (_{describes the issue that was acted upon: blocked by, cloned by, duplicated by, related to, and resolved by etc.}) or outward (_{meaning the source issue is taking action on the destination issue: block, clone, duplicate, relate, resolve etc.}).

Issue Attachments

Attachment Issue Key / Issue Key

ATTACHMENT_ISSUE_KEY

String

Attachment Issue Key is a key of an issue which contains attachments.

Attachment Issue Id / Issue ID

ATTACHMENT_ISSUE_ID

Int64

Attachment Issue ID is the internal ID of the Jira issue with attachments, which is internally used in Jira database to refer to an issue.

^{This is the unique ID for a Jira issue and does not change.}

_{The fastest way to view the Attachment issue id — is to mouse-over the Edit  button on the Issue page, that you wanted to view the issue id, and you can view the issue id at the bottom of browser as shown in the screenshot.}

Attachment FileName

ATTACHMENT_FILENAME

String

Attachment File Name is literally a name of the attached file.

Attachment FileSize

ATTACHMENT_ILESIZE

Int64

Attachment File Name is the measure of space a file takes up on a storage medium.

Attachment MimeType

ATTACHMENT_MIMETYPE

String

Attachment MIME type is an identifier of content that is being sent type, and can determine how that data is transferred.

Attachment Is ZIP

ATTACHMENT_IS_ZIP

Boolean

Attachment Is ZIP is an identifier whether a sent content has been convert to the appropriate format.

Attachment Date Created

ATTACHMENT_DATE_CREATED

DateTimeOffset

Attachment Date Created is an identifier of time when file was sent.

Attachment User Key / Author ID

ATTACHMENT_USER_KEY

String

Worklog User Key is a randomly generated identifier of the user.

^{In older versions of Jira, the key and username have the same value.}

_{You can find User Key in your BI account' oData tables.}

Attachment User Name / Author Name

ATTACHMENT_USER_NAME

String

Attachment User Name is a name of the user who attached the file.

^{The fastest way to view it — is to mouse-over the attachment area.}

Issue Remote Links

Issue Id

REMOTE_LINK_ISSUE_ID

Int64

Issue Id is the internal ID of the Jira issue which contains links to information in other systems.

Issue Key

REMOTE_LINK_ISSUE_KEY

String

Issue Id is a unique identifier of the Jira issue which contains remote links.

Title

REMOTE_LINK_TITLE

String

Title is a displayed name of remote links.

URL

REMOTE_LINK_URL

String

URL is a web address to the object in the remote system.

^{The fastest way to view it — is to mouse-over the link name area.}

Summary

REMOTE_LINK_SUMMARY

String

Summary is a short description of the remote object essence in Jira.

^{It is displayed as a comment. But note, that it is better to duplicate link name in the summary, so as not to lose it among the rest comments.}

Icon URL

REMOTE_LINK_ICON_URL

String

Icon URL is the address of a given quickly identifier that represents the remote link via image.

Icon Title

REMOTE_LINK_ICON_TITLE

String

Icon Title is a name of icon which reflects the remote link essence.

Resolved

REMOTE_LINK_RESOLVED

Double

Resolved is a value that identifies whether the remote object i resolved (if it is, for example, an issue, support ticket, and so on).

^{It will not make sense for things like Wiki pages.}

Application Type

REMOTE_LINK_APPLICATION_TYPE

String

Application Type is a name-spaced type of the application.

Application Name

REMOTE_LINK_APPLICATION_NAME

String

Application Name is a name of the remote application instance that stores the remote object. 

Relationship

REMOTE_LINK_RELATIONSHIP

String

Relationship is a relationship pointer between the remote object and the Jira issue.

^{This can be a verb or a noun, in instance "links to".}

Status Name

REMOTE_LINK_STATUS_NAME

String

Status Name is a name of the remote object status.

^{You can view it by clicking on the remote object link or find it in your BI account' oData tables.}

Status Description

REMOTE_LINK_STATUS_DESCRIPTION

String

Status Description is a textual description of the remote object status.

^{You can view it by clicking on the remote object link or find it in your BI account' oData tables.}

Issue Labels

Labels Issue Key / Issue Key

LABEL_ISSUE_REY

String

Label Issue Key is a key of an issue which contains label.

Labels Issue Id / Issue Id

LABEL_ISSUE_ID

Int64

Labels Issue ID is the internal ID of the Jira issue with labels, which is internally used in Jira database to refer to an issue.

^{The fastest way to view it — is to mouse-over the Edit  button on the Issue page, that you wanted to view the issue id, and you can view the issue id at the bottom of browser as shown in the screenshot.}

Labels Name / Name

LABEL_NAME

String

Labels Name is a title of some sort of hashtag, assigned to an issue, so that the respective tasks can be found more easily using this filter.

Issue Comments

Issue Id

COMMENT_ISSUE_ID

String

Comment Issue ID is the internal ID of the Jira issue with comments, which is internally used in Jira database to refer to an issue.

^{The fastest way to view the comment issue id — is to mouse-over the Edit  button on the Issue page, that you wanted to view the issue id, and you can view the issue id at the bottom of browser as shown in the screenshot.}

Issue Key

COMMENT_ISSUE_KEY

Int64

Comment Issue Key is a key of an issue which contains comments.

Comment

COMMENT

String

Comment is a message related to a current issue that let watchers know what's happening on the issue, to code snippets, images, tables, and more. The editor converts things like links, code, and markdown on-the-fly, so you can paste in your content and let the editor do the work.

Created

COMMENT_CREATED

DateTimeOffset

Comment Date Created is an identifier of time when comment was sent.

Author Key / Author ID

COMMENT_AUTHOR_KEY

String

Comment Author Key is a randomly generated identifier of the user.

_{You can find User Key in your BI account' oData tables.}

Author Name

COMMENT_AUTHOR_NAME

String

Comment Author Name is a name of the user who has left the comment.

Parent Issues

Issue Key

ISSUE_KEY

String

Issue Key is a key of a child issue.

^{Its also possible to view it from the parent issue by mouse-overing the name of sub task — the issue’s id appears at the bottom of browser as shown in the screenshot.}

Parent Issue Key

ISSUE_PARENT_ISSUE_KEY

String

Issue Key is a key of an issue to which the sub task is linked.

Parent Issue Status Id / Parent Issue Id

ISSUE_PARENT_ISSUE_STATUS_ID

String

Parent Issue ID is the internal ID of the Jira issue with sub task, which is internally used in Jira database to refer to an issue. To find it you should go to the Parent task by clicking on its summary.

^{The fastest way to view the parent issue id — is to mouse-over the Edit  button on the Parent Issue page, and you can view the issue id at the bottom of browser as shown in the screenshot.}

Parent Issue Status Name

ISSUE_PARENT_ISSUE_STATUS_NAME

String

Parent Issue Status Name is an indicator of parent issue's current place in the project's workflow.

Parent Issue Status Category Name

ISSUE_PARENT_ISSUE_STATUS_CATEGORY_NAME

String

Parent Status Category Name is a reflection of the Status Category and allows for a team to have the most clear description of current issues statuses.

Parent Issue Type Id

ISSUE_PARENT_ISSUE_TYPE_ID

String

Parent Issue Type Id is an alphanumeric character code uniquely identifies an issue of a company.

^{To view the issue type id — hover your mouse cursor over the Edit operation link of an issue type in the Issues section on the Issue Types page in the Administration menu.}

Parent Issue Type Name

ISSUE_PARENT_ISSUE_TYPE_NAME

String

Parent Issue Type Name is an identifying name of the Issue Type.

^{Besides default issue types you have an opportunity to create your own ones, by clicking on the Add Issue Type button in the Issues field of Administration menu.}

Parent Issue Summary

ISSUE_PARENT_ISSUE_SUMMARY

String

A Summary is what the issue is about, a short phrase to give you an idea of what the issue is about

Parent Issue Priority

ISSUE_PARENT_ISSUE_PRIORITY

String

Parent Issue Priority is a relative importance of an issue in relation to other issues for the team, so it helps your users determine which issues should be tackled first.

Sub-Tasks

Issue Key

SUBTASKS_ISSUE_KEY

String

Issue Key is a key of a child issue which is linked to the parent one.

^{Its also possible to view it from. the parent issue by mouse-overing the name of sub task — the issue’s id appears at the bottom of browser as shown in the screenshot.}

Sub-Tasks

SUBTASKS_SUBTASKS

String

Sub-Tasks is a list of sub tasks related to the current parent issue.

Histories

History Field / Field

HISTORY_FIELD

String

History Field is an instance with the record of all the activities performed on issues, where user can view information about changes, which is:

• User name who made the changes.

• Time while the changes was made.

• If an issue field is changed, new and old values of that field.

History Author

HISTORY_AUTHOR

String

History Author is a user name who made the changes

History New Value / New Value

HISTORY_NEW_VALUE

String

History New Value is a new value of issue field that had been changed.

History Old Value / Old Value

HISTORY_OLD_VALUE

String

History Old Value is an original value of issue field that had been changed.

History New Value Name / New Value Formatted

HISTORY_NEW_VALUE_NAME

String

History New Value Name is a summary of new value issue field that was changed.

History Old Value Name / Old Value Formatted

HISTORY_OLD_VALUE_NAME

String

History Old Value Name is a summary of original value issue field that was changed.

History Issue Key / Issue Key

HISTORY_ISSUE_KEY

String

History Issue Key is a key of an issue which history is being viewed.

History Issue Id / Issue Id

HISTORY_ISSUE_ID

Int64

History Issue ID is the internal ID of the Jira issue with sub task, which is internally used in Jira database to refer to an issue which history is being viewed.

^{The fastest way to view the history issue id — is to mouse-over the Edit  button on the Issue page, and you can view the issue id at the bottom of browser as shown in the screenshot.}

History Created / Created

HISTORY_CREATED

DateTimeOffset

History Created is an identifier of time when change was done.

Time in Statuses

History Status

ISTORY_STATUS

String

History Status is a counter of status transitions in the issue history.

Time in Status in hours / Duration in 24/7

TIME_IN_STATUS_HOURS

Double

Time in Status is a time indicator that allows you to see how much time each issue spent in each status.

Time in Status in days

TIME_IN_STATUS_DAYS

Time in Status in business hours

TIME_IN_STATUS_BUSINESS_HOURS

Time in Status in business days / Duration in Business Days (24/5)

TIME_IN_STATUS_BUSINESS_DAYS

Status Start

STATUS_START

DateTimeOffset

Status Start is a value which indicates the date when status was assigned to an issue.

Status End

STATUS_END

DateTimeOffset

Status End is a value which shows the date when issue was resolved from current status.

Time at Assignee / Time With Assignee

Assigned person / User Name

ASSIGNED_PERSON

String

Username is a full name of the assigned person, via they log in in Jira.

^{You can find it in user’s profile.}

Time at Assignee in hours / Duration in 24/7

TIME_WITH_ASSIGNEE_HOURS

Double

Time at Assignee is amount of time that person was assigned to the issue in general.

Time at Assignee in days

TIME_WITH_ASSIGNEE_DAYS

Time at Assignee in business hours

TIME_WITH_ASSIGNEE_BUSINESS_HOURS

Business Time at Assignee is amount of time that person was assigned to the issue related to the business time (most often 1 business day = 8 hours, so the working hours in this case will be those that fit in current range)

Time at Assignee in business days / Duration in Business Days (24/5)

TIME_WITH_ASSIGNEE_BUSINESS_DAYS

Assignee Start

ASSIGNEE_START

DateTimeOffset

Assignee Start is a date when the issue was assigned to the person.

Assignee End

ASSIGNEE_END

DateTimeOffset

Assignee End is a date when the person was unassigned from the issue.

Assignee Sequence

ASSIGNEE_SEQUENCE

Int64

Assignee Sequence is a number that represents the order of the user assigned to the issue.

Assignee With Sequence

ASSIGNEE_WITH_SEQUENCE

String

Assignee With Sequence is a combination of ‘Assignee With Sequence’ and the user name.

Is Current Assignee

ASSIGNEE_IS_CURRENT

Boolean

Is Current Assignee is an identifier whether the Assignee is still assigned to the issue.

Projects

Project Lead / Project Lead ID

PROJECT_LEAD

Int64

Project Lead ID is the full name of person running or owning the project in Jira.

^{You can find it choosing All projects page from Projects menu.}

Project Lead Name

PROJECT_LEAD_NAME

String

Project Lead Name is a username of person who leads the project, via they log in to Jira.

Project Lead Email

PROJECT_LEAD_EMAIL

String

Project Lead Email is Email of the user who leads the project.

^{The fastest way to view the issue id — is to mouse-over the Project Lead Name.}

Project Category / Category

PROJECT_CATEGORY

String

Project Category is a classification option for projects based on the purpose for which they were created, enabling you to define and locate groups of projects.

Project Name / Name

PROJECT_NAME

String

Project Name is an identifying name of the project.

Project Key

PROJECT_KEY

String

Project key is the prefix of the issue number, based on your project name, that describe to people across your Jira site that some issues are related to your project.

Project Description / Description

PROJECT_DESCRIPTION

String

Project Description is a brief, detailed explanation of the project.

^{Project descriptions are only available in company-managed projects.}

^{You can view Project description on the Project page, just if you previously have enabled this option at the System preferences in Administration menu.}

_Also

Project Type / Type

PROJECT_TYPE

String

Project Type is a team or department’s workspace at the group level with specific features for each type.

Permission Scheme ID

PROJECT_PERMISSION_SCHEME_ID

Int64

Permission Scheme ID is the internal ID of the Jira set of users groups or project roles assignments for the project permissions, which is internally used in Jira database to refer what number of users are able to do with projects.

Permission Scheme Name

PROJECT_PERMISSION_SCHEME__NAME

String

Permission Scheme Name is a summary of Jira set of users groups or project roles assignments for the project permissions.

Fix Versions / Versions + Issue Fix Versions

Fix Version Issue Key / Issue Key

FIX_VERSION_ISSUE_KEY

String

Issue Key is a unique identifier of an issue that is created to serve different client needs and which refers to the fix version.

_{You can check it at the Releases page after clicking on the release version name.}

Fix Version Issue Id / Issue Id

FIX_VERSION_ISSUE_ID

Int64

Issue Id is the internal ID of the issue which refers to the fix version.

_{You can check it at the issue page after clicking on the issue field in the Releases page.}

Fix Version Archived / Is Archived?

FIX_VERSION_ARCHIVED

Double

Fix Version Archived is an indicator which shows whether the current version is hide rom the Change Log reports, and in the Jira User Interface.

Fix Version Description / Description

FIX_VERSION_DESCRIPTION

Int64

Fix version Description is a description of the release version used to track different software developments and/or any updates.

Fix Version Name / Version Name

FIX_VERSION_NAME

String

Fix Version Name is a name of the version which was designed to help each development team and product owner track all code to be released at one time. 

Fix Version Release Date / Release Date

FIX_VERSION_RELEASE_DATE

DateTimeOffset

Release Date is an indicator of the date the version was fixed.

Fix Version Start Date / Start Date

FIX_VERSION_START_DATE

DateTimeOffset

Start Date is a scheduled point in time when Fix Version is planned to be released.

Fix Version Released / Is Released?

FIX_VERSION_RELEASED

Double

Fix Version Released is an indicator which shows whether the current version is rolled out.

Affect Versions / Issue Affect Versions

Affects Version Issue Key / Issue Key

AFFECTS_VERSION_ISSUE_KEY

String

Affects version Issue Key is a unique identifier of an issue which refers to the version in which a bug or problem in already-released code was found.

_{You can check it at the Releases page after clicking on the release version name.}

Affects Version Issue Id / Issue Id

AFFECTS_VERSION_ISSUE_ID

Int64

Issue Id is the internal ID of the issue which affect version is viewed.

_{You can check it at the issue page after clicking on the issue field in the releases page.}

Affects Version Name / Version Name

AFFECTS_VERSION_NAME

String

Version Name typically numeric name of each affect version, which represent points-in-time for a project, for example, 1.0 or 2.1.1.

Components / Project Components

Component Name

COMPONENT_NAME

String

Component Name is a name of generic containers for issues that add some structure to projects, breaking them up into features, teams, modules, subprojects, etc.

^{Component name is enabled to view in the Search for issues menu.}

Component Issue Id

COMPONENT_ISSUE_ID

Int64

Component Issue Id is a numeric character code of those issue which is a part of viewing component.

^{It can be shown when clicking at the issue key in the Search for issues menu, and then — mouse-overing the Edit button on the Issue page.}

Component Description / Description

COMPONENT_DESCRIPTION

String

Component Description is a description of the component, revealing its purpose.

Component Lead / Lead Name

COMPONENT_LEAD

String

Lead Name is a name of the person who is automatically assigned issues with that component.

Component Lead Id / Lead Id

COMPONENT_LEAD_ID

Int64

Lead Id is a numeric character code of those who leads the component.

Component Issue Key

COMPONENT_ISSUE_KEY

String

Component Issue Key is a unique identifier of an issue which belongs to current component.

Jira Groups

Group Name

JIRA_GROUP_NAME

String

Group Name is a name of multiple users bunch within your instance that have the same application permissions.

^{You can only find a desired group name if you have an administrator permission, in a User management section.}

_{You can also check it in your BI account' oData tables.}

Member User Key

JIRA_GROUPS_MEMBER_USER_KEY

String

Member User Key is an alphanumeric character code of a user.

Member Username

JIRA_GROUPS_MEMBER_USER_NAME

String

User Username is a username of the person, via they log in in Jira.

^{You can only find a desired group name if you have an administrator permission, in a User management section.}

_{You can also check it in your BI account' oData tables.}

Users

User Key/ User ID

USER_KEY

String

User ID is an alphanumeric character code of a user.

User Name

USER_NAME

String

Username is a full name of the person, via they log in in Jira.

^{You can find it in user’s profile.}

User Is Active / Is Active?

USER_ACTIVE

Double

User is Active is an indicator which shows whether the current user has access to current Jira Software area.

User TimeZone / Timezone

USER_TIMEZONE

String

User Timezone is a geographic region with the corresponding standard time in which the user works.

_{Can be retrieved from the Users section after clicking the User’s Name.}

User Email / Email

USER_EMAIL

String

User Email is exactly the user's email in Jira.

_{Can be retrieved from the Users section after clicking the User’s Name.}

User Username

USER_USERNAME

String

User Username is a username of the person, via they log in in Jira.

^{You can find it in user’s profile.}

User Last Login

USER_LAST_LOGIN

DateTimeOffset

User Last Login is an indicator of the last date the user logged into the account.

^{You can find it in user’s profile.}

Created At

USER_CREATED_DATE

DateTimeOffset

Created At is a date of user’s account creation.