Jira Schema Support
This class represent any issue, story, task, epic
Metaclass: Issue
Is Abstract: No
Extends:
Description: This class represents issue.
Property Name | Data Type | Enum | Req’d | R/O | Description |
|---|---|---|---|---|---|
id | String | no | yes | no | Identifier if the issue, eg: 1230 |
self | String | no | yes | no | Direct url to the issue. |
key | String | no | yes | no | Identifier if the issue, eg: ABC-01 |
assignee | String | no | no | no | User ID of the assignee |
creator | String | no | no | no | User ID of the Creator |
description | Html | no | no | no | Description of the issue |
issueType | String | no | yes | no | Type – Story, Task, Bug, Epic |
priority | String | no | no | no | Priority of the issue. Eg: Medium, High, Low |
labels | String Array | no | no | no | Labels on the issue. |
reporter | String | no | no | no | User ID of the Reporter of the issue |
status | String | no | no | no | Current status of the issue. Eg: TODO, Working |
summary | String | no | yes | no | Issue Summary (Issue title) |
timeSpent | Integer | no | no | no | Total time spent on the issue |
projectID | String | no | no | no | Identifier of the Project |
projectName | String | no | yes | no | Name of the Project |
timeOriginalEstimate | Integer | no | no | no | The original estimate of the total amount of time it would take to complete the issue. |
aggregateTimeSpent | Integer | no | no | no | Time spent on the issue. |
timeEstimate | Integer | no | no | no | The current estimate of the remaining amount of time it would take to complete the issue. |
resolution | String | no | no | no | It specifies the reason an issue is closed. |
created | Date | no | no | no | Issue created date. |
updated | Date | no | no | no | Issue updated date. |
dueDate | Date | no | no | no | Issue due date. |
parentID | String | no | no | no | ID of the parent Issue. |
asotUri | String | no | yes | Yes | Direct uri to Jira Issue |
Note: Jira needs the highlighted properties in the table above mapped before subscribing to models from other systems.
The Issue Type is published as a STEREOTYPE shape, eg: A Story will be a combination of shapeId Issue with type METACLASS and shapeId Story and type STEREOTYPE
Locator
Name | Description |
|---|---|
| This is the API id of the issue |
Epic Properties
The fields Epic Name and Epic Link should be available on both the create and update issue screens.
Custom Properties :
Jira Adapter supports following type of custom properties.
Type |
|---|
Number Field |
Text Field |
URL Field |
Labels |
Checkboxes |
Multiple Select |
Radio Buttons |
Single Select |
Cascading Select |
Date Picker |
Date Time Picker |
Date and Datetime format are by default in GMT format.
Links:
There are 2 relations on issue, that needs to be mapped.
Relation Name | Type | Mult. | Description |
|---|---|---|---|
ChildOf | ASSOCIATION | 0..1 | Points to the parent of an Issue |
Any other relations are published with their respective
relation name.