prio is an evolving tool intended to help people prioritize their lives and stay organized.
prio can help you make difficult prioritization less painful, and also make sure that you don't forget about important things that you have to do.
Currently prio is in a closed testing stage, but if you want an account to help it evolve drop me a line at:
johno (at) johno (dot) se
Warning: Missing argument 4 for johno\prio\url\makeLink(), called in /customers/6/6/0/johno.se/httpd.www/prio/log.php on line 97 and defined in /customers/6/6/0/johno.se/httpd.www/prio/url.php on line 44
prionews submitted June 30, 2010, 13:30:06
I have iterated on my ideas for viewing retired tasks, online now.
Basically you can filter by label as before, as well as by month / year. The month / year selection is in the same style as the label filter, i.e. a horizontal layout of hyperlinks. I find this to make better use of screen real estate, and also I personally don't like dropdown lists...
- - - -
prionews submitted June 29, 2010, 15:34:40
I'm working on splitting up the display of retired tasks (and eventually submitted logs) into month-wise chunks. Work in progress, but a first version is online now.
- - - -
prionews submitted June 29, 2010, 13:33:54
I'm experimenting with the concept of "sub-users" in prio at the moment.
The idea is basically to be able to run a team off of a single prio account, with the owner of that account acting as the project leader.
The current test involves a single sub-user that has specific tasks in a project. Those tasks are marked with a specific label, and the sub-user has rights enabled to "retire" those tasks (and nothing else).
In addition, the sub-user can view everything (unsorted, active, and retired tasks, as well as logs) related to two different labels; one is the label that he can "retire" tasks in, as well as another project related label.
Currently the configuration for this sub-user is in code, but if things work out well I will make it data driven and expose it to all prio users.
- - - -
prionews submitted June 08, 2010, 00:23:40
I have implemented label based prioritization of tasks in prio.
This basically means that everything that has to do with tasks is filtered by label; viewing as well as (most importantly) prioritization.
This feature has evolved as a direct response to certain users request for a kind of heirarchy. While my original idea was that people should simply put every single task into a single pile and prioritize them, I realize that some people need to be able to separate for example work tasks from spare-time tasks (or any other split they might require). As a result, label based operation is now a part of prio.
For myself, I will be using labels to enable something that I've been missing from prio, namely the prioritization of tasks within a single project. While earlier everything was in a big pile, now I will be able to have a label called for example 'main' which represents tasks that are themselves projects, and then have a label that corresponds to each project which I use for each task in that project.
The big win here would then be that I can sort project tasks against each other, while all projects (tasks with the label 'main') can be sorted against each other. This is simply my personal take on how I will be using prio, and replaces my need for a separate todo-list per project.
I expect other users to use the labels feature in any number of creative ways; no single way is more right than any other.
- - - -