A proposal/project which needs attention from ASAM office.

A proposal/project which needs to be discussed across standards in the coordination group meeting.

A proposal which is approved by all relevant CCBs.

A proposal that is ready to be reviewed by at least 1 Standard CCB

A proposal which is currently open for members to enroll for.

A project which all of its Merge requests are merged into respective release candidates from all relevant standards

A proposal which is still in draft state, and not ready for review by CCBs yet

A project which is currently in development

A project which is completely reviewed, and ready for merge in next standard(s) releases(s)

A proposal that was rejected by either the CCB(s) or the TSC

A project which has finished and in review phase

A proposal which is approved by TSC to start

A project which is ready for TSC review (approved by the CCB(s) and have minimum 3 companies enrolled)

An issue that has been accepted by the group, which needs to be assigned to a responsible, given a due date and needs a clear specification of requirements to be fulfilled. 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 has a type and that needs to be accepted by the group. 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 has a solution in an associated merge request, which is ready to be reviewed by the group. 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 is assigned a responsible, has a due date and clear requirements, which now needs to be implemented in a solution. 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 has been integrated and has an integration reviewer, which is ready to be checked and all open comments are resolved. 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.

A new issue that needs to be classified to a type. 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 has been integrated and is assigned to the workflow manager, which is ready to be merged. 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.