Pretty cool extension. I'll give it a shot at work this week.
I do have a question though, what is the difference between the value field and the estimated effort field? Value gets displayed on the card when view the whole board but effort doesn't. I would expect effort to be listed as well but then again 'm not really sure what value is meant to represent.
Estimated effort is the amount of work (e.g. in hours) it takes to get the job done. Value defines how valuable the outcome of the task is (which should correlate with how quickly you actually do the task).
So given two tasks: Task A with 5 hrs of effort and value of 100, and Task B with 5 hrs of effort and value of 20, you should first do Task A since it produces more value. Value figures should be relative so when you estimate how valuable some task is, compare it to at least two other tasks.
"tabs" is just needed to check if Kanbanly is already open in another tab. If yes, activate that tab instead of opening a new tab.
The side effect of this permission is that Chrome claims the extensions has access to browsing history (which is incorrect since that would require "history" permission). So it's really a Chrome bug and the WebExtension does not access your history or any content in tabs whatsoever.
9 comments
[ 3.6 ms ] story [ 32.1 ms ] threadI do have a question though, what is the difference between the value field and the estimated effort field? Value gets displayed on the card when view the whole board but effort doesn't. I would expect effort to be listed as well but then again 'm not really sure what value is meant to represent.
So given two tasks: Task A with 5 hrs of effort and value of 100, and Task B with 5 hrs of effort and value of 20, you should first do Task A since it produces more value. Value figures should be relative so when you estimate how valuable some task is, compare it to at least two other tasks.
Could you just add some keyboard shortcuts for jumping between lists please?
"permissions": [ "tabs", "https://www.googleapis.com/", "identity", "notifications" ]
"tabs" is just needed to check if Kanbanly is already open in another tab. If yes, activate that tab instead of opening a new tab.
The side effect of this permission is that Chrome claims the extensions has access to browsing history (which is incorrect since that would require "history" permission). So it's really a Chrome bug and the WebExtension does not access your history or any content in tabs whatsoever.