Prioritized Labels
  • Weight XXL
    This is an epic or a very big task that requires to be fragmented into sub stories. About 16 scrum points !
    • Project label
  • Weight XL
    Hard or Complicated Task. About 8 scrum points. This story can still be considered as one story and, although it is hard and/or long, there is no good reason to subdivide it into other stories.
    • Project label
  • Weight L
    Normal Task or easy but long. About 5 scrum points.
    • Project label
  • Weight M
    Easy Task. About 3 scrum points.
    • Project label
  • Weight S
    Very Easy Task. About 2 scrum points. The objectives and tasks of the story are clearly defined, it should take a small amount of time and have no specific complexity to manage.
    • Project label
  • Weight XS
    Ultra Easy Task. About 1 scrum point. All the actions to complete the story are clearly defined, no surprise are expected, can be done eyes closed.
    • Project label
  • Backlog
    Issue/story in the release backlog (i.e., planned to be done during for the next release). This issue is a valid story (objectives, description and acceptance tests are clearly understood). Please remove all "Story" tags
    • Project label
  • Sandbox
    Issue has a track. But it is not a valid story (some criteria is missing) or is not in the current project focus or priority.
    • Project label
  • CamiTK 4.2 Sprint #1
    Issue/story in the backlog of the first sprint for CamiTK 4.2 release (i.e., planned to be done during this sprint)
    • Project label
  • CamiTK 4.2 Sprint #2
    Issue/story in the backlog of the second sprint for CamiTK 4.2 release (i.e., planned to be done during this sprint)
    • Project label
  • CamiTK 4.2 Sprint #3
    Issue/story in the backlog of the third sprint for CamiTK 4.2 release (i.e., planned to be done during this sprint)
    • Project label
  • Other Labels
  • Feature Request
    Proposal to improve source code, documentation or any other things
    • Project label
  • Bug
    Declared as a bug
    • Project label
  • Bug Confirmed
    Confirmed as a bug
    • Project label
  • Track Code Maintainability
    Related to the improvement of the source code maintainability, stability, readability and security. Include source code review.
    • Project label
  • Track Debugging
    • Project label
  • Track None
    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
  • Track Prototyping Experience
    Related to the improvement of the prototyping experience felt by developers
    • Project label
  • Track Knowledge Management
    Plugin management, packaging, .cep
    • Project label
  • Track Technology Integration
    • Project label
  • Track Continuous Integration
    Related to adding or improving continuous integration and delivery, i.e. source code tests (unit, integration or functional tests), CI script,...
    • Project label
  • Story Acceptable
    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
  • Story WIP
    Issue is being worked on, it is not a valid story (refine objectives, description or acceptance tests) but it should become one.
    • Project label
  • Track Dev Support
    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
  • Track End User Experience
    Related to the GUI/ergonomy of any front-end application (e.g., camitk-imp, state machine...) for end users (e.g, clinicians,...)
    • Project label