-
Notifications
You must be signed in to change notification settings - Fork 0
Issues
Tomas Stenlund edited this page Jun 29, 2022
·
4 revisions
An issue is a task of some sort that can be prioritized in backlogs, It also has a hierarchy and can have a relation to user needs and requirements.
Name | Type | Value Set | Description |
---|---|---|---|
id | string | alfanumeric | The identity of the issue, typical derived from the product and a running number |
name | string | alfanumeric | The name of the issue |
description | string | alfanumeric | A description of the issue |
priority | string | alfanumeric | The priority of the issue |
child | IssueRelation[] | GUID | A list of children for this issue |
type | UserNeed[] | GUID | The type of the issue, e.g. task, incident, etc. |
state | Requirement[] | GUID | The current state of the issue |
An issue can have a relation to another issue, user need or requirement. This object describes the type of relation.
Name | Type | Value Set | Description |
---|---|---|---|
version | string | alfanumeric | The version of the product, or release of a product |
relationType | RelationType | GUID | The type of the relation |
any | Any | GUID | The referenced object |
The type of relations an issue can have with another issue, user need or requirement.
Name | Type | Value Set | Description |
---|---|---|---|
name | string | alfanumeric | The name of the type of relation |
It can have the following values, that are set at install time:
Name | Description |
---|---|
implements | Usually a relation to a requirement |
supports | Usually a relation to a user need |
requires | Usually a relation to an issue |