1 September 2014 3 minutes to read
Some years ago I've realized that the Agile way steals a lot of the development time. Whenever I start a new task I must change the status, later I have to modify it once again and so on. I can recall many tickets which were as costly as the time needed for their organization and only in case I have a direct link to the corresponding board.
A company with a small number of projects may modify the JIRA’s homepage accordingly. But those lucky gluttons who have more than 20 projects are really suffering. It is almost impossible to find a group of tasks you need in two clicks and a manager(or scrum master) spends a lot of time with a custom JQL queries.
How to develop a routine to stop wasting time? - it was the question a few years ago. To help myself and those guys who use the Chrome browser, I decided to create a new extension with a limited set of requirements.
|#169||Add part of url to the debug output||enhancement|
|#168||Work-log locale interpretation problem||bug|
|#166||Improve debug output||enhancement|
|#165||An example of intranet address in URL hint||enhancement|
|#164||Link to gitter chat||enhancement|
|#157||Check the connection icon does not ask for permission||bug|
|#156||Status icon is not available.||bug|
|#155||Highlight the "enable account" button||enhancement|
|#148||Assigned ticket notification is not clickable||bug|
At first glance the technology stack looks normal. However, I would like to clarify some points.
In the end of 2012 I had a long and nice discussion touching many aspects of JS frameworks including their future. We’ve ended it with two most promising: Ember.js and Angular.js. Since then nothing changed. Angular.js is the most popular and easiest event-driven framework nowadays.