Nasdanika
Issue
Issue is a unit of work to accomplish to achieve a desired outcome on its containing engineered element, e.g.:
- New functionality in a module,
- New or refined persona goals,
- New skills acquired by an engineer,
- Improved organization processes.
Issue(s) can:
- Be assigned to an engineer,
- Be planned for an increment or release; It is possible to plan for both increment and release, e.g. May increment and release planned for June increment,
- Contribute to features,
- Have zero or more issue categories
- Be in one issue status,
- Have priority and severity,
- Be organized in a hierarchy (WBS),
- Require capabilities to become workable, e.g. another issue to be completed, or a release to be available.
- Be aligned to aims, e.g principles or key results of objectives,
- Specify effort and cost required to be completed.
Issue progress is tracked using notes. Notes are also used for discussions and tracking of issue-related decisions.
Supertypes
Subtypes
Referrers
cost : EDoubleMonetary cost for this issue, e.g. cost of materials.
| Type | EDouble |
|---|---|
| Cardinality | 0..1 |
| Changeable | true |
| Derived | false |
Effort for this issue.
| Type | EDouble |
|---|---|
| Cardinality | 0..1 |
| Changeable | true |
| Derived | false |
Remaining cost is computed from issue cost and notes cost or remaining cost.
| Type | EDouble |
|---|---|
| Cardinality | 0..1 |
| Changeable | false |
| Derived | true |
Remaining effort is computed from issue effort and notes effort or remaining effort.
| Type | EDouble |
|---|---|
| Cardinality | 0..1 |
| Changeable | false |
| Derived | true |
Issue is workable if it doesn’t have any unavailable required capabilities.
| Type | EBoolean |
|---|---|
| Cardinality | 0..1 |
| Changeable | false |
| Derived | true |
categories : IssueCategory*Issue category.
| Type | IssueCategory |
|---|---|
| Cardinality | 0..* |
| Changeable | true |
| Derived | false |
| Opposite | issues |
Issues can be infinitely nested to form a Work Breakdown Structure.
| Type | Issue |
|---|---|
| Cardinality | 0..* |
| Changeable | true |
| Derived | false |
| Key | path |
Increment for which this issue is directly scheduled. Issue can be scheduled for an increment directly or indirectly via features and releases. Release increment can be different from issue incrmenent. E.g. issue can be scheduled for May, but its release might be scheduled for July.
| Type | Increment |
|---|---|
| Cardinality | 0..1 |
| Changeable | true |
| Derived | false |
| Opposite | issues |
Issue notes are used for discussion and to record progress, remaining effort, and issue status if it is not set at the issue level.
| Type | Note |
|---|---|
| Cardinality | 0..* |
| Changeable | true |
| Derived | false |
| Key | path |
Issue status.
| Type | IssuePriority |
|---|---|
| Cardinality | 0..1 |
| Changeable | true |
| Derived | false |
| Opposite | issues |
Capabilities required to start working on an issue.
| Type | Capability |
|---|---|
| Cardinality | 0..* |
| Changeable | true |
| Derived | false |
| Opposite | requiredBy |
Issue status.
| Type | IssueSeverity |
|---|---|
| Cardinality | 0..1 |
| Changeable | true |
| Derived | false |
| Opposite | issues |
Issue status.
| Type | IssueStatus |
|---|---|
| Cardinality | 0..1 |
| Changeable | true |
| Derived | false |
| Opposite | issues |
Target element for this issue - container of the issue itself or the root issue in the issue hierarchy.
| Type | EngineeredElement |
|---|---|
| Cardinality | 0..1 |
| Changeable | false |
| Derived | true |