Cleaning up the issue tracker

Our issue tracker at is in desperate need of a spring cleaning. Most of the issues were imported from our old repository at Google Code, which had a much nicer way to sort and prioritize them. With github, we need to be much more disciplined. :smile:

Here are a few things to do:

  • Reduce and consolidate the labels – done
  • Move parts-related issues to fritzing-parts – done
  • Get rid of old issues that no longer apply – partly done
  • Label recent issues – partly done
  • Differentiate all issues between bug / enhancement / question – partly done
  • Revise all critical and high priortiy issues – critical done
  • Identify issue that could be good starting points for new developers and mark as grab me – started