{5} Assigned, Active Tickets by Owner (Full Description) (45 matches)

I'm using the truck version. Performance of the home page seems much slower then previous versions. Included is the log of rendering the home page. hajee004s:/Library/WebServer/Documents/tracks/current root# script/server => Booting Mongrel (use 'script/server webrick' to force WEBrick) => Rails application starting on http://0.0.0.0:3000 => Call with -d to detach => Ctrl-C to shutdown server ** Starting Mongrel listening at 0.0.0.0:3000 ** Starting Rails with development environment... has_many_polymorphs: Rails environment detected has_many_polymorphs: loaded ok SwitchEnvironmentController?: missing default helper path switch_environment_helper UnobtrusiveJavascriptController?: missing default helper path unobtrusive_javascript_helper has_many_polymorphs: autoload hook invoked has_many_polymorphs: INIT ** Rails loaded. ** Loading any Rails specific GemPlugins? ** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart). ** Rails signals registered. HUP => reload (without restart). It might not work well. ** Mongrel available at 0.0.0.0:3000 ** Use CTRL-C to stop.

SQL (0.000479) SET SQL_AUTO_IS_NULL=0 Tagging Columns (0.004406) SHOW FIELDS FROM taggings Todo Columns (0.005293) SHOW FIELDS FROM todos has_many_polymorphs: injecting dependencies has_many_polymorphs: preloaded parent model Tag

Processing TodosController#index? (for 10.0.0.156 at 2007-07-30 22:43:37) [GET]

Session ID: 055722f63fe444e76e91c24f5c92e09b Parameters: {"action"=>"index", "controller"=>"todos"} User Columns (0.004880) SHOW FIELDS FROM users Preference Columns (0.007723) SHOW FIELDS FROM preferences User Load Including Associations (0.006263) SELECT users.id AS t0_r0, users.login AS t0_r1, users.crypted_password AS t0_r2, users.token AS t0_r3, users.is_admin AS t0_r4, users.first_name AS t0_r5, users.last_name AS t0_r6, users.auth_type AS t0_r7, users.open_id_url AS t0_r8, users.remember_token AS t0_r9, users.remember_token_expires_at AS t0_r10, preferences.id AS t1_r0, preferences.user_id AS t1_r1, preferences.date_format AS t1_r2, preferences.week_starts AS t1_r3, preferences.show_number_completed AS t1_r4, preferences.staleness_starts AS t1_r5, preferences.show_completed_projects_in_sidebar AS t1_r6, preferences.show_hidden_contexts_in_sidebar AS t1_r7, preferences.due_style AS t1_r8, preferences.admin_email AS t1_r9, preferences.refresh AS t1_r10, preferences.verbose_action_descriptors AS t1_r11, preferences.show_hidden_projects_in_sidebar AS t1_r12, preferences.time_zone AS t1_r13, preferences.show_project_on_todo_done AS t1_r14, preferences.title_date_format AS t1_r15, preferences.mobile_todos_per_page AS t1_r16 FROM users LEFT OUTER JOIN preferences ON preferences.user_id = users.id WHERE (users.id = 1) SQL (0.005529) SELECT count(*) AS count_all, project_id AS project_id FROM todos WHERE (user_id = 1 and state = 'active') GROUP BY project_id SQL (0.002191) SELECT count(*) AS count_all, context_id AS context_id FROM todos WHERE (user_id = 1 and state = 'active') GROUP BY context_id Project Columns (0.004824) SHOW FIELDS FROM projects Context Columns (0.006303) SHOW FIELDS FROM contexts Tag Columns (0.005997) SHOW FIELDS FROM tags Todo Load Including Associations (0.190127) SELECT todos.id AS t0_r0, todos.context_id AS t0_r1, todos.project_id AS t0_r2, todos.description AS t0_r3, todos.notes AS t0_r4, todos.created_at AS t0_r5, todos.due AS t0_r6, todos.completed_at AS t0_r7, todos.user_id AS t0_r8, todos.show_from AS t0_r9, todos.state AS t0_r10, projects.id AS t1_r0, projects.name AS t1_r1, projects.position AS t1_r2, projects.user_id AS t1_r3, projects.description AS t1_r4, projects.state AS t1_r5, projects.created_at AS t1_r6, projects.updated_at AS t1_r7, projects.default_context_id AS t1_r8, contexts.id AS t2_r0, contexts.name AS t2_r1, contexts.position AS t2_r2, contexts.hide AS t2_r3, contexts.user_id AS t2_r4, contexts.created_at AS t2_r5, contexts.updated_at AS t2_r6, tags.id AS t3_r0, tags.name AS t3_r1, tags.created_at AS t3_r2, tags.updated_at AS t3_r3 FROM todos LEFT OUTER JOIN projects ON projects.id = todos.project_id LEFT OUTER JOIN contexts ON contexts.id = todos.context_id LEFT OUTER JOIN taggings ON (todos.id = taggings.taggable_id AND taggings.taggable_type = 'Todo') LEFT OUTER JOIN tags ON (tags.id = taggings.tag_id) WHERE (todos.user_id = 1 AND (todos.state = 'active' or todos.state = 'completed')) ORDER BY completed_at DESC, todos.created_at DESC Todo Load Including Associations (0.018530) SELECT todos.id AS t0_r0, todos.context_id AS t0_r1, todos.project_id AS t0_r2, todos.description AS t0_r3, todos.notes AS t0_r4, todos.created_at AS t0_r5, todos.due AS t0_r6, todos.completed_at AS t0_r7, todos.user_id AS t0_r8, todos.show_from AS t0_r9, todos.state AS t0_r10, projects.id AS t1_r0, projects.name AS t1_r1, projects.position AS t1_r2, projects.user_id AS t1_r3, projects.description AS t1_r4, projects.state AS t1_r5, projects.created_at AS t1_r6, projects.updated_at AS t1_r7, projects.default_context_id AS t1_r8, contexts.id AS t2_r0, contexts.name AS t2_r1, contexts.position AS t2_r2, contexts.hide AS t2_r3, contexts.user_id AS t2_r4, contexts.created_at AS t2_r5, contexts.updated_at AS t2_r6, tags.id AS t3_r0, tags.name AS t3_r1, tags.created_at AS t3_r2, tags.updated_at AS t3_r3 FROM todos LEFT OUTER JOIN projects ON projects.id = todos.project_id LEFT OUTER JOIN contexts ON contexts.id = todos.context_id LEFT OUTER JOIN taggings ON (todos.id = taggings.taggable_id AND taggings.taggable_type = 'Todo') LEFT OUTER JOIN tags ON (tags.id = taggings.tag_id) WHERE (todos.user_id = 1 AND (todos.state = 'active')) ORDER BY todos.due IS NULL, todos.due ASC, todos.created_at ASC, completed_at DESC, todos.created_at DESC Project Load Including Associations (0.108122) SELECT projects.id AS t0_r0, projects.name AS t0_r1, projects.position AS t0_r2, projects.user_id AS t0_r3, projects.description AS t0_r4, projects.state AS t0_r5, projects.created_at AS t0_r6, projects.updated_at AS t0_r7, projects.default_context_id AS t0_r8, todos.id AS t1_r0, todos.context_id AS t1_r1, todos.project_id AS t1_r2, todos.description AS t1_r3, todos.notes AS t1_r4, todos.created_at AS t1_r5, todos.due AS t1_r6, todos.completed_at AS t1_r7, todos.user_id AS t1_r8, todos.show_from AS t1_r9, todos.state AS t1_r10 FROM projects LEFT OUTER JOIN todos ON todos.project_id = projects.id WHERE (projects.user_id = 1) ORDER BY position ASC Context Load Including Associations (0.104260) SELECT contexts.id AS t0_r0, contexts.name AS t0_r1, contexts.position AS t0_r2, contexts.hide AS t0_r3, contexts.user_id AS t0_r4, contexts.created_at AS t0_r5, contexts.updated_at AS t0_r6, todos.id AS t1_r0, todos.context_id AS t1_r1, todos.project_id AS t1_r2, todos.description AS t1_r3, todos.notes AS t1_r4, todos.created_at AS t1_r5, todos.due AS t1_r6, todos.completed_at AS t1_r7, todos.user_id AS t1_r8, todos.show_from AS t1_r9, todos.state AS t1_r10 FROM contexts LEFT OUTER JOIN todos ON todos.context_id = contexts.id WHERE (contexts.user_id = 1) ORDER BY position ASC Todo Load IDs For Limited Eager Loading (0.009136) SELECT id FROM todos WHERE (todos.user_id = 1 AND (todos.state = 'completed' and todos.completed_at is not null)) ORDER BY todos.completed_at DESC LIMIT 5 Todo Load Including Associations (0.011276) SELECT todos.id AS t0_r0, todos.context_id AS t0_r1, todos.project_id AS t0_r2, todos.description AS t0_r3, todos.notes AS t0_r4, todos.created_at AS t0_r5, todos.due AS t0_r6, todos.completed_at AS t0_r7, todos.user_id AS t0_r8, todos.show_from AS t0_r9, todos.state AS t0_r10, contexts.id AS t1_r0, contexts.name AS t1_r1, contexts.position AS t1_r2, contexts.hide AS t1_r3, contexts.user_id AS t1_r4, contexts.created_at AS t1_r5, contexts.updated_at AS t1_r6, projects.id AS t2_r0, projects.name AS t2_r1, projects.position AS t2_r2, projects.user_id AS t2_r3, projects.description AS t2_r4, projects.state AS t2_r5, projects.created_at AS t2_r6, projects.updated_at AS t2_r7, projects.default_context_id AS t2_r8, tags.id AS t3_r0, tags.name AS t3_r1, tags.created_at AS t3_r2, tags.updated_at AS t3_r3 FROM todos LEFT OUTER JOIN contexts ON contexts.id = todos.context_id LEFT OUTER JOIN projects ON projects.id = todos.project_id LEFT OUTER JOIN taggings ON (todos.id = taggings.taggable_id AND taggings.taggable_type = 'Todo') LEFT OUTER JOIN tags ON (tags.id = taggings.tag_id) WHERE (todos.user_id = 1 AND (todos.state = 'completed' and todos.completed_at is not null)) AND todos.id IN ('451', '591', '635', '634', '616') ORDER BY todos.completed_at DESC Context Load (0.003730) SELECT * FROM contexts WHERE (contexts.id = 2) Context Load (0.002074) SELECT * FROM contexts WHERE (contexts.id = 2) Context Load (0.001839) SELECT * FROM contexts WHERE (contexts.id = 2) Context Load (0.001816) SELECT * FROM contexts WHERE (contexts.id = 2) Context Load (0.001970) SELECT * FROM contexts WHERE (contexts.id = 1) Context Load (0.001740) SELECT * FROM contexts WHERE (contexts.id = 2) Context Load (0.001709) SELECT * FROM contexts WHERE (contexts.id = 1) Context Load (0.001975) SELECT * FROM contexts WHERE (contexts.id = 1) Context Load (0.001727) SELECT * FROM contexts WHERE (contexts.id = 1) Context Load (0.001762) SELECT * FROM contexts WHERE (contexts.id = 2) Context Load (0.001805) SELECT * FROM contexts WHERE (contexts.id = 1) Context Load (0.001735) SELECT * FROM contexts WHERE (contexts.id = 1) Rendering within layouts/standard Rendering todos/index Rendered todos/_todo (0.06213) Rendered todos/_todo (0.04967) Rendered todos/_todo (0.04772) Rendered todos/_todo (0.04522) Rendered todos/_todo (0.04587) Rendered todos/_todo (0.04447) Rendered todos/_todo (0.04450) Rendered todos/_todo (0.04510) Rendered todos/_todo (0.04928) Rendered contexts/_context (0.47278) Rendered todos/_todo (0.04561) Rendered todos/_todo (0.04354) Rendered todos/_todo (0.04617) Rendered todos/_todo (0.22122) Rendered todos/_todo (0.04637) Rendered todos/_todo (0.05110) Rendered todos/_toggle_notes (0.03037) Rendered todos/_todo (0.08107) Rendered todos/_todo (0.04284) Rendered contexts/_context (0.60880) Rendered contexts/_context (0.01735) Rendered todos/_todo (0.04302) Rendered contexts/_context (0.06246) Rendered contexts/_context (0.01685) Rendered contexts/_context (0.01862) Rendered todos/_todo (0.04514) Rendered todos/_todo (0.04097) Rendered todos/_todo (0.04097) Rendered todos/_todo (0.04176) Rendered todos/_todo (0.04246) Rendered todos/_todo (0.04277) Rendered todos/_todo (0.04145) Rendered todos/_todo (0.20716) Rendered todos/_todo (0.04731) Rendered todos/_todo (0.04360) Rendered todos/_todo (0.04384) Rendered todos/_todo (0.04243) Rendered todos/_todo (0.04398) Rendered todos/_todo (0.04285) Rendered contexts/_context (0.80283) Rendered todos/_todo (0.04100) Rendered todos/_todo (0.04235) Rendered todos/_todo (0.04168) Rendered todos/_todo (0.04742) Rendered todos/_toggle_notes (0.02100) Rendered todos/_todo (0.06922) Rendered contexts/_context (0.26472) Rendered contexts/_context (0.01828) Rendered todos/_toggle_notes (0.01989) Rendered todos/_todo (0.04487) Rendered todos/_todo (0.02457) Rendered todos/_todo (0.18734) Rendered todos/_todo (0.02741) Rendered todos/_todo (0.02664) Rendered todos/_completed (0.32564) Rendered shared/_add_new_item_form (0.02341) Rendered sidebar/_project (0.00944) Rendered sidebar/_project (0.00129) Rendered sidebar/_project (0.00125) Rendered sidebar/_project (0.00122) Rendered sidebar/_project (0.00128) Rendered sidebar/_project (0.00131) Rendered sidebar/_project (0.00126) Rendered sidebar/_project (0.00120) Rendered sidebar/_project (0.00121) Rendered sidebar/_project (0.00121) Rendered sidebar/_project (0.00124) Rendered sidebar/_project (0.00131) Rendered sidebar/_project_list (0.04197) Rendered sidebar/_context (0.00934) Rendered sidebar/_context (0.00183) Rendered sidebar/_context (0.00135) Rendered sidebar/_context (0.00184) Rendered sidebar/_context (0.00152) Rendered sidebar/_context (0.00125) Rendered sidebar/_context (0.00198) Rendered sidebar/_context (0.00128) Rendered sidebar/_context (0.00130) Rendered sidebar/_context_list (0.04002) Rendered shared/_flash (0.00903) Rendered shared/_footer (0.00866) Completed in 5.66548 (0 reqs/sec) | Rendering: 2.83032 (49%) | DB: 0.51922 (9%) | 200 OK http://hajee004s/

Processing UnobtrusiveJavascriptController#generate? (for 10.0.0.156 at 2007-07-30 22:43:44) [GET]

Session ID: 055722f63fe444e76e91c24f5c92e09b Parameters: {"page_path"=>["index.js"], "action"=>"generate", "controller"=>"unobtrusive_javascript"} Completed in 0.00646 (154 reqs/sec) | Rendering: 0.00018 (2%) | DB: 0.00000 (0%) | 200 OK http://hajee004s/behaviours/index.js

Viewing the notes out of context seems kind of pointless. Also in the project view the note might be better placed between the action list and the completed actions rather than at the end.

how about adding a 'followup' button next to 'delete' and 'edit' next to each action ? It would mark the action as done, but prompt for the next action in the same project and propose the same context by default. E.g. I would mark 'call X about Y' done and immediately add 'wait for answer fro X about Y' as next action.

Projects are an excellent way of defining lots of next actions into a group with a singular goal, but what do you do about NAs that depends on another NA to be completed?

What i'm suggesting is a slight modification to the ticker system that currently exists in trunk, you can set a date for the NA to show on the main list OR when a certain NA has been completed. That way when you complete one NA on your main list, the follow-on NA will be transfered from the Tickler to the main list.

This feature would be an amazing timesaver, and i guess that other people would also like it implemented.

It will be convenient to do assignment of responsible persons for task

When I create a project, I'd like to pick a default context to use for its next actions. My "update online portfolio" project is all computer context, for example.

I'd love for Tracks to make intelligent guesses about the proper context for actions. Don't most next actions begin with a verb? The guesser could assume that actions are worded "[verb] [direct object] [prepositions] [indirect object]". When a verb keyword is matched, it triggers the appropriate context. The user should be able to define verb-context pairs. E.g.:

• Items beginning with "call" or "phone" trigger the calls context, such as "call Johnson about lack of TPS reports."
• Ditto for "email".
• Words like "buy", "fetch", and "drop off" trigger the errands context.
• Because Kelly's hobby is woodworking, she has created a woodshop context, and defined its trigger verbs as "build", "saw", and "varnish".

What do you think?

I'm noticing that as time progresses, I have projects with several next actions that all become stale simultaneously, and the reason is because some other task/project has come up that either trumps that project in priority, or somehow makes that other project completely dependant upon the new task/project.

It would appear that there needs to be a way to set an entire project into a "waiting for" context.

Also, if you have a task that is in the "waiting-for" context, it would then seem that you should be able to set a primary context for the task, and when placing it into "waiting-for", select the task or project it is waiting for. When that task/project gets moved to complete, the task should automatically leave (or at least prompt the user) the "waiting-for" context and set itself into its new home.

In this same vein, when an item gets moved either to or from the "waiting-for" context, it's staleness factor should either be refreshed or ignored. "Waiting For" means just that, it is waiting for something. Turning the item all sorts of alarming colors doesn't do anything but induce stress. :) As of right now the only way to get rid of the staleness colors is to get a due date, even if it is is "waiting for" something else. That just doesn't make sense, now does it? ;)

There should be a system default "Someday Maybe" context where you can create items that never become stale, or turn all kinds of scary and alarming colors.

First of all - nice application - really looks good and thank you for doing this and making it available to others.

Secondly, I looked at your roadmap and, to share my 2 cents worth - please think about doing the stand-alone sooner rather than later. I think GTD is going to be the only way I'm going to get myself more effective and efficient and I travel a lot (don't always have access to a web connection).

Again, thanks and I hope you enjoyed Brazil.

I find that when I create a project, I often come up with several future actions. However, these actions are sequential, i.e. action 3 depends upon the completion of action 2, action 2 on action 1, etc. As such, I only want to see the next action (action 1), and not the follow-up actions (2,3). Looking through previous tickets, I noticed that others have requested a similar feature, though it appears that the current version of Tracks (svn revision 170) does not yet support this.

After (briefly) looking through the code and the database, I thought of one way that this might be implemented. Two new columns could be added to the 'todo' table: 'active' (a boolean which could prevent display) and 'predecessor_id'(or something similar). An existing action would then have a link to create a follow-up action; the follow-up's predecessor_id would be set to that of the existing action, and would be marked as inactive. When the existing action is marked as done, it would look for any follow-up actions and mark them as active (hence one action could have multiple follow-ups).

The active/predecessor_id columns could also be added to projects, so that projects could be treated in the same fashion. One issue here, though, would be determining if a predecessor_id refers to an action or a project.

A side benefit of adding an active flag to actions/projects is that it could also be used to for the Someday/Maybe context; any actions/projects added to Someday/Maybe could be marked as inactive so that they are not shown in the 'Home' display.

This is a longshot, and a lot of work. I was using the GTD Add-In for MS Outlook for a while, and I'd LOVE to see Tracks support this sort of thing.

Essentially, Tracks would have to act as a web based email client. All email comes to your inbox and you then filter it from there, but w/ somewhat sophistocated wizards. For example, an email comes in from your real estate agent about an offer you've received for your house. From the Projects list, you select "Sell house". From the "Contexts" list you select "At Computer". You click the reply button and email your agent a counter offer. When you send it, instead of going to "Sent Mail", a copy goes to "Waiting".

You get the idea. Obviously, there are a million ways this could work, and the best approach might be to offer simple manual options in earlier releases that can be automated in later releases.

I find myself updating the notes on a project's next action a lot as things change, or when I shift the action from some context to @Waiting For. It would be neat if a history was kept every time the notes field was updated. This would create a journal or diary on each task as it was updated.

hifi@alphalink.com.au

I would like to see a limited number of NAs for a given project in my home and context view. I currently accomplish this by only ever having 1 NA on the project NA list and the others as a project note. Then as I finish one I move one off of the note and put it in the proper context.

A more elegant solution would be to allow you to list as many NAs on a project page as you wish but only ever queue up one per context.

I use the Edit Action box a lot to keep a running update of the task status, email snippets, etc. There are a few simple changes that would make it a bit more useful:

1. Increase the text box size (maybe even configurable)

2. Have a button that would pop-up a much larger standalone text box in its own browser window (like some of the blog 'Add a comment' features do)

3. Add Submit and Cancel to the top of the window since often times they're off the bottom of the screen.

I changed the view template for my own installation to deal with 1 and 3 and I like it better, though something like this may be highly user dependent.

Regards, Jim

I just started using Tracks and it's great. However, it would be really helpful if there would be a button next to each action such that when you click it, it brings you to a specific directory (depending on the action) which contains the files regarding this action, so that you find the files related to the action immediately and start completing the action...

I regularly carry out the same set of actions as part of a process. Would it be possible to allow me to create a 'template project' containing actions for each step in the process, and then create instances of that template as required?

None of the documentation specifies a) what the Notes functionality is for and b) how I can enable whatever functionality it may provide.

When I click the "Notes" top navigation item I see no content (although I see the tracks framework HTML), and no buttons to perform any actions.

I am an ecstatic user of tracks 1.04 on Linux Fedora Core 4 using Firefox 1.5. I use project and context functionality daily and have no other functional problems.

When I add new next action with due date set it goes to the bottom of the specified context unconditionally.

It's only gets sorted to a proper place of the list when I refresh the page.

If there is interest, at some stage we should consider adding Multilingual support.

I'd love to see the ability to set a META HTTP-EQUIV=REFRESH value on the main page. It's necessary, in my opinion, now that we have an API that allows users to add new tasks via interfaces other than the web page itself. For instance, if I add a few new things via a Quicksilver command, and then later return to my main Tracks page, which has been sitting in the background somewhere, those new items won't be visible until I refresh the page. As a result, I sometimes forget that such items are there for quite a while. But if the page refreshed itself automatically at some pre-set interval, such items would eventually show back up.

I see this as being implemented by a new preference. By default, the refresh would be set to '0,' which would mean not to include a refresh tag on the main page. A user could enter a numeric value equal to the number of minutes between refreshes. (When implementing the tag, this numeric value would have to be multiplied by 60, as the refresh tag counts in seconds rather than minutes.)

The context drop down is not functioning in the add next action form on the home page. If I enter the first letter of the context, auto complete does work. If I delete the text I type, leaving the text box empty, the drop down will function. ~ Changed type to enhancement -Luke

I'd really like the ability to cc an email address and have tracks catch the email and file it as an action item. I can later go into tracks and tidy it up - project / delivery date etc.

I know some apps also try to do the whole context thing, and parse the email for due dates, project, but that's probably a step too far - and would defeat the 'quick update' purpose of the request.