Of critical priority for the client, the project cannot move forward without a resolution.

Low priority. An improvement to the project, but should not be scheduled in the next two or three sprints.

Of medium priority. Should be scheduled in a forthcoming sprint, but other issues should be resolved first.

A question which needs to be resolved before a feature request or bug fix can be recorded as an issue.

A change in the code that improves its structure and sustainability but does not change its semantics

Resources related to scenes in simulations.

An issue / merge request dealing with a bug that allows unauthorised access to data.

Whilst not currently causing an issue, this will need to be resolved in future.

An issue / merge request in the current backlog.

A tracking issue can be closed when a number of related issues are closed. Tracking issues should have a list of checkboxes that refer to their related sub-issues.

Resources related to creating and updating traffic lights

Issue or merge request is currently waiting on a reviewer, or waiting on a response to a review.

Adding new unit tests or refactoring existing ones.

Resources related to creating and updating vehicles

This is a known issue that has no planned solution in the forseeable future, either due to technical difficulty or poorly skewed effort vs reward.