List view

• 4.6.0

  No due date

  •0/4 issues closed
  0% complete4 open0 closed

• 4.4.0

  No due date

  •23/23 issues closed
  100% complete0 open23 closed

• backlog

  if we have some milestones in the distant future and assign tickets to this milestone, because you do not want to decide now: at some day we will have plenty of these tickets to review again. Proposal is to have a backlog milestone for tickets that are a) useful b) not high prio c) unclear situation who is going to work on it in the milestone section instead of assigning this to an actual milestone.

  No due date

  •169/261 issues closed
  64% complete92 open169 closed