An issue that has a been accepted by the group, has an assigned integrator, which is ready to be integrated into the standard or project. State labels reflect the current state of an issue. State labels should change in accordance to the state of an issue. An issue shall have one state. On changing state, a new state label shall be added and the old state label shall be removed. See the contribution workflow documented in the project guide https://asam-ev.github.io/asam-project-guide/asamprojectguide/latest/tour_guide/contribution.html.

An issue that contains contradictions or errors in the standard. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.

An issue documenting meeting minutes for an ASAM CCB meeting. Meeting minutes should be kept for each official CCB meeting. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.

An issue that contains general structural and editorial changes for the whole documentation. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.

An issue that amends or improves existing features. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.

An issue related to the repository infrastructure such as CI, builds, document toolchain or similar. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.

An issue documenting meeting minutes for an ASAM meeting. On starting, a project shall define the location of all meeting minutes for the project. This is either in a project sharepoint or in the issue list. Meeting minutes should be kept for each official project meeting. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.

An issue that adds new features to the project. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.

General questions about the project, work-flow or anything related to the standard as well as support requests. Type labels display the intended field of the issue. Type labels are static and never change. An issue shall only have one type.

This issue has already been raised or was already solved in another issue. Resolution type labels indicate why an issue was closed. An issue must be closed to have a resolution and shall only have one resolution type.

The task described in the issue was addressed. Resolution type labels indicate why an issue was closed. An issue must be closed to have a resolution and shall only have one resolution type.

The task described in the issue will not addressed by this standard. Resolution type labels indicate why an issue was closed. An issue must be closed to have a resolution and shall only have one resolution type.