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.
|#8||Remember the opened tab||enhancement|
|#7||Make release 2.0||enhancement|
|#6||Add timer for the active issue.||enhancement|
|#4||Show the current status of the ticket||enhancement|
|#3||Replace a ticket description with a ticket title||enhancement|
|#2||Add "change the state" option||enhancement|
|#14||Add badge icon with timer for the active issue.||enhancement|
|#13||A button to stop a timer without time-logging.||enhancement|
|#11||Design issue if more that 2 workflows||bug|
|#10||Increase ajax timeout to 10sec||duplicate|
|#9||Increase ajax timeout to 10sec||enhancement|
|#15||Badge requires background task||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.