Types
Entities that can be affected by an Issue, meaning that this entity is in some regard impacted by e.g. a bug described by an issue, or the non-present of a feature described by an issue.
Entity which represents a software component, e.g. a library, a microservice, or a deployment platform, .... The type of software component is defined by the template. Can have issues, labels and artefacts as this is a Trackable. Defines InterfaceSpecifications, but visible/invisible InterfaceSpecificationVersions depend on the ComponentVersion. Can be affected by Issues. READ is granted via an associated ComponentPermission or if READ is granted on any Project including any ComponentVersion in `versions` of this Component.
Version of a component. Can specifies visible/invisible InterfaceSpecifications. Can be used in Relations, affected by issues and included by Projects. READ is granted if READ is granted on `component`.
Entity which represents an issue management system (like GitHub, Jira, Redmine, ...). Trackables can be added to this via an IMSProject, so that their issues are synced to this IMS. READ is granted via an associated IMSPermission.
Issue on an IMS, represents an Issue synced to an IMS. The representation of the Issue on the IMS depends on the type of IMS. READ is granted if read is granted on `issue`.
Project on an IMS, represents a Trackable synced to an IMS. The representation on the IMS depends on the type of IMS, e.g. for GitHub, a project is a repository. READ is granted if READ is granted on `trackable` or `ims`.
An interface which is part of a specific ComponentVersion. Its semantics depend on the InterfaceSpecification it is specified by, e.g. an Interface can represent a REST API. Can be used in Relations and affected by Issues. READ is granted if READ is granted on `interfaceDefinition`.
InterfaceDefinition on a ComponentVersion Specifies if it is visible/invisible self-defined. Specifies if it is visible/invisible derived (and by which Relations) READ is granted if READ is granted on `componentVersion`
Part of an Interface(Specification). Its semantics depend on the InterfaceSpecification, e.g. for a REST API interface, this could represent a single endpoint of the API. Relations can specify for both start and end included InterfaceParts. Can be affected by Issues, and be used as start / end of ServiceEffectSpecifications. READ is granted if READ is granted on `definedOn`.
Specification of an Interface. Defined on a Component, but can be visible and invisible on different ComponentVersions. Can be affected by Issues, and be used as start / end of ServiceEffectSpecifications. Defines InterfaceParts, but active parts depend on the InterfaceSpecificationVersion. READ is granted if READ is granted on `component`, or any InterfaceSpecificationVersion in `versions`.
A specific version of an InterfaceSpecification. Defines which InterfaceParts are active. Can be both visible (generates an Interface) and invisible (does not generate an Interface) on different Components. Can be derived by Relations, and affected by Issues. READ is granted if READ is granted on `interfaceSpecification`, or any InterfaceDefinition in `definitions`
Participant of a a IntraComponentDependencySpecification Consists of an Interface it refers to, and optionally a subset of its active InterfaceParts. READ is granted if READ is granted on the associated ComponentVersion
Describes a dependency between Interfaces of a Component. Both ends can optionally affected InterfaceParts. Semantically, any InterfaceSpecification(Version) in `outgoing` depends on any InterfaceSpecification(Version) in `incoming`. This can result in a propagation of Issues, if any location in `in` is in some regard affected by an Issue, all locations in `out` are affected by this Issue, too.
Affected by issue with a name and description
A project of the Gropius system. Consists of a set of ComponentVersions, which form a graph with the Relations between them. Can be affected by issues. Can have issues, labels and artefacts as this is a Trackable. READ is granted via an associated ProjectPermission.
A relation between RelationPartners (ComponentVersions and Interfaces). Relations are always directional. Relations can derive Interfaces from `end` to `start` if both `start` and `end` are ComponentVersions and the template of this Relation allows it. The template defines which RelationPartners are possible as `start` / `end`. For both start and end, if it is an Interface, it is possible to define the InterfaceParts this includes. Caution: This is **not** a supertype of IssueRelation. READ is granted if READ is granted on `start`.
Entity which can be used as start / end of Relations. Can be affected by Issues.
A target where users can configure how the sync should behave.
An entity which can have Issues, Labels and Artefacts. Has pinned issues. Can be synced to an IMS by creating an IMSProject. Can be affected by Issues.
Properties
Name of the bean defining the partOfProject filter
Name of the bean defining the relatedTo filter
Name of the bean which provides the sync allowed extension field
Name of the bean which provides the sync allowed extension field