Declared as a bug
-
Project label
-
Confirmed as a bug
-
Project label
-
Proposal to improve source code, documentation or any other things
-
Project label
-
Issue is mature and marked as a valid story candidate for the backlog (objectives, description and acceptance tests are understood). It is waiting for a peer review. There can only be one "Story" tag per issue.
-
Project label
-
Issue is being worked on, it is not a valid story (refine objectives, description or acceptance tests) but it should become one.
-
Project label
-
Related to the improvement of the source code maintainability, stability, readability and security. Include source code review.
-
Project label
-
Related to adding or improving continuous integration and delivery, i.e. source code tests (unit, integration or functional tests), CI script,...
-
Project label
-
-
Project label
-
Related to the writing or improving user support, includes all issues about project documentation (internal documents for CamiTK or API or other documents for CEP developers)
-
Project label
-
Related to the GUI/ergonomy of any front-end application (e.g., camitk-imp, state machine...) for end users (e.g, clinicians,...)
-
Project label
-
Plugin management, packaging, .cep
-
Project label
-
By default issues should not have any track. If a track label is added, remove this label. An issue with a track label can enter the story conformance process.
-
Project label
-
Related to the improvement of the prototyping experience felt by developers
-
Project label
-
-
Project label
-
Prioritized label