An Issue in the Gropius system. Issues can be used to report bugs, request features, ask questions, ... Issues are synced to all IMSProjects of Trackables they are part of. All changes to the Issue are reflected by the timeline. READ is granted if READ is granted on any Trackable in `trackables`. Caution: due to confidentiality reasons, updates to `incomingRelations` do not cause updates on `lastModifiedBy` and `participants`, however, `lastModifiedAt` and `lastUpdatedAt` is still changed. The same applies to RelatedByIssueEvent, RemovedIncomingRelationEvent and IncomingRelationTypeChangedEvent.
Constructors
Properties
Entities which are in some regard affected by this Issue.
AggregatedIssues which aggregate this Issue.
Current Assignments to this Issue. For the history, see timelineItems.
The DateTime this entity was created at.
Current IssueRelations which have this Issue as end point.
Comments on the Issue, subset of the timeline.
The DateTime this entity was last modified at.
The User who last modified this entity.
The DateTime when the Issue was last updated, this includes a changed timeline.
Version used for optimistic locking
Current IssueRelations which have this Issue as start point.
Users who participated on the Issue, e.g. commented, added Labels, ...
The priority of the Issue, e.g. HIGH. Allowed IssuePriorities are defined by the template.
The state of the Issue, e.g. OPEN. Allowed IssueStates are defined by the template. The state also defines if this Issue is considered open or closed.
Template associated with the TemplatedNode
The values for all templated fields. The schema is defined by the Template of this node
Timeline of the Issue, shows how the Issue changed over time.
Trackables this Issue is part of.
Functions
Dummy function to avoid GraphQL kotlin optimization weirdness
Value of a field defined by the template. Error if such a field is not defined.