JIRA uses Entity Engine module of the OfBiz suite to communicate with the database. You can learn more about the Entity Engine by reading its online documentation.

The database schema is described in the entitymodel.xml found in the WEB-INF/classes/entitydefs directory under the JIRA web application. The entitymodel.xml file has an XML definition of all JIRA's database tables, table columns and their data type. Some of the relationships between tables also appear in the file.

If you are using JIRA's API you will notice that a lot of code deals with GenericValue objects. The GenericValue is an OfBiz entity engine object. Each GenericValue object represents a record in the database.

To get a value of a field from a GenericValue you will need to use the relevant getter method for the field's type. For example:

GenericValue project = ...
String name = project.getString("name");
Long id = project.getLong("id");

The list of valid fields for each entity can be obtained by looking the entity's definition in the WEB-INF/classes/entitydefs/entitymodel.xml file. For the above example, one needs to look at the "Project" entity.

Relationships between tables

Some of the relationships between JIRA's tables in the database are documented below:

Issue Fields

カスタム フィールド

Change History

作業ログ

Work log entries are kept in the worklog table. For instance, some worklogs in JIRA (from JRA-10393):

are stored in worklog table as:

ここで:

• issueid maps to jiraissue.id
• timeworked is in seconds

Whenever a worklog entry is added, the jiraissue.timespent and jiraissue.timeestimate values are incremented and decremented respectively.

ユーザーとグループ

Issue status and workflow

Example SQLs

Some examples of SQLs that can be run against the JIRA schema:
Example SQL queries for JIRA