{"id":2078,"date":"2014-07-31T13:17:55","date_gmt":"2014-07-31T11:17:55","guid":{"rendered":"https:\/\/usersnap.com\/?p=2078"},"modified":"2025-10-01T07:30:28","modified_gmt":"2025-10-01T05:30:28","slug":"github-issues-tip-will-make-life-easier-4-github-tricks-facts","status":"publish","type":"post","link":"https:\/\/usersnap.com\/blog\/github-issues-tip-will-make-life-easier-4-github-tricks-facts\/","title":{"rendered":"A Github Issues tip that will make your life easier and 4 GitHub tricks and facts"},"content":{"rendered":"\n

Just a few days ago Github announced their new update of Github Issues<\/em>. You can see the updates with some screenshots from here<\/a>. Also, please take a look at the new Deployment API<\/a> if you haven\u2019t already.<\/p>\n\n\n\n

Move beyond the simple Issues<\/b><\/p>\n\n\n\n

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<\/em> even more useful for your team.<\/p>\n\n\n\n\n\n\n

Try Usersnap for Bug Tracking<\/h2>Try Usersnap Now<\/a><\/div>\n\n\n\n

The players:<\/h2>\n\n\n\n

A website<\/h3>\n\n\n\n

Imagine you have a website, that is hosted on Github, like this one<\/a>, which is the code-base for input.mozilla.com.<\/p>\n\n\n\n

A team\/community<\/h3>\n\n\n\n

Let\u2019s also imagine that you have a team or a community which is handling bug-requests. You have a designer and a programmer at least.<\/p>\n\n\n\n

Users<\/h3>\n\n\n\n

Millions of people are browsing your website month after month and at least a couple of them will find something to complain about, right? \ud83d\ude42 Let\u2019s take this seriously<\/strong> – Every website owner wants to make the users happy for one reason or another and when a problem appears – it must be fixed in time. Right?<\/p>\n\n\n\n

In short, we have a website with source hosted on GitHub and something happens and the team must fix it.<\/strong><\/p>\n\n\n\n

The process and how much time it takes to fix a bug<\/h2>\n\n\n\n

So, someone discovered a bug. Let\u2019s say one of the L10n strings breaks the layout. Yes, it happens all the time, especially with those Cyrillic languages, right:<\/p>\n\n\n\n

\"5044f737-ec1e-4af5-ab52-1afaeafd1596\"<\/a><\/figure>\n\n\n\n

<\/p>\n\n\n\n

Let\u2019s see the whole process step by step<\/h2>\n\n\n\n
Steps<\/strong><\/td>Time<\/strong><\/td><\/tr>
The user is trying to find a way to report the bug (contact-us section)<\/td>2 mins<\/td><\/tr>
The user sends an e-mail to the support – with a description of the bug – ‘your Russian version is broken. You have problems in the footer. Please fix it<\/em>‘<\/td>2 mins<\/td><\/tr>
The support guy assigns the bug to the dev team<\/td>1 min<\/td><\/tr>
A QA person is trying to reproduce the bug. Cannot reproduce. Works like a charm. Closing it!<\/td>5 mins<\/td><\/tr>
The same bug is reported again<\/td><\/tr>
The QA is trying to get the information from the end-user – a screenshot, OS, browser version, screen resolution, plugins installed in the browser, etc<\/td>25 mins<\/td><\/tr>
Now we have everything (after teaching the user how to collect the information, again and again). the QA enters the bug into the GitHub Issues providing all information from the client + attaching a screenshot<\/td>7 mins<\/td><\/tr>
The Project Manager is assigning the task to a developer<\/a> and to a milestone + adding labels of course.<\/td>3 mins<\/td><\/tr>
The developer fixes the issue<\/td>it depends \ud83d\ude42<\/td><\/tr>
Total: <\/strong>45 mins + it depends<\/span><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Right now this is one of the most popular processes<\/strong> in the industry. Of course, there can be some improvements, but not like the one I will show you now.<\/p>\n\n\n\n

\n

What about if I told you there is a way to drastically decrease the time above: from 45 min to 15 or even less?!<\/p>\n<\/blockquote>\n\n\n\n

Advice from experts – add visual feedback<\/h2>\n\n\n\n

Let\u2019s see which of the processes we can optimize:<\/p>\n\n\n\n