Show me how you set priorities on tickets at Github? Apparently they are philosophically opposed to you being able to sort issues by importance.
One thing I love about Google Code is that they allow multiple repositories per "project". This is very important for when you want to share the same issue tracker, wiki, downloads etc because the items are related. Many of the overall projects I work on have a server piece, some tools and an Android client. They all work together as a whole. When there is an issue, it is often not apparent where the blame actually lies and which component will need to be changed to fix it. (Eg a font being too large in the Android client could have been generated from the server which served up templates made by a tool.) Google rule out private hosting so they can't be used in this scenario - http://code.google.com/p/support/issues/detail?id=1829
As a regular user of Google Code, Bitbucket and Github, the arbitrary differences are very annoying. Each uses a different wiki syntax, and most relevant each has a different syntax for closing tickets in a commit comment - they are similar but not exactly the same.
We use tags on github for priority. Combined with milestones, we're easily able to figure out what to work on next.
Right now just limited to "High", "Medium" and "Low", but we could have whatever level of granularity we want. We can also color code the tags (red = high, orange = medium, yellow = low).
The thing I really miss on github is a place to stick a numeric estimate for how long something will take to help with knowing how much capacity we have left in a release/iteration.
I don't see any way of sorting by tags. We also use tags for several other things so it wouldn't even know which tags to sort by.
trac does a really good job on this side of things, especially a nice place to provide (and sort) milestones, show their progress, a little bit of writeup etc. This is an example:
One thing I love about Google Code is that they allow multiple repositories per "project". This is very important for when you want to share the same issue tracker, wiki, downloads etc because the items are related. Many of the overall projects I work on have a server piece, some tools and an Android client. They all work together as a whole. When there is an issue, it is often not apparent where the blame actually lies and which component will need to be changed to fix it. (Eg a font being too large in the Android client could have been generated from the server which served up templates made by a tool.) Google rule out private hosting so they can't be used in this scenario - http://code.google.com/p/support/issues/detail?id=1829
As a regular user of Google Code, Bitbucket and Github, the arbitrary differences are very annoying. Each uses a different wiki syntax, and most relevant each has a different syntax for closing tickets in a commit comment - they are similar but not exactly the same.