AGILE_DATA_BACKLOG_CONFIG
Note: All the tables prefixed with AGILE_DATA store data of agile projects that are running in the agile tools such as OpenText Software Delivery Management and Atlassian JIRA.
This table stores the configuration information of agile project backlog items (such as story, bug, feature, and epic).
Foreign Keys
There are no foreign keys for this table.
Column Descriptions
Column Name |
Null? |
Data Type |
Description |
---|---|---|---|
CONFIG_ID | NOT NULL | NUMBER (19) | Configuration identifier |
INSTANCE_ID | NULLABLE | VARCHAR2 (100) | Instance identifier |
COLOR | NULLABLE | VARCHAR2 (10) | Color for the backlog status |
BACKLOG_TYPE | NULLABLE | VARCHAR2 (100) | Backlog type, such as user story, defect, and epic |
BACKLOG_STATUS | NULLABLE | VARCHAR2 (100) | Backlog status, such as to so, in progress, and done |
IS_FINISH_STATUS | NULLABLE | NUMBER(1) |
Flag whether or not the backlog status is finish status. 1 means yes; 0 means no. |
CREATION_DATE | NULLABLE | DATE | Date when the configuration record is created |
CREATED_BY | NULLABLE | NUMBER(9) | Identifier for the user who created the configuration |
LAST_UPDATE_DATE | NULLABLE | DATE | Date when the configuration record is last updated |
LAST_UPDATED_BY | NULLABLE | NUMBER(9) | Identifier for the user who last updated the configuration record |
VERSION | NULLABLE | NUMBER(9) | System-generated version for the entity. This column must not be updated manually. |
Indexes
Index Name | Index Type | Sequence | Column Name |
---|---|---|---|
PK_AGILE_DATA_BACKLOG_CONFIG | UNIQUE | 1 | CONFIG_ID |