Just a few days ago Github announced their new update of Github Issues. You can see the updates with some screenshots from here. Also, please take a look at the new Deployment API if you haven’t already.
Move beyond the simple Issues
Starting at the same day something else were released, not by GitHub, but still connected to Issues. Let me show you, how you can use a chain of tools to make your GitHub Issues even more useful for your team.
The players:
A website
Imagine you have a website, that is hosted on Github, like this one, which is the code-base for input.mozilla.com.
A team/community
Let’s also imagine that you have a team or a community which is handling bug-requests. You have a designer and a programmer at least.