<?xml version="1.0" encoding="UTF-8"?>
<tickets type="array">
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2012-05-25T03:56:46Z</created-on>
  <description>'rails server' works well with the development database. 'rails server -e production' produces the following problem when looking at pages:

&lt;pre&gt;&lt;code&gt;ActionController::RoutingError (No route matches [GET] &quot;/assets/favicon-b8d09938b88c0a73921a57660601d2ca.ico&quot;):
  actionpack (3.2.3) lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'
  actionpack (3.2.3) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call'
  railties (3.2.3) lib/rails/rack/logger.rb:26:in `call_app'
  railties (3.2.3) lib/rails/rack/logger.rb:16:in `call'
  actionpack (3.2.3) lib/action_dispatch/middleware/request_id.rb:22:in `call'
  rack (1.4.1) lib/rack/methodoverride.rb:21:in `call'
  rack (1.4.1) lib/rack/runtime.rb:17:in `call'
  activesupport (3.2.3) lib/active_support/cache/strategy/local_cache.rb:72:in `call'
  rack (1.4.1) lib/rack/lock.rb:15:in `call'
  rack-cache (1.2) lib/rack/cache/context.rb:136:in `forward'
  rack-cache (1.2) lib/rack/cache/context.rb:245:in `fetch'
  rack-cache (1.2) lib/rack/cache/context.rb:185:in `lookup'
  rack-cache (1.2) lib/rack/cache/context.rb:66:in `call!'
  rack-cache (1.2) lib/rack/cache/context.rb:51:in `call'
  railties (3.2.3) lib/rails/engine.rb:479:in `call'
  railties (3.2.3) lib/rails/application.rb:220:in `call'
  rack (1.4.1) lib/rack/content_length.rb:14:in `call'
  railties (3.2.3) lib/rails/rack/log_tailer.rb:14:in `call'
  rack (1.4.1) lib/rack/handler/webrick.rb:59:in `service'
  /home/popsch/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/webrick/httpserver.rb:138:in `service'
  /home/popsch/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/webrick/httpserver.rb:94:in `run'
  /home/popsch/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/webrick/server.rb:191:in `block in start_thread'
&lt;/code&gt;&lt;/pre&gt;
</description>
  <from-support type="integer">1</from-support>
  <id type="integer">22030683</id>
  <importance type="integer">1264</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>aUkc3w1Y0r4jEseJe4gwI3</notification-list>
  <number type="integer">1300</number>
  <priority type="integer">3</priority>
  <reporter-id>aUkc3w1Y0r4jEseJe4gwI3</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>production mode doesn't show pages</summary>
  <updated-at type="datetime">2012-05-25T03:57:20Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">Small</estimate>
  <total-estimate type="float">1.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aUkc3w1Y0r4jEseJe4gwI3</id><login>popsch</login><login_name warning="deprecated">popsch</login_name><name>popsch</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">defect</custom-field>
<custom-field type="List" name="Severity" id="3081">blocker</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">defect</CustomField>
<CustomField type="List" name="Severity" id="3081">blocker</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2012-05-25T04:09:04Z</created-on>
  <description>When I click on the 'show notes' icon, then the yellow notes are briefly shown before the notes collapse again. This happens with the latest firefox and google chrome browser.</description>
  <from-support type="integer">1</from-support>
  <id type="integer">22031053</id>
  <importance type="integer">1265</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>aUkc3w1Y0r4jEseJe4gwI3</notification-list>
  <number type="integer">1301</number>
  <priority type="integer">3</priority>
  <reporter-id>aUkc3w1Y0r4jEseJe4gwI3</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>cannot unfold notes with rails3</summary>
  <updated-at type="datetime">2012-05-25T04:09:04Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">Small</estimate>
  <total-estimate type="float">1.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aUkc3w1Y0r4jEseJe4gwI3</id><login>popsch</login><login_name warning="deprecated">popsch</login_name><name>popsch</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">defect</custom-field>
<custom-field type="List" name="Severity" id="3081">critical</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">defect</CustomField>
<CustomField type="List" name="Severity" id="3081">critical</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">4</component-id>
  <created-on type="datetime">2012-04-12T17:21:05Z</created-on>
  <description>I installed 2.1as of this morning (with the rendered notes in the db).  Install and migration went fine (had to disable zentest and fix permissions on /public/stylesheets and /public/javascripts).

When I opened up my homepage and clicked on 'toggle notes' the notes weren't there, only a thick yellow line where they should be (i.e., rendering a 'NULL' note).  After I recovered from cardiac arrest I clicked 'edit' on a todo and the note was still there, and after clicking 'update' it showed up on the homepage.  However, reloading the homepage made it disappear again.

Tracked it down to a missing 'self' in the todo model and created a new migration to fix the database. 
Patch attached.  So far so good, will test some more later.</description>
  <from-support type="integer">1</from-support>
  <id type="integer">18739963</id>
  <importance type="integer">1278</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1250953</milestone-id>
  <notification-list>c8JmGwsZCr4jRTeJe5cbLA,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1278</number>
  <priority type="integer">2</priority>
  <reporter-id>c8JmGwsZCr4jRTeJe5cbLA</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Migration for rendered_notes does not work - Fix attached</summary>
  <updated-at type="datetime">2012-04-20T13:30:30Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">Small</estimate>
  <total-estimate type="float">1.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>c8JmGwsZCr4jRTeJe5cbLA</id><login>cfrankct</login><login_name warning="deprecated">cfrankct</login_name><name>cfrankct</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">defect</custom-field>
<custom-field type="List" name="Severity" id="3081">blocker</custom-field>
<custom-field type="List" name="Version" id="3084">2.1RC1</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">defect</CustomField>
<CustomField type="List" name="Severity" id="3081">blocker</CustomField>
<CustomField type="List" name="Version" id="3084">2.1RC1</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2012-05-09T12:46:02Z</created-on>
  <description>Actions inside a project were sorted by due date in Tracks 1.7.2.  Tracks 2.0 and Tracks 2.1 do not sort actions inside a project. The actions appear in the order in which they were created.

Please restore the Tracks 1.7 behavior in Tracks 2.1.1

Thanks,

Werner</description>
  <from-support type="integer">1</from-support>
  <id type="integer">20915033</id>
  <importance type="integer">1291</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1250953</milestone-id>
  <notification-list>bp2AVIMDar4z40acwqjQWU,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1292</number>
  <priority type="integer">2</priority>
  <reporter-id>bp2AVIMDar4z40acwqjQWU</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Actions not sorted in a project.</summary>
  <updated-at type="datetime">2012-05-09T19:31:40Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">Small</estimate>
  <total-estimate type="float">1.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></assigned-to>
  <reporter><id>bp2AVIMDar4z40acwqjQWU</id><login>werner.fouche</login><login_name warning="deprecated">werner.fouche</login_name><name>werner.fouche</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">defect</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">2.1</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">defect</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">2.1</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2012-04-24T09:31:09Z</created-on>
  <description>add test too

fix:

diff --git a/app/controllers/projects_controller.rb b/app/controllers/projects_controller.rb
index 24aa5ea..c5366d9 100644
--- a/app/controllers/projects_controller.rb
+++ b/app/controllers/projects_controller.rb
@@ -267,6 +267,7 @@ class ProjectsController &lt; ApplicationController
     @projects = current_user.projects.alphabetize(:state =&gt; @state) if @state
     @contexts = current_user.contexts
     init_not_done_counts(['project'])
+    init_project_hidden_todo_counts(['project']) if @state == 'hidden'
   end
 
   def actionize
@@ -274,6 +275,7 @@ class ProjectsController &lt; ApplicationController
     @projects = current_user.projects.actionize(:state =&gt; @state) if @state
     @contexts = current_user.contexts
     init_not_done_counts(['project'])
+    init_project_hidden_todo_counts(['project']) if @state == 'hidden'
   end
 
   def done_todos
</description>
  <from-support type="integer">1</from-support>
  <id type="integer">19563413</id>
  <importance type="integer">1290</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1250953</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1290</number>
  <priority type="integer">3</priority>
  <reporter-id>cF8gq42n4r3zEZab7jnrAJ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>actionize hidden project fails</summary>
  <updated-at type="datetime">2012-04-24T09:31:10Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">Small</estimate>
  <total-estimate type="float">1.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">defect</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">2.1</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">defect</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">2.1</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2012-05-11T21:04:10Z</created-on>
  <description>Hello,

I have started using tracks intensively a few days ago and ran into the following problem today.

Context:
* Hardware/O.S.: VMWare ESXi running on a dedicated server - guest O.S. is Debian 6, stock, bare install + SSH
* Application stack: tracks 2.1 from the current bitnami installer, no customisation

Symptoms:
After adding many deferred tasks to a huge project, and leaving the project page to another one, I became unable to get back to the project page: it triggers an error 500. I also cannot display the &quot;Deferred&quot; page anymore.

My analysis:
The bug seemed to appear when exceeding a given number of tasks in, either in one project or as a whole (my total is 284 right now, including 49 closed ones). Trying to display the list of deferred actions gives the following error trace in the production log:

Processing TodosController#list_deferred (for 212.198.178.7 at 2012-05-11 14:07:17) [GET]
Rendering template within layouts/standard
Rendering todos/list_deferred

ActionView::TemplateError (stack level too deep) on line #23 of app/views/todos/_successor.html.erb:
20:             :locals =&gt; { :todo =&gt; successor,
21:             :parent_container_type =&gt; parent_container_type,
22:             :suppress_dependencies =&gt; true,
23:             :predecessor =&gt; successor }
24:         %&gt;
25:         &lt;/div&gt;
26:       &lt;% end %&gt;

    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/_successor.html.erb:23
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/helpers/todos_helper.rb:76:in `collapsed_successors_image'
    app/helpers/todos_helper.rb:74:in `collapsed_successors_image'
    app/views/todos/_todo.html.erb:37
    app/views/contexts/_context.rhtml:18:in `_run_rhtml_app47views47contexts47_context46rhtml_locals_collapsible_context_context_counter_object'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    /opt/tracks-2.1-0/ruby/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in `method_missing'
    app/views/todos/list_deferred.html.erb:8
    app/controllers/todos_controller.rb:583:in `list_deferred'
    config/initializers/mongrel_workaround.rb:84:in `dispatch_cgi'

My hypothesis is this: I went over a threshold that triggers pagination when displaying tasks. Pagination doesn't work, be it because the will_paginate gem is buggy or because the installed version is incorrect, or because it is not used as intended (tracks bug). Another hypothesis would be circular referencing between actions but -1- I saw that there is an input check to prevent that, and -2- the whole project I was working on is very linear (action A depends on B, which depends on C, etc.) so it's very unlikely.

I file this as a major issue because it is a show stopper for some part of my work. All the planning done on the project that triggerred the bug is partially out of my reach now: I can only view the next actions using the mobile view, and I have no way to see/edit the deferred actions until I close the ones they depend on. I have been lucky enough to complete the whole planning before actually leaving the project page for the last time, so the situation could be worse, but still... I have other incoming projects like this one, and I can hardly devote efforts to tracks, knowing that projects might suddenly drop out of my reach.

I am, obviously, willing to provide any additional information you may require to help solving this issue.</description>
  <from-support type="integer">1</from-support>
  <id type="integer">21135583</id>
  <importance type="integer">1263</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1250953</milestone-id>
  <notification-list>cQhVaQM6Cr4y0dacwqjQWU</notification-list>
  <number type="integer">1295</number>
  <priority type="integer">3</priority>
  <reporter-id>cQhVaQM6Cr4y0dacwqjQWU</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Cannot display big project or deferred actions page (too many actions -&gt; pagination bug?)</summary>
  <updated-at type="datetime">2012-05-13T07:53:22Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">Small</estimate>
  <total-estimate type="float">1.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cQhVaQM6Cr4y0dacwqjQWU</id><login>detunizedgravity</login><login_name warning="deprecated">detunizedgravity</login_name><name>detunizedgravity</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">defect</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">2.1</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">defect</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">2.1</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>aUkc3w1Y0r4jEseJe4gwI3</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">6</component-id>
  <created-on type="datetime">2012-03-24T18:50:52Z</created-on>
  <description>I removed the test that failed with a TimeoutError.

&lt;pre&gt;&lt;code&gt;$ bundle exec rake cucumber RAILS_ENV=production
Please install RDoc 2.4.2+ to generate documentation.
config.gem: Unpacked gem aruba-0.2.2 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this.
/usr/bin/ruby1.8 -S bundle exec cucumber  --profile default
Using the default profile...
NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01.
Gem.source_index called from /usr/lib/ruby/gems/1.8/gems/rails-2.3.14/lib/rails/gem_dependency.rb:21.
config.gem: Unpacked gem aruba-0.2.2 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this.
.....................F----.........................................................F---......................................F----..............................................................................F--.....F--------..............F-.......................................F-----........F------..............................................F--......F-----------..------------......................---------......----------...F....----------......----------.F.F-------...F-----.....-------.........F--......F---.....F---....................................----.......F-..................................---.......------.............----........-------.....................................................................................................----..................................................................F.....................F--.........................................................................................................................................F----......F--........................................F..............................F-.....................F---......................................................F.................F------....................F-..........................................................................................................................F--...................................................F--.................................................F------...............................----.....-------.....---------.....--------.....---..........--------.---.....---.---........................-----....................---------......................--.................................--------.........F--.............................................-----....................................................................................................F-......................F--........F--..........................................................F--..................................................................................-----........-----....----........------...............................................................................------........................----....................---................................................................

(::) failed steps (::)
expected css &quot;a#delete_context_1&quot; not to return anything (Spec::Expectations::ExpectationNotMetError)
./features/step_definitions/context_list_steps.rb:11:in `/^I delete the context &quot;([^\&quot;]*)&quot;$/'
features/context_list.feature:70:in `When I delete the context &quot;@laptop&quot;'

expected css &quot;button#submit_context_1&quot; to return something (Spec::Expectations::ExpectationNotMetError)
./features/step_definitions/context_list_steps.rb:16:in `/^I edit the context to rename it to &quot;([^\&quot;]*)&quot;$/'
features/context_list.feature:79:in `And I edit the context to rename it to &quot;@ipad&quot;'

unknown error (Selenium::WebDriver::Error::JavascriptError)
./features/step_definitions/context_list_steps.rb:47:in `/^I drag context &quot;([^&quot;]*)&quot; above context &quot;([^&quot;]*)&quot;$/'
features/context_list.feature:115:in `When I drag context &quot;@home&quot; above context &quot;@ipad&quot;'
expected xpath &quot;//div[@id='message_holder']/h4[@id='flash']&quot; to return something (Spec::Expectations::ExpectationNotMetError)
./features/step_definitions/generic_steps.rb:20:in `/^I should see an error flash message saying &quot;([^&quot;]*)&quot;$/'
features/dependencies.feature:124:in `Then I should see an error flash message saying &quot;Cannot add this action as a dependency to a completed action!&quot;'

Unable to find xpath &quot;//div[@id='line_todo_2']/div/a[@class='show_successors']/img&quot; (Capybara::ElementNotFound)
(eval):2:in `send'
(eval):2:in `find'
./features/step_definitions/dependencies_steps.rb:24:in `/^I expand the dependencies of &quot;([^\&quot;]*)&quot;$/'
features/dependencies.feature:137:in `When I expand the dependencies of &quot;test 2&quot;'

Unable to find xpath &quot;//div[@id='line_todo_2']/div/a[@class='show_successors']/img&quot; (Capybara::ElementNotFound)
(eval):2:in `send'
(eval):2:in `find'
./features/step_definitions/dependencies_steps.rb:24:in `/^I expand the dependencies of &quot;([^\&quot;]*)&quot;$/'
features/dependencies.feature:137:in `When I expand the dependencies of &quot;test 2&quot;'

expected xpath &quot;//div[@id='tickler']//div[@id='line_todo_1']&quot; to return something (Spec::Expectations::ExpectationNotMetError)
./features/step_definitions/container_steps.rb:75:in `/^I should see &quot;([^&quot;]*)&quot; in the deferred container$/'
features/dependencies.feature:159:in `Then I should see &quot;test 1&quot; in the deferred container'

expected xpath &quot;//div[@id='tickler']//div[@id='line_todo_1']&quot; to return something (Spec::Expectations::ExpectationNotMetError)
./features/step_definitions/container_steps.rb:75:in `/^I should see &quot;([^&quot;]*)&quot; in the deferred container$/'
features/dependencies.feature:159:in `Then I should see &quot;test 1&quot; in the deferred container'
expected visible? to return true, got false (Spec::Expectations::ExpectationNotMetError)
./features/step_definitions/todo_steps.rb:151:in `send'
./features/step_definitions/todo_steps.rb:151:in `/^I should (see|not see) empty message for (completed todos|todos) of home/'
features/edit_a_todo.feature:83:in `And I should see empty message for todos of &lt;page type&gt;'

expected css &quot;div#no_todos_in_view&quot; not to return anything (Spec::Expectations::ExpectationNotMetError)
./features/step_definitions/todo_tag_steps.rb:2:in `/^I should not see empty message for todos of tag$/'
features/edit_a_todo.feature:123:in `And I should not see empty message for todos of &lt;page type&gt;'

expected visible? to return true, got false (Spec::Expectations::ExpectationNotMetError)
./features/step_definitions/todo_steps.rb:151:in `send'
./features/step_definitions/todo_steps.rb:151:in `/^I should (see|not see) empty message for (completed todos|todos) of home/'
features/edit_a_todo.feature:121:in `And I should see empty message for completed todos of &lt;page type&gt;'

expected visible? to return false, got true (Spec::Expectations::ExpectationNotMetError)
./features/step_definitions/project_steps.rb:212:in `send'
./features/step_definitions/project_steps.rb:212:in `/^I should (see|not see) empty message for (todos|deferred todos|completed todos) of project/'
features/edit_a_todo.feature:138:in `And I should not see empty message for todos of &lt;page type&gt;'


expected xpath &quot;//div[@id='completed_container']//a[@href='/todos/1.m']&quot; to return something (Spec::Expectations::ExpectationNotMetError)
./features/step_definitions/todo_steps.rb:146:in `/^I should see &quot;([^&quot;]*)&quot; in the completed section of the mobile site$/'
features/mobile_edit_a_todo.feature:32:in `Then I should see &quot;changed action&quot; in the completed section of the mobile site'

expected there to be content &quot;There are no incomplete actions&quot; in &quot;TRACKS::Login\n\n\n      The action 'test action' was deferred\n  \n\n\n  \n      The action 'test action' was deferred\n  \n\n  Please log in to use Tracks:\n\n\n  \n      \n        Login:\n            \n          Password:\n            \n          Stay logged in:\n            \n          \n            \n          \n  \n\n\n\n \n\n\nMobile Tracks 2.1devel (2012-03-24 10:55:17 +0100): Email | Website | Contribute  \n&quot; (Spec::Expectations::ExpectationNotMetError)
./features/step_definitions/web_steps.rb:110
./features/step_definitions/web_steps.rb:14:in `with_scope'
./features/step_definitions/web_steps.rb:108:in `/^(?:|I )should see &quot;([^&quot;]*)&quot;(?: within &quot;([^&quot;]*)&quot;)?$/'
features/mobile_edit_a_todo.feature:49:in `Then I should see &quot;There are no incomplete actions&quot;'

cannot fill in, no text field, text area or password field with id, name, or label 'value' found (Capybara::ElementNotFound)
(eval):2:in `send'
(eval):2:in `fill_in'
./features/step_definitions/project_steps.rb:152:in `/^I edit the project name in place to be &quot;([^&quot;]*)&quot;$/'
features/project_edit.feature:30:in `And I edit the project name in place to be &quot;release tracks 2.0&quot;'

expected css &quot;div#project_name&gt;form&gt;input&quot; to return something (Spec::Expectations::ExpectationNotMetError)
./features/step_definitions/project_steps.rb:223:in `/^I should be able to change the project name in place$/'
features/project_edit.feature:41:in `Then I should be able to change the project name in place'

expected there to be content &quot;Name already exists&quot; in &quot;2 Saturday, 24 March 2012\nToggle collapsed contexts  |  Toggle notes  |  Logout (testuser) \nHome\nStarred\nProjects\nTickler\nOrganize\nView\nAdmin\n?\nProject saved\n2 Last Active Projects\nSort \nAlphabetically\n | \nBy number of tasks\nmanage me (0 actions)\ntest (1 action)\n Hide form\nName:\n\nDescription (optional):\n\nDefault context (optional):\n\nDefault Tags (optional):\n\nAdd Project\nTake me to the new project page\nSend feedback on 2.1devel (2012-03-24 10:55:17 +0100): Bugs | Forum | Wiki | Email | Website | Contribute&quot; (Spec::Expectations::ExpectationNotMetError)
./features/step_definitions/web_steps.rb:110
./features/step_definitions/web_steps.rb:14:in `with_scope'
./features/step_definitions/web_steps.rb:108:in `/^(?:|I )should see &quot;([^&quot;]*)&quot;(?: within &quot;([^&quot;]*)&quot;)?$/'
features/project_edit.feature:88:in `Then I should see &quot;Name already exists&quot;'

expected there to be content &quot;manage him&quot; in &quot;3 Saturday, 24 March 2012\nToggle collapsed contexts  |  Toggle notes  |  Logout (testuser) \nHome\nStarred\nProjects\nTickler\nOrganize\nView\nAdmin\n?\n3 Last Active Projects\nSort \nAlphabetically\n | \nBy number of tasks\nmanage me (0 actions)\nupgrade jquery (0 actions)\na project name starting with a (0 actions)\n Hide form\nName:\n\nDescription (optional):\n\nDefault Tags (optional):\n\nAdd Project\nTake me to the new project page\nSend feedback on 2.1devel (2012-03-24 10:55:17 +0100): Bugs | Forum | Wiki | Email | Website | Contribute&quot; (Spec::Expectations::ExpectationNotMetError)
./features/step_definitions/web_steps.rb:110
./features/step_definitions/web_steps.rb:14:in `with_scope'
./features/step_definitions/web_steps.rb:108:in `/^(?:|I )should see &quot;([^&quot;]*)&quot;(?: within &quot;([^&quot;]*)&quot;)?$/'
features/project_list.feature:31:in `Then I should see &quot;manage him&quot;'

expected there to be content &quot;manage him&quot; in &quot;3 Last Active Projects\nSort \nAlphabetically\n | \nBy number of tasks\nmanage me (0 actions)\nupgrade jquery (0 actions)\na project name starting with a (0 actions)&quot; (Spec::Expectations::ExpectationNotMetError)
./features/step_definitions/web_steps.rb:110
./features/step_definitions/web_steps.rb:14:in `with_scope'
./features/step_definitions/web_steps.rb:108:in `/^(?:|I )should see &quot;([^&quot;]*)&quot;(?: within &quot;([^&quot;]*)&quot;)?$/'
features/project_list.feature:46:in `Then I should see a project named &quot;manage him&quot;'

unknown error (Selenium::WebDriver::Error::JavascriptError)
./features/step_definitions/project_list_steps.rb:22:in `/^I drag the project &quot;([^&quot;]*)&quot; below &quot;([^&quot;]*)&quot;$/'
features/project_list.feature:69:in `When I drag the project &quot;manage me&quot; below &quot;upgrade jquery&quot;'

Element is not currently visible and so may not be interacted with (Selenium::WebDriver::Error::ElementNotVisibleError)
[remote server] file:///tmp/webdriver-profile20120324-8486-bngevc/extensions/fxdriver@googlecode.com/components/command_processor.js:9509:in `unknown'
[remote server] file:///tmp/webdriver-profile20120324-8486-bngevc/extensions/fxdriver@googlecode.com/components/command_processor.js:10510:in `unknown'
[remote server] file:///tmp/webdriver-profile20120324-8486-bngevc/extensions/fxdriver@googlecode.com/components/command_processor.js:10529:in `unknown'
[remote server] file:///tmp/webdriver-profile20120324-8486-bngevc/extensions/fxdriver@googlecode.com/components/command_processor.js:10534:in `unknown'
[remote server] file:///tmp/webdriver-profile20120324-8486-bngevc/extensions/fxdriver@googlecode.com/components/command_processor.js:10482:in `unknown'
(eval):2:in `send'
(eval):2:in `fill_in'
./features/step_definitions/recurring_todo_steps.rb:47:in `/^I edit the name of the pattern &quot;([^\&quot;]*)&quot; to &quot;([^\&quot;]*)&quot;$/'
features/recurring_todos.feature:37:in `And I edit the name of the pattern &quot;run tests&quot; to &quot;report test results&quot;'


Failing Scenarios:
cucumber features/calendar.feature:27 # Scenario: Clearing the due date of a todo will remove it from the calendar
cucumber features/context_edit.feature:41 # Scenario: Editing the context of the last todo will remove the todo and show empty message
cucumber features/context_edit.feature:76 # Scenario: Moving the todo to the tickler will move todo to tickler container and update empty messages
cucumber features/context_list.feature:66 # Scenario: Delete context from context page right after an edit
cucumber features/context_list.feature:75 # Scenario: Edit context from context twice
cucumber features/context_list.feature:107 # Scenario: I can drag and drop to order the contexts
cucumber features/dependencies.feature:13 # Scenario: Adding dependency to dependency by drag and drop
cucumber features/dependencies.feature:27 # Scenario: I can edit a todo to add the todo as a dependency to another
cucumber features/dependencies.feature:96 # Scenario: Deleting a successor will update predecessor
cucumber features/dependencies.feature:115 # Scenario: Dragging an action to a completed action will not add it as a dependency
cucumber features/dependencies.feature:128 # Scenario: Marking a successor as complete will update predecessor
cucumber features/dependencies.feature:128 # Scenario: Marking a successor as complete will update predecessor
cucumber features/dependencies.feature:150 # Scenario: Marking a successor as active will update predecessor
cucumber features/dependencies.feature:150 # Scenario: Marking a successor as active will update predecessor
cucumber features/edit_a_todo.feature:53 # Scenario: Deleting the last todo in container will show empty message # only project, context, tag, not todo
cucumber features/edit_a_todo.feature:53 # Scenario: Deleting the last todo in container will show empty message # only project, context, tag, not todo
cucumber features/edit_a_todo.feature:53 # Scenario: Deleting the last todo in container will show empty message # only project, context, tag, not todo
cucumber features/edit_a_todo.feature:74 # Scenario: I can mark an active todo complete and it will update empty messages
cucumber features/edit_a_todo.feature:74 # Scenario: I can mark an active todo complete and it will update empty messages
cucumber features/edit_a_todo.feature:94 # Scenario: I can mark a deferred todo complete and it will update empty messages
cucumber features/edit_a_todo.feature:113 # Scenario: I can mark a completed todo active and it will update empty messages and context containers
cucumber features/edit_a_todo.feature:113 # Scenario: I can mark a completed todo active and it will update empty messages and context containers
cucumber features/edit_a_todo.feature:131 # Scenario: I can mark a completed todo active and it will update empty messages for pages without context containers
cucumber features/edit_a_todo.feature:146 # Scenario: I can edit a todo to change its description
cucumber features/edit_a_todo.feature:146 # Scenario: I can edit a todo to change its description
cucumber features/edit_a_todo.feature:146 # Scenario: I can edit a todo to change its description
cucumber features/edit_a_todo.feature:162 # Scenario: I can edit a todo to move it to another context
cucumber features/edit_a_todo.feature:180 # Scenario: I can edit a todo to move it to another context in tickler page
cucumber features/edit_a_todo.feature:193 # Scenario: I can edit a todo to move it to another project
cucumber features/edit_a_todo.feature:203 # Scenario: I can edit a todo to move it to the tickler
cucumber features/edit_a_todo.feature:270 # Scenario: Editing the context of a todo to a new context will show new context
cucumber features/edit_a_todo.feature:282 # Scenario: Editing the context of a todo in the tickler to a new context will show new context
cucumber features/mobile_edit_a_todo.feature:18 # Scenario: I can edit an action on the mobile page
cucumber features/mobile_edit_a_todo.feature:43 # Scenario: I can defer an action on the mobile page
cucumber features/project_edit.feature:27 # Scenario: I can edit the project name in place
cucumber features/project_edit.feature:37 # Scenario: I cannot edit the project name in two places at once
cucumber features/project_edit.feature:83 # Scenario: I cannot change the name of a project in the project list view to the name of another existing project
cucumber features/project_edit.feature:113 # Scenario: Cancelling editing a project will restore project settings
cucumber features/project_edit.feature:136 # Scenario: Moving the todo out of the tickler will move todo to active container and update empty messages
cucumber features/project_list.feature:28 # Scenario: Editing a project name will update the list
cucumber features/project_list.feature:42 # Scenario: Deleting a project after a edit will remove it from the list
cucumber features/project_list.feature:66 # Scenario: Dragging a project to change list order of projects
cucumber features/recurring_todos.feature:35 # Scenario: I can edit a repeat pattern
cucumber features/recurring_todos.feature:82 # Scenario: Deleting a recurring todo with active pattern will show new todo
cucumber features/search.feature:28 # Scenario: I can edit found todos
cucumber features/shared_add_new_todo.feature:101 # Scenario: I can add multiple todos from several pages
cucumber features/shared_add_new_todo.feature:101 # Scenario: I can add multiple todos from several pages
cucumber features/shared_add_new_todo.feature:101 # Scenario: I can add multiple todos from several pages
cucumber features/shared_add_new_todo.feature:159 # Scenario: Adding a todo to a hidden project does not show the todo
cucumber features/shared_add_new_todo.feature:212 # Scenario: Adding a dependency to a todo updates the successor
cucumber features/shared_add_new_todo.feature:212 # Scenario: Adding a dependency to a todo updates the successor
cucumber features/shared_add_new_todo.feature:228 # Scenario: Adding a dependency to a todo in another project
cucumber features/tagging_todos.feature:19 # Scenario: I can remove a tag from a todo from the tag view and the todo will be removed
cucumber features/tagging_todos.feature:39 # Scenario: I can move a tagged todo in tag view to a hidden project and it will move the todo on the page to the hidden container
cucumber features/tagging_todos.feature:49 # Scenario: I can move a tagged todo in tag view to a hidden context and it will move the todo on the page to the hidden container
cucumber features/tickler.feature:33 # Scenario: Editing the context of a todo moves it to the new context

340 scenarios (56 failed, 284 passed)
3234 steps (56 failed, 151 skipped, 3027 passed)
21m58.714s
rake aborted!
Command failed with status (1): [/usr/bin/ruby1.8 -S bundle exec cucumber  ...]

(See full trace by running task with --trace)
$ 
&lt;/code&gt;&lt;/pre&gt;
</description>
  <from-support type="integer">1</from-support>
  <id type="integer">17584563</id>
  <importance type="integer">1</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">410880</milestone-id>
  <notification-list>aUkc3w1Y0r4jEseJe4gwI3,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1261</number>
  <priority type="integer">3</priority>
  <reporter-id>aUkc3w1Y0r4jEseJe4gwI3</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>cucumber tests fail</summary>
  <updated-at type="datetime">2012-05-19T08:31:16Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>aUkc3w1Y0r4jEseJe4gwI3</id><login>popsch</login><login_name warning="deprecated">popsch</login_name><name>popsch</name></assigned-to>
  <reporter><id>aUkc3w1Y0r4jEseJe4gwI3</id><login>popsch</login><login_name warning="deprecated">popsch</login_name><name>popsch</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">defect</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">defect</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2012-04-20T07:40:14Z</created-on>
  <description>works for rails 3:

current_user.contexts.joins(:todos).group(&quot;contexts.id&quot;).where(&quot;todos.state='active'&quot;).count

improve where for active todos</description>
  <from-support type="integer">1</from-support>
  <id type="integer">19225923</id>
  <importance type="integer">1287</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">410880</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1287</number>
  <priority type="integer">3</priority>
  <reporter-id>cF8gq42n4r3zEZab7jnrAJ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>project and context todo count improvement</summary>
  <updated-at type="datetime">2012-04-20T07:40:15Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">Small</estimate>
  <total-estimate type="float">1.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2012-04-20T21:05:47Z</created-on>
  <description>Was working on the fast ui patch and found this: [[url:http://touchpunch.furf.com/|http://touchpunch.furf.com/]]

It's a drop in jquery library that enables drag and drop on touch screen devices by simulating the corresponding mouse events.  Works for me on my iPad (1st generation) with the fast UI interface, although dragging feels a little sluggish.  Better than not having it.

Trivial patch against stock 2.1 attached (patch includes the new library, both big and minified and a one-line update to layouts/standard.html.erb to include it)

Remember to delete public/stylesheets/jquery-cached.js after installing!

Could someone please try this on an Android device?

</description>
  <from-support type="integer">1</from-support>
  <id type="integer">19274183</id>
  <importance type="integer">1288</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">410880</milestone-id>
  <notification-list>c8JmGwsZCr4jRTeJe5cbLA,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1288</number>
  <priority type="integer">3</priority>
  <reporter-id>c8JmGwsZCr4jRTeJe5cbLA</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Make drag and drop work on touch screens</summary>
  <updated-at type="datetime">2012-05-10T21:03:40Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">Small</estimate>
  <total-estimate type="float">1.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></assigned-to>
  <reporter><id>c8JmGwsZCr4jRTeJe5cbLA</id><login>cfrankct</login><login_name warning="deprecated">cfrankct</login_name><name>cfrankct</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Resolution" id="3082">worksforme</custom-field>
<custom-field type="Text" name="Keywords" id="3083">Touch Screen Drag Drop</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Resolution" id="3082">worksforme</CustomField>
<CustomField type="Text" name="Keywords" id="3083">Touch Screen Drag Drop</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">10</component-id>
  <created-on type="datetime">2012-05-11T21:24:20Z</created-on>
  <description></description>
  <from-support type="integer">1</from-support>
  <id type="integer">21136893</id>
  <importance type="integer">1289</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">410880</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1296</number>
  <priority type="integer">3</priority>
  <reporter-id>cF8gq42n4r3zEZab7jnrAJ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Missing translation on mobile notes page of todo</summary>
  <updated-at type="datetime">2012-05-11T21:24:20Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">Small</estimate>
  <total-estimate type="float">1.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">2.1</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">2.1</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>bAHywc2B4r3yj4ab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">10</component-id>
  <created-on type="datetime">2012-05-12T04:13:14Z</created-on>
  <description>the model for recurring todos uses 'common.days' but this does not exist. 'common.days_midsentence.other' seems to fit the bill. This commit fixes: https://github.com/maddentim/tracks/commit/75744a9abfcce78a0d1681a3deefeca4c166ceda
I attached this to an existing pull request. I seem to still have only read only access to TracksApp on github. Maybe I am doing something wrong...</description>
  <from-support type="integer">1</from-support>
  <id type="integer">21144313</id>
  <importance type="integer">1290</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">410880</milestone-id>
  <notification-list>bAHywc2B4r3yj4ab7jnrAJ</notification-list>
  <number type="integer">1297</number>
  <priority type="integer">3</priority>
  <reporter-id>bAHywc2B4r3yj4ab7jnrAJ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Translation broken for 'days' on recurring todos listing</summary>
  <updated-at type="datetime">2012-05-13T14:16:02Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">Small</estimate>
  <total-estimate type="float">1.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>bAHywc2B4r3yj4ab7jnrAJ</id><login>maddentim</login><login_name warning="deprecated">maddentim</login_name><name>maddentim</name></assigned-to>
  <reporter><id>bAHywc2B4r3yj4ab7jnrAJ</id><login>maddentim</login><login_name warning="deprecated">maddentim</login_name><name>maddentim</name></reporter>
<custom-fields>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2012-05-16T13:11:51Z</created-on>
  <description>translate does not work well (or not at all) under rails3

tolk is well maintained: https://github.com/tolk/tolk</description>
  <from-support type="integer">1</from-support>
  <id type="integer">21407723</id>
  <importance type="integer">1291</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">410880</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1298</number>
  <priority type="integer">3</priority>
  <reporter-id>cF8gq42n4r3zEZab7jnrAJ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>consider tolk to replace translate for i18n</summary>
  <updated-at type="datetime">2012-05-16T13:11:51Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">Small</estimate>
  <total-estimate type="float">1.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2006-03-17T21:19:55Z</created-on>
  <description>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.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240383</id>
  <importance type="integer">4</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">233</number>
  <priority type="integer">2</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>add a 'followup' button next to 'delete' and 'edit'</summary>
  <updated-at type="datetime">2012-04-16T11:34:16Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084"></custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084"></CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2008-02-20T10:59:31Z</created-on>
  <description>When a context becomes irrelevant, you can either delete it or hide it. I'd like to keep the context for archive / statistics or for re-use if it becomes relevant again. 

So deleting a context is not a good option, especially because all related actions will be deleted too. Therefore I currently hide all contexts that are 'done'. But some contexts like someday/maybe are hidden too. This gets confusing when you have a lot of hidden contexts

So I propose a separate state for contexts: 'Done' which acts just like 'Done' for projects. You can hide it from view, but seperate it from hidden contexts.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240802</id>
  <importance type="integer">5</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">645</number>
  <priority type="integer">2</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>add 'Done' state to contexts</summary>
  <updated-at type="datetime">2012-04-16T12:09:12Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084"></custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084"></CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2008-11-11T12:59:59Z</created-on>
  <description>the problem:

sometimes, as time goes by, an action gets unnecessary. the currently available actions in such a situation are quite unhandy:[[br]]
- delete: the action was planned for some reason and it needed some time to process. but when the action is deleted, this effort gets lost in the weekly review and on the statistics page. additionally you could simply forget why the action became unnecessary, since you can't just add a note in the description field.[[br]]
- mark action as completed: though you can add a note why you dropped the action, but it will be wrongly treated as &quot;completed&quot;.

the idea:[[br]]
therefore i propose a special state (e.g. action dropped) to move the action off the list of active actions, without deleting it (maybe moving it to a separate section at the bottom of the list. like for &quot;Completed Actions&quot;).[[br]]
So the &quot;dropped&quot; tasks could also be reviewed (just by re-reading them, or even with special statistics).

work-around:[[br]]
currently I use a tag &quot;dropped&quot; when closing a wrongly created action. but since it's logically wrong and lacks of reviewability, I hope to see it in a future version of Tracks.

also see discussion at: &quot;regards[[br]&quot;:http://www.rousette.org.uk/projects/forums/viewthread/294/]

best
amarillo</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240949</id>
  <importance type="integer">3</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">790</number>
  <priority type="integer">2</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>add a &quot;dropped&quot;-state for actions</summary>
  <updated-at type="datetime">2012-04-16T12:09:12Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084"></custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084"></CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2010-08-06T08:44:50Z</created-on>
  <description>from #1001:

Tracks is not allowing such a default context to be changed to blank. It gets reset to the originally defined, first letter capitalised context.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1857231</id>
  <importance type="integer">2</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1058</number>
  <priority type="integer">2</priority>
  <reporter-id>cF8gq42n4r3zEZab7jnrAJ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Tracks is not allowing default context to be changed to blank</summary>
  <updated-at type="datetime">2012-04-16T11:34:34Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2011-01-01T17:42:55Z</created-on>
  <description>todo.hidden? looks at todo.state, context.hidden? and project.hidden?
moving a todo to a hidden project sets the state of the todo to project_hidden
moving a todo to a hdden context does not change the state

I'd propose to use only one hidden state for todo that is set when a todo is added/moved to a hidden project or a hidden context. This cleans up a lot of logic trying to figure out if the todo is hidden or not (including named scopes of todo)</description>
  <from-support type="integer">0</from-support>
  <id type="integer">2846703</id>
  <importance type="integer">1</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1082</number>
  <priority type="integer">2</priority>
  <reporter-id>cF8gq42n4r3zEZab7jnrAJ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>get consistent hidden states</summary>
  <updated-at type="datetime">2012-04-16T11:34:39Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2005-09-02T01:12:51Z</created-on>
  <description>There should be a system default &quot;Someday Maybe&quot; context where you can create items that never become stale, or turn all kinds of scary and alarming colors.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240253</id>
  <importance type="integer">19</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">114</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>A smart &quot;Someday Maybe&quot; context.</summary>
  <updated-at type="datetime">2012-04-16T11:35:09Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084"></custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084"></CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-08-02T08:11:24Z</created-on>
  <description>I'm coming from kGTD, and one of the things I really miss is the grouping of tasks in a certain project by context. Right now Tracks just shows me a list with with all contexts mixed. I often decide to work on a certain project, in a certain context, and right now it isn't very clear what I can and can't do.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240499</id>
  <importance type="integer">23</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">344</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>group tasks by context in project view</summary>
  <updated-at type="datetime">2012-04-16T11:34:50Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084"></custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084"></CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2007-05-16T02:36:33Z</created-on>
  <description>bsag on the mailing list:

&quot;In a more general vein, I've been looking at the Project pages  
recently, and thinking that it looks a bit busy. Again, I'm not  
criticising the work that anyone has done - it's just that we've got  
a lot more elements on the page now, with the default context, status  
of the project etc., and to me, it feels like there's a bit too much  
going on. Unfortunately, I don't have any easy ways to fix it, but  
I'll have a think about it.&quot;</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240672</id>
  <importance type="integer">22</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">515</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Project page UI needs to be streamlined</summary>
  <updated-at type="datetime">2012-04-16T12:09:42Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084"></custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084"></CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2008-01-06T23:13:11Z</created-on>
  <description>Its a little cumbersome to delete project notes right now.. you have to show the note first, then click the delete link. You should be able to delete them right on the project page, and nuke it with AJAX.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240782</id>
  <importance type="integer">21</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">625</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Delete Project Notes directly on Project Page</summary>
  <updated-at type="datetime">2012-04-16T11:34:56Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2008-01-12T21:49:28Z</created-on>
  <description>Let's also emit JSON format for project/context/todo lists and individual items. </description>
  <from-support type="integer">0</from-support>
  <id type="integer">240786</id>
  <importance type="integer">18</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ,bgwl_cUj4r4l7keJe5cbLr,c9n3zqjnqr4jRUeJe5cbLr</notification-list>
  <number type="integer">629</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Enhance REST api with JSON support</summary>
  <updated-at type="datetime">2012-04-16T11:35:14Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2008-01-19T17:35:31Z</created-on>
  <description>Could you show the created_at column when displaying or editing todos?  Maybe this could be a preference or maybe the user could just add this to the notes if he wants to track it.  I'm now using trunk and it's fabulous!

Thanks,

Jason</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240792</id>
  <importance type="integer">3</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">635</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Show created_at on todo items.</summary>
  <updated-at type="datetime">2012-04-16T11:36:22Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084"></custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084"></CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">6</component-id>
  <created-on type="datetime">2010-03-06T21:42:14Z</created-on>
  <description>Recurring todos have a huge amount of frontend and model code. This needs a comprehensive test suite.

I'm working on cleaning up the model and views in a branch at http://github.com/epall/tracks/tree/recurring-cleanup, but I can't really ensure things are working without comprehensive tests. I already broke some functionality in the jQuery re-write, so this has all ready been a problem for us.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1056933</id>
  <importance type="integer">17</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>c3AHgC1Wyr3A5uab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1006</number>
  <priority type="integer">3</priority>
  <reporter-id>c3AHgC1Wyr3A5uab7jnrAJ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Write comprehensive tests for recurring todos</summary>
  <updated-at type="datetime">2012-04-16T11:35:21Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>c3AHgC1Wyr3A5uab7jnrAJ</id><login>epall</login><login_name warning="deprecated">epall</login_name><name>epall</name><website>http://hackerengineer.net/</website></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">major</custom-field>
<custom-field type="Text" name="Keywords" id="3083">recurring-todos</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">major</CustomField>
<CustomField type="Text" name="Keywords" id="3083">recurring-todos</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2011-03-25T12:48:15Z</created-on>
  <description>I have been thinking tracks should provide some keyboard shortcut.  Might be good for accessibility purposes too.  Right now if you are on a page with the todo form, the page loads with the description focused.  If you leave the form, you can get back to the form by pressing tab and can move through the form from field to field with more tabs.  Access keys are defined for a number of menu items so that an ALT + p takes you to the projects list page.
Some enhancements could be:
* shortcut to focus on the first todo on the page.  (thinking of the way a google search result page does on load.  the first result has a &gt; next to it...) 
* you could then nav through todos with the arrows.  
* once on a todo, pressing 'd' toggles the complete.
* hitting a number defers it so many days.
* 'e' opens the edit form
* 's' stars it.
A jquery plugin to facilitate this could be[[url:https://github.com/jeresig/jquery.hotkeys| this https://github.com/jeresig/jquery.hotkeys ]] 
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">3460959</id>
  <importance type="integer">4</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>bAHywc2B4r3yj4ab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1134</number>
  <priority type="integer">3</priority>
  <reporter-id>bAHywc2B4r3yj4ab7jnrAJ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Keyboard Shortcuts</summary>
  <updated-at type="datetime">2012-04-16T11:36:18Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bAHywc2B4r3yj4ab7jnrAJ</id><login>maddentim</login><login_name warning="deprecated">maddentim</login_name><name>maddentim</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2011-05-01T15:07:29Z</created-on>
  <description>The results from auto-complete do not put the match that has the exact prefix on top.

This bothers me, because my system has an unique two-letter code for each context to quickly enter actions. For example, I have the following contexts:
sc Steven - Computer
mc Meike - Computer
ac Allebei - Computer
Ongesorteerde acties

The last context is used to dump actions in for later processing. Now, suppose I enter a new action that I want to put in &quot;Allebei - Computer&quot;. I'm used to typing &quot;ac&quot; in the context field, waiting for auto-complete to offer suggestions and then hit return to accept the first match. However, the first match will not be &quot;ac Allebei - Computer&quot; (the expected result) but &quot;Ongesorteerde acties&quot; (which also contains 'ac').

What should the sort order be? Am I right that exact prefixes should be preferred? Where in the code is this dealt with?</description>
  <from-support type="integer">0</from-support>
  <id type="integer">3749128</id>
  <importance type="integer">20</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>cx3kSs6Xir3z4Pab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ,aQmhwCB_Sr4kgfeJe5cbCb</notification-list>
  <number type="integer">1161</number>
  <priority type="integer">3</priority>
  <reporter-id>cx3kSs6Xir3z4Pab7jnrAJ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Auto-complete sort does not prefer exactly matching prefix</summary>
  <updated-at type="datetime">2012-04-16T11:35:04Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cx3kSs6Xir3z4Pab7jnrAJ</id><login>zteven</login><login_name warning="deprecated">zteven</login_name><name>zteven</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">2.0RC2</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">2.0RC2</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">10</component-id>
  <created-on type="datetime">2011-05-02T18:21:00Z</created-on>
  <description>the de.yml localization file uses different representation of umlauts. The hex variant like \xC3\xB6 (for &#246;) is often used instead of the human readable HTML versions like &amp;ouml; (this is: &amp;Ouml; for &#214;, &amp;auml; for &#228;, etc.)</description>
  <from-support type="integer">0</from-support>
  <id type="integer">3756020</id>
  <importance type="integer">1</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1163</number>
  <priority type="integer">3</priority>
  <reporter-id>aQmhwCB_Sr4kgfeJe5cbCb</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>mixed usage of \x__ and &amp;_uml; syntax in de.yml locale</summary>
  <updated-at type="datetime">2012-04-16T11:36:33Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aQmhwCB_Sr4kgfeJe5cbCb</id><login>voxspox</login><login_name warning="deprecated">voxspox</login_name><name>voxspox</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">2.0RC2</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">2.0RC2</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2011-09-04T19:41:53Z</created-on>
  <description>script/console &lt;&lt;EOF
class Context &lt; ActiveResource::Base; end 
Context.site = &quot;http://localhost:3000/&quot;
Context.site.user = &quot;username&quot;
Context.site.password = CGI.escape &quot;password&quot;
a = Context.find :first
a.save
EOF

Returns this error:

NoMethodError: undefined method `name' for nil:NilClass
	from /opt/local/lib/ruby/gems/1.8/gems/activesupport-2.3.14/lib/active_support/whiny_nil.rb:52:in `method_missing'
	from /opt/local/lib/ruby/gems/1.8/gems/activesupport-2.3.14/lib/active_support/xml_mini/rexml.rb:29:in `merge_element!'
	from /opt/local/lib/ruby/gems/1.8/gems/activesupport-2.3.14/lib/active_support/xml_mini/rexml.rb:18:in `parse'
	from /opt/local/lib/ruby/gems/1.8/gems/activesupport-2.3.14/lib/active_support/xml_mini.rb:12:in `__send__'
	from /opt/local/lib/ruby/gems/1.8/gems/activesupport-2.3.14/lib/active_support/xml_mini.rb:12:in `parse'
	from /opt/local/lib/ruby/gems/1.8/gems/activesupport-2.3.14/lib/active_support/core_ext/hash/conversions.rb:164:in `from_xml'
	from /opt/local/lib/ruby/gems/1.8/gems/activeresource-2.3.14/lib/active_resource/formats/xml_format.rb:19:in `decode'
	from /opt/local/lib/ruby/gems/1.8/gems/activeresource-2.3.14/lib/active_resource/base.rb:1092:in `load_attributes_from_response'
	from /opt/local/lib/ruby/gems/1.8/gems/activeresource-2.3.14/lib/active_resource/base.rb:1078:in `update'
	from /opt/local/lib/ruby/gems/1.8/gems/activeresource-2.3.14/lib/active_resource/base.rb:1077:in `tap'
	from /opt/local/lib/ruby/gems/1.8/gems/activeresource-2.3.14/lib/active_resource/base.rb:1077:in `update'
	from /opt/local/lib/ruby/gems/1.8/gems/activeresource-2.3.14/lib/active_resource/base.rb:867:in `save_without_validation'
	from /opt/local/lib/ruby/gems/1.8/gems/activeresource-2.3.14/lib/active_resource/validations.rb:259:in `save'
	from (irb):6</description>
  <from-support type="integer">0</from-support>
  <id type="integer">5982101</id>
  <importance type="integer">13</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>aUkc3w1Y0r4jEseJe4gwI3,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1190</number>
  <priority type="integer">3</priority>
  <reporter-id>aUkc3w1Y0r4jEseJe4gwI3</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>save() function fails in console script</summary>
  <updated-at type="datetime">2012-04-16T11:35:33Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aUkc3w1Y0r4jEseJe4gwI3</id><login>popsch</login><login_name warning="deprecated">popsch</login_name><name>popsch</name></reporter>
<custom-fields>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="Text" name="Keywords" id="3083">console scripting</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="Text" name="Keywords" id="3083">console scripting</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">8</component-id>
  <created-on type="datetime">2011-10-09T05:32:09Z</created-on>
  <description>Tracks needs some performance benchmark to start detect possible improvements. When you have 700+ projects (mix of closed and active), then tracks will become unbearably slow.

It's easy to try out: just add lots of projects using the template script in /docs/
 </description>
  <from-support type="integer">0</from-support>
  <id type="integer">7830743</id>
  <importance type="integer">12</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>aUkc3w1Y0r4jEseJe4gwI3,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1216</number>
  <priority type="integer">3</priority>
  <reporter-id>aUkc3w1Y0r4jEseJe4gwI3</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>benchmark</summary>
  <updated-at type="datetime">2012-04-16T11:35:39Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aUkc3w1Y0r4jEseJe4gwI3</id><login>popsch</login><login_name warning="deprecated">popsch</login_name><name>popsch</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2011-10-28T00:33:51Z</created-on>
  <description>This may be related to #759 and/or #1212.

Problem:
Less-important actions can pile up, and the staleness indicator loses its impact.

Solution:
Create an option to reset staleness on an action.

Example:
During my review, I find a task that hasn't been completed in two weeks. It's marked as stale, but it can wait another week or two. I don't want to defer it (move to tickler, remove from visible actions list), because I might get to it this week, but I don't want it to appear stale because it isn't very important. I click the action's drop-down, and select &quot;Touch&quot;; The staleness counter is reset for that action, and I can focus on more important things.</description>
  <from-support type="integer">1</from-support>
  <id type="integer">9030443</id>
  <importance type="integer">2</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>dBhRJk790r4ilSacwqjQWU,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1219</number>
  <priority type="integer">3</priority>
  <reporter-id>dBhRJk790r4ilSacwqjQWU</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>option to reset staleness of action</summary>
  <updated-at type="datetime">2012-04-16T11:36:28Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dBhRJk790r4ilSacwqjQWU</id><login>meznak</login><login_name warning="deprecated">meznak</login_name><name>Nathan Plamondon</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2011-11-04T04:54:18Z</created-on>
  <description>It would be nice to have the most frequently used actions for projects not hidden inside the ''Edit project settings&quot; form. The following actions come to mind:

* Mark as reviewed (also listed in #1212)
* Mark as complete
* Set 'show from' to 14 days in the future ('show from' should be implemented for projects; #942)

This patch provides the 'set reviewed'. If you like it, I can look into more actions.



&lt;pre&gt;&lt;code&gt;diff --git a/app/views/projects/_project_settings.rhtml b/app/views/projects/_pr
index df0f759..e09528c 100644
--- a/app/views/projects/_project_settings.rhtml
+++ b/app/views/projects/_project_settings.rhtml
@@ -24,3 +24,10 @@
 &lt;div id=&quot;&lt;%= dom_id(project, 'edit') %&gt;&quot; class=&quot;edit-form&quot; style=&quot;display:none;
    &lt;div class=&quot;placeholder&quot;&gt; &lt;/div&gt;
 &lt;/div&gt;
+
+&lt;div class=&quot;project_settings&quot;&gt; 
+  Quickactions: &lt;a href=&quot;&lt;%=set_reviewed_project_path(project)%&gt;&quot; id=&quot;&lt;%= dom_i
+  &lt;%=image_tag(&quot;reviewed.png&quot;, :alt =&gt; &quot;&quot;) %&gt;
+  Reviewed
+&lt;/a&gt;
+&lt;/div&gt;

&lt;/code&gt;&lt;/pre&gt;
</description>
  <from-support type="integer">1</from-support>
  <id type="integer">9369263</id>
  <importance type="integer">11</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>aUkc3w1Y0r4jEseJe4gwI3,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1220</number>
  <priority type="integer">3</priority>
  <reporter-id>aUkc3w1Y0r4jEseJe4gwI3</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Quickactions for project view</summary>
  <updated-at type="datetime">2012-04-16T11:35:45Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aUkc3w1Y0r4jEseJe4gwI3</id><login>popsch</login><login_name warning="deprecated">popsch</login_name><name>popsch</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2012-01-12T19:30:40Z</created-on>
  <description>There are multiple reasons why one wants to find todos without an assigned project:

* They have some future 'show from' date set and get lost in the database
* They don't show up in the review mode
* One might want to complete the information

This ticket should serve to start the discussion on how to handle the todos without an assigned project. Any ideas?</description>
  <from-support type="integer">1</from-support>
  <id type="integer">12787283</id>
  <importance type="integer">9</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>aUkc3w1Y0r4jEseJe4gwI3,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1235</number>
  <priority type="integer">3</priority>
  <reporter-id>aUkc3w1Y0r4jEseJe4gwI3</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>todos without a assigned project are hard to find</summary>
  <updated-at type="datetime">2012-04-16T11:35:52Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aUkc3w1Y0r4jEseJe4gwI3</id><login>popsch</login><login_name warning="deprecated">popsch</login_name><name>popsch</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2012-02-19T05:16:38Z</created-on>
  <description>The the drop down menu for todos accounts for 25-30% of the rendering time for todos/index. I tested this by removing the menu (see the diff) and running on a database with &gt;120 todos visible on the todo/index page. There should be a way to optimize the javascript/ruby conglomerate for the menu. Can we create one menu in the file and call the menu with a parameter  instead of duplicating the code for each todo? 

&lt;pre&gt;&lt;code&gt;--- a/app/views/todos/_todo.html.erb
+++ b/app/views/todos/_todo.html.erb
@@ -11,20 +11,6 @@ parameters += &quot;&amp;_tag_name=#{@tag_name}&quot; if @source_view == 'tag'
     &lt;%= remote_star_icon(todo) %&gt;
     &lt;%= remote_toggle_checkbox(todo) %&gt;
     &lt;%= remote_edit_button(todo) unless suppress_edit_button %&gt;
-    &lt;ul class=&quot;sf-menu sf-item-menu&quot;&gt;
-      &lt;li style=&quot;z-index:&lt;%=@z_index_counter%&gt;&quot;&gt;&lt;%= image_tag &quot;downarrow.png&quot;, :alt=&gt; &quot;&quot; %&gt;
-        &lt;ul id=&quot;ul&lt;%= dom_id(todo) %&gt;&quot;&gt;
-          &lt;li&gt;&lt;%= remote_delete_menu_item(todo) %&gt;&lt;/li&gt;
-          &lt;% unless todo.completed? || todo.deferred? -%&gt;
-            &lt;li&gt;&lt;%= remote_defer_menu_item(1, todo) %&gt;&lt;/li&gt;
-            &lt;li&gt;&lt;%= remote_defer_menu_item(2, todo) %&gt;&lt;/li&gt;
-            &lt;li&gt;&lt;%= remote_defer_menu_item(3, todo) %&gt;&lt;/li&gt;
-            &lt;li&gt;&lt;%= remote_defer_menu_item(7, todo) %&gt;&lt;/li&gt;
-            &lt;li&gt;&lt;%= remote_promote_to_project_menu_item(todo) %&gt;&lt;/li&gt;
-          &lt;% end -%&gt;
-        &lt;/ul&gt;
-      &lt;/li&gt;
-    &lt;/ul&gt;
     &lt;%= grip_span(todo) %&gt;
     &lt;div class=&quot;description&lt;%= staleness_class( todo ) %&gt;&quot;&gt;
       &lt;%= date_span(todo) -%&gt;
&lt;/code&gt;&lt;/pre&gt;</description>
  <from-support type="integer">1</from-support>
  <id type="integer">15270193</id>
  <importance type="integer">8</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>aUkc3w1Y0r4jEseJe4gwI3,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ,c8JmGwsZCr4jRTeJe5cbLA</notification-list>
  <number type="integer">1249</number>
  <priority type="integer">3</priority>
  <reporter-id>aUkc3w1Y0r4jEseJe4gwI3</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>replacing the dropdown menu with faster code</summary>
  <updated-at type="datetime">2012-04-18T22:43:17Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aUkc3w1Y0r4jEseJe4gwI3</id><login>popsch</login><login_name warning="deprecated">popsch</login_name><name>popsch</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">minor</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">minor</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2012-04-05T16:18:44Z</created-on>
  <description>I use the recurring todos feature frequently in my usage of the app.  Often though, my recurrence is the next recurrence to start a specific time period following the completion of the prior todo instead of at a specific point in the month or week. For example, say I needed to clean a filter on something every 6 months, but, in practice, I might not get to it until a month after I should have. Shame on me, but hey, at least I did it! In this case, I really don't need the next cleaning to occur in 5 months, but in 6 from the last completion.

So, I will look into implementing a new recurrence pattern based this logic. I have not looked into it yet, but have it in my job jar todo.

I am assuming that I will need to work in these:
* app/views/recurring_todos
* app/controllers/recurring_todos_controller.rb
Let me know if this is something of interest and if you have any pointers on what needs to be done.</description>
  <from-support type="integer">1</from-support>
  <id type="integer">18366083</id>
  <importance type="integer">6</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>bAHywc2B4r3yj4ab7jnrAJ,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1270</number>
  <priority type="integer">3</priority>
  <reporter-id>bAHywc2B4r3yj4ab7jnrAJ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>New Recurring Todo feature: new recurrence in X days/weeks/etc.</summary>
  <updated-at type="datetime">2012-04-16T11:36:06Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bAHywc2B4r3yj4ab7jnrAJ</id><login>maddentim</login><login_name warning="deprecated">maddentim</login_name><name>maddentim</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2012-04-05T20:48:00Z</created-on>
  <description>The current wording at the bottom of the recurring todo edit window is confusing.  Initial proposal is to replace it with
&lt;pre&gt;&lt;code&gt;Use the computation to set the action's
[] 'Show from' date (do not set a due date)
[] Due date.  Show the action:
     [] always
     [] not until [ ] days before the due date
&lt;/code&gt;&lt;/pre&gt;
(ticket opened at Reinier's request based on discussion in [[url:http://www.assembla.com/spaces/tracks-tickets/tickets/1270|#1270]])</description>
  <from-support type="integer">1</from-support>
  <id type="integer">18383183</id>
  <importance type="integer">5</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>c8JmGwsZCr4jRTeJe5cbLA,cF8gq42n4r3zEZab7jnrAJ,aQmhwCB_Sr4kgfeJe5cbCb</notification-list>
  <number type="integer">1273</number>
  <priority type="integer">3</priority>
  <reporter-id>c8JmGwsZCr4jRTeJe5cbLA</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Clarify wording in recurring todo UI (setting of due_date vs show_from_date)</summary>
  <updated-at type="datetime">2012-04-16T11:36:11Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>c8JmGwsZCr4jRTeJe5cbLA</id><login>cfrankct</login><login_name warning="deprecated">cfrankct</login_name><name>cfrankct</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">minor</custom-field>
<custom-field type="Text" name="Keywords" id="3083">recurring, ui</custom-field>
<custom-field type="List" name="Version" id="3084">2.1RC1</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">minor</CustomField>
<CustomField type="Text" name="Keywords" id="3083">recurring, ui</CustomField>
<CustomField type="List" name="Version" id="3084">2.1RC1</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2012-04-12T22:03:10Z</created-on>
  <description>Reinier,

the pre-rendered notes did not make a big difference on my machine, it still took 4.5 server seconds to re-load the homepage with 105 actions.  That was virtually unchanged from the previous times.  I suspect it is because only ~15% of my actions have notes, and I don't use markup in them.

However, it inspired me to mock up a faster UI, based on Popsch's observation that the dropdown menu takes a long time to render.  With the new UI my home page loads in 2.7 server seconds, a 40% improvement.  Rendering is also marginally faster, but I have a fast machine to begin with, so it's less of an issue.

The new UI gets rid of the dropdown menu and the edit button.  The todo description is now a link that activates the edit menu.  That should improve tablet usability since you don't have to try to hit the small pencil icon.  In the edit menu I have moved the buttons from the bottom to the top, and added the buttons for defer 1,2,3,7 days, delete and promote to project, so the dropdown functions are still there.

All of this seems to work, and renders fast.  Where I was hoping to get some help is hooking up the defer / delete / promote buttons to the backend functionality.  There is too much call-back / remote magic in the helper for me to update, but I suspect Reinier can hook these up very quickly.

About the only drawback I can see that the defer buttons now take two clicks, rather than a click and a drag.

Attached the diff of 2.1RC, it's not very intrusive and limited to a few files, but if you want to take it in a different direction or defer to 2.2 I won't be offended.  
</description>
  <from-support type="integer">1</from-support>
  <id type="integer">18759003</id>
  <importance type="integer">1279</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>c8JmGwsZCr4jRTeJe5cbLA,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1279</number>
  <priority type="integer">3</priority>
  <reporter-id>c8JmGwsZCr4jRTeJe5cbLA</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Patch for faster UI and better tablet usability</summary>
  <updated-at type="datetime">2012-04-20T20:41:18Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">Small</estimate>
  <total-estimate type="float">1.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>c8JmGwsZCr4jRTeJe5cbLA</id><login>cfrankct</login><login_name warning="deprecated">cfrankct</login_name><name>cfrankct</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">2.1RC1</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">2.1RC1</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2009-02-24T21:44:16Z</created-on>
  <description>Per this note in the forums:

http://www.getontracks.org/forums/viewthread/336/

Please consider adding the ability for users to add selector tags to RSS feed urls to allow for the creation of custom feeds.  Thanks!</description>
  <from-support type="integer">0</from-support>
  <id type="integer">290132</id>
  <importance type="integer">2</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>cw4_VCaRSr3QekeJe5aVNr,cF8gq42n4r3zEZab7jnrAJ,c9n3zqjnqr4jRUeJe5cbLr</notification-list>
  <number type="integer">845</number>
  <priority type="integer">4</priority>
  <reporter-id>cw4_VCaRSr3QekeJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>addition of selectors to feed urls</summary>
  <updated-at type="datetime">2012-04-16T11:36:41Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cw4_VCaRSr3QekeJe5aVNr</id><login>ckolar</login><login_name warning="deprecated">ckolar</login_name><name>ckolar</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083">txt feed</custom-field>
<custom-field type="List" name="Version" id="3084">1.7RC</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083">txt feed</CustomField>
<CustomField type="List" name="Version" id="3084">1.7RC</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2011-01-20T20:38:08Z</created-on>
  <description>Hi,

the change-auth-type functionality has broken javascript. Furthermore you cannot enter an identity url when signing up and the app failes if you only enter one.
Right now I have a first commit in https://github.com/02strich/tracks/commit/c2d9c68c691aa0655337098296de12f99977e600, and I will see how the tests work out.

One question remains for me: is it a good idea to be able to only use openId auth?

-Stefan</description>
  <from-support type="integer">0</from-support>
  <id type="integer">2978827</id>
  <importance type="integer">2</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>c9n3zqjnqr4jRUeJe5cbLr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1087</number>
  <priority type="integer">4</priority>
  <reporter-id>c9n3zqjnqr4jRUeJe5cbLr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Bugs with OpenID auth: change_auth_scheme and signup broken</summary>
  <updated-at type="datetime">2012-04-19T10:34:37Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>c9n3zqjnqr4jRUeJe5cbLr</id><login>02strich</login><login_name warning="deprecated">02strich</login_name><name>02strich</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">defect</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">defect</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2010-08-06T08:46:48Z</created-on>
  <description>from the comments of #1001

creating a context &quot;Context1&quot;, then specifying the non-existent &quot;context1&quot; as a context in a task, causes a message to pop up asking to create the new context. However, in this case - no new context is created, and the task is given &quot;Context1&quot;.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1857237</id>
  <importance type="integer">1</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">1234383</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ,bgwl_cUj4r4l7keJe5cbLr</notification-list>
  <number type="integer">1059</number>
  <priority type="integer">5</priority>
  <reporter-id>cF8gq42n4r3zEZab7jnrAJ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Finding a context is case insensitive while Tracks assumes case sensitivty</summary>
  <updated-at type="datetime">2012-04-16T11:37:10Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">minor</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">minor</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2005-04-02T06:15:21Z</created-on>
  <description>Would it be possible to add a Wiki section into Tracks? That would make it an all-in-one webapp for me to use as a single data collection inbox.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240151</id>
  <importance type="integer">92</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">17</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>integration of a wiki into Tracks</summary>
  <updated-at type="datetime">2012-04-06T12:18:56Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2005-04-27T06:49:43Z</created-on>
  <description>I've integrated true multi-user functionality using sessions and some database mods into a previous version of Tracks.  I will be submitting a patch after making appropriate modifications to the current trunk.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240181</id>
  <importance type="integer">4</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>beAXGWk5ir35jEeJe5aVNr,bgfq4qA1Gr2QjIaaaHk9wZ,cF8gq42n4r3zEZab7jnrAJ,bJxdBEGXar4yo2acwqjQXA</notification-list>
  <number type="integer">47</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>True Multi-User Capability</summary>
  <updated-at type="datetime">2012-04-21T16:49:38Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2005-04-29T12:29:31Z</created-on>
  <description>It will be convenient to do assignment of responsible persons for task</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240183</id>
  <importance type="integer">1</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">49</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Do assignment of responsible persons</summary>
  <updated-at type="datetime">2012-04-16T12:10:28Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2005-07-14T05:50:50Z</created-on>
  <description>When I create a project, I'd like to pick a default context to use for its next actions.  My &quot;update online portfolio&quot; 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 &quot;[verb] [direct object] [prepositions] [indirect object]&quot;.  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 &quot;call&quot; or &quot;phone&quot; trigger the calls context, such as &quot;call Johnson about lack of TPS reports.&quot;
 * Ditto for &quot;email&quot;.
 * Words like &quot;buy&quot;, &quot;fetch&quot;, and &quot;drop off&quot; trigger the errands context.
 * Because Kelly's hobby is woodworking, she has created a woodshop context, and defined its trigger verbs as &quot;build&quot;, &quot;saw&quot;, and &quot;varnish&quot;.

What do you think?</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240220</id>
  <importance type="integer">15</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">83</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Ideas for better context selection</summary>
  <updated-at type="datetime">2012-04-16T12:10:20Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2005-07-29T12:57:08Z</created-on>
  <description>Would it be possible to give users the ability to reorder next actions in the same way that projects can be reordered?</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240228</id>
  <importance type="integer">14</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">91</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Reorder next actions</summary>
  <updated-at type="datetime">2012-04-16T12:10:19Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2005-08-07T02:55:39Z</created-on>
  <description>Add the following to one to the appropiate model after releasing 1.04.

&lt;pre&gt;&lt;code&gt;
select p.name, p.id, COUNT(t.project_id) AS count FROM projects p, todos t 
WHERE t.project_id IS NOT NULL AND t.done=0 
AND p.done h1. * t.project_id GROUP BY p.id;
}}}

Consider moving the sidebar management into a seperate controller. This might allow us to set up some clever OSX/dashboard widgets or small popups.

Select the above for a list of projects by:
{{{
  p.id IN #{projectids.join(&quot;,&quot;)}
&lt;/code&gt;&lt;/pre&gt;
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240234</id>
  <importance type="integer">91</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">97</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Smarter sidebar</summary>
  <updated-at type="datetime">2012-04-16T12:09:18Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2005-08-10T11:52:34Z</created-on>
  <description>I'm a convert from GTDTiddlyWiki and I found that I like Tracks better, but it didn't feel right. After some thinking I found out that this is because the 'Home' page is too overwhelming with all the lists showing by default. Working with only one context showing would be better, but it's harder to reach these, because they are below the projects list.
But if you take GTD, then contexts are way more important than Projects, so I don't really see why they're at the top.

I changed the ordering myself in app/views/project/show.rhtml, app/views/context/show.rhtml and app/views/todo/list.rhtml and it seems much nicer to me :)</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240241</id>
  <importance type="integer">12</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">103</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Context at top in sidebar</summary>
  <updated-at type="datetime">2012-04-16T12:10:17Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2005-08-25T17:28:16Z</created-on>
  <description>I use actions for my web-based bookmarks (@read, @buy etc.) and it would cool to be able to pull those specific tag feeds into the sidebar. Not being a ruby person I have no idea how to implement this :(</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240245</id>
  <importance type="integer">13</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">107</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>display feed in sidebar</summary>
  <updated-at type="datetime">2012-04-16T12:10:18Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2005-09-08T20:50:19Z</created-on>
  <description>Would anyone else find it useful to have a grid view, with configurable columns, that could be sorted by any column?  I'd love to work on it myself, but I just don't have the time.  I keep finding myself wanting to be able to view all tasks by project on the same screen, rather than by context.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240257</id>
  <importance type="integer">11</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">117</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Feature Request: Grid View of actions</summary>
  <updated-at type="datetime">2012-04-16T12:10:17Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2005-09-30T09:58:20Z</created-on>
  <description>It would be nice if i could move a complete project on to another context. Sometimes i park a complete project in Someday/Maybe (see also [#114]), and if this become active i would like to change the Context of all associated Actions.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240265</id>
  <importance type="integer">90</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">125</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Move complete project to another context</summary>
  <updated-at type="datetime">2011-02-08T09:03:06Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2005-12-10T06:08:47Z</created-on>
  <description>so as i do stuff, i need to go through the list of projects where there are no actions and assign new actions.

this is problematic when there are 80 projects, a lot of time is spent hunting for projects with 0 next actions.

so a view with projects with no assigned actions with an interface that allows easy adding of next actions would make easier ensuring all projects have some next action assigned.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240322</id>
  <importance type="integer">10</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">175</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>view for projects with no active next actions.</summary>
  <updated-at type="datetime">2012-04-06T12:12:38Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2005-12-12T20:30:42Z</created-on>
  <description>i think it'd be great to have a way to choose a task that is currently in progress and have that appear on all pages.  this can be an anchor of sorts.  i often find myself doing something and then getting distracted and ending up doing something else. so being reminded of what i set out to do can help me stay on task.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240324</id>
  <importance type="integer">88</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">177</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>currnetly working on item:</summary>
  <updated-at type="datetime">2012-04-16T12:09:18Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2005-12-29T17:59:22Z</created-on>
  <description>I would like to add tree relationships to Contexts and Projects.  Contexts can have other contexts as their parents, and projects can have other projects as their parents (but a context cannot have a project as a parent and v.v.).  

For example, the context &quot;WidgetCorp Account&quot; could be a child of the context &quot;Work,&quot; and the project &quot;Update Documentation&quot; could be a child of the project &quot;Prepare Client Deliverable.&quot;  

I would be willing to implement this.  How the various views would be modified, and what additional views would be added, would need to be fleshed out.  </description>
  <from-support type="integer">0</from-support>
  <id type="integer">240330</id>
  <importance type="integer">87</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">183</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Adding Tree (Parent/Child) Relationships to Contexts &amp; Projects</summary>
  <updated-at type="datetime">2012-04-16T12:09:19Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2006-01-05T08:07:02Z</created-on>
  <description>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.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240335</id>
  <importance type="integer">9</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">188</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>New notes view is redundant</summary>
  <updated-at type="datetime">2012-04-16T12:10:22Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2006-01-15T15:19:09Z</created-on>
  <description>I find it hard to see some of my tasks in contexts that are not related to a project when there are many tasks in the same context that are associated to projects.

I basically have to look for tasks that do not have a [P] beside them, but it would be more clear if there were a way to toggle viewing project related tasks on or off in a context view.

Thank you,

Gino</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240346</id>
  <importance type="integer">86</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">197</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Should be able to hide all project related tasks in context view</summary>
  <updated-at type="datetime">2012-04-16T12:09:20Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-02-13T10:47:27Z</created-on>
  <description>It would be _really_ nice if someone with more Gentoo knowledge than me could get Tracks into portage.

I've spent hours installing it and trying to persuade it to talk consistently to MySQL, and being able to type 'emerge tracks' and have it Just Work certainly has its attractions :)</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240355</id>
  <importance type="integer">3</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>bBp5Jm2mOr3yFdab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">206</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Gentoo ebuild</summary>
  <updated-at type="datetime">2012-04-06T12:18:57Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-02-17T13:21:16Z</created-on>
  <description>Hello,

I got to this project because of my recent interests in rails. However, I don't know anything about GDT (and have been looking for some more information about this).

Maybe you could provide some more information on the GDT concepts (or a small 'tutorial' on how to use Tracks) on the wiki?</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240360</id>
  <importance type="integer">8</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">211</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>provide some information on GTD concepts?</summary>
  <updated-at type="datetime">2012-04-16T12:10:21Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2006-03-20T13:56:06Z</created-on>
  <description>I would like Tracks to have a &quot;Hipster PDA&quot; composer function.  Format output for 3x5, vertical in my mind but maybe horizontal.  Print 4 to a page or direct to 3x5.

Projects, one per card.

NextAction lists, one context per card (or if @home is too big, a second card would be fine).

Consider when in NextAction cards it should also put the { Project } it is associated with, appended to the NextAction.

Listing as Design/Apperance because I think the bits are still there, just needs to have a VIEW defined for this.  </description>
  <from-support type="integer">0</from-support>
  <id type="integer">240386</id>
  <importance type="integer">7</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">236</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Req: Tracks as Hipster Composer</summary>
  <updated-at type="datetime">2012-04-16T12:10:26Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-03-25T15:06:23Z</created-on>
  <description>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 &quot;Sell house&quot;. From the &quot;Contexts&quot; list you select &quot;At Computer&quot;. You click the reply button and email your agent a counter offer. When you send it, instead of going to &quot;Sent Mail&quot;, a copy goes to &quot;Waiting&quot;.

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.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240391</id>
  <importance type="integer">6</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">240</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>email management</summary>
  <updated-at type="datetime">2012-04-16T12:10:26Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-05-03T22:23:08Z</created-on>
  <description>It would be nice to supplement task description with esimation of duration (say, in minutes) required for this task to be completed.

It would help in deciding what task could be taken for work at the moment and to estimate what effort need to be done to accomplish context or project (in addition to # of tasks displayed at the very top of the page).

Small 3-digit box near task description in &quot;Add a next action&quot; menu would be enough.

One more related feature is to allow fixation of elapsed time (in similar 3-digit box near task description in context or home page).

That would facilitate in creation of activity reports (how did I spend a day). They are not timesheets in any case but may help to understand in what task(s) I invested (wasted) so much time also serving as a source for time management improvement.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240429</id>
  <importance type="integer">85</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">276</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>add duration estimation for activity</summary>
  <updated-at type="datetime">2012-04-16T12:09:20Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-05-18T23:11:14Z</created-on>
  <description>I want a feture of re-arranging action items in a project , and reflecting the order in the feed list (and of course onscreen.)
In the feed list, I hope the items be sorted in Context&gt;Project&gt;'the order in the Project'.

Also I hope that the feed have the output pattern of 'top 5 of each Context', which will be handy if I send the feed to my celluphone for quick reference.
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240449</id>
  <importance type="integer">84</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">294</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>re-arranging action items and reflecting it in feed order</summary>
  <updated-at type="datetime">2012-04-06T12:18:57Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>bgfq4qA1Gr2QjIaaaHk9wZ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-05-23T15:19:53Z</created-on>
  <description>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.)</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240450</id>
  <importance type="integer">4</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>bgfq4qA1Gr2QjIaaaHk9wZ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">295</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Meta Refresh Prefrence on Main Page?</summary>
  <updated-at type="datetime">2012-04-16T12:10:30Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-06-12T04:09:24Z</created-on>
  <description>The ability to subscribe to a remote iCal in the project section.

</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240460</id>
  <importance type="integer">83</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">305</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Subscribe to a remote iCal To Do list</summary>
  <updated-at type="datetime">2012-04-16T12:09:27Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2006-06-24T05:59:26Z</created-on>
  <description>I'd like to see the ability to select multiple contexts in a single list.  I never seem to get to my &quot;@calls&quot; actions because they're way below the &quot;work&quot; and &quot;computer&quot; contexts on my home page.

What I'd like to see instead would be a way to select the contexts I can work on now and have them show the actions from all of those contexts in a single list.  The current sorting (and any future enhancements to it) would cause my older actions to filter to the top when I can work on them.

Combined with the feature requested in ticket:48 it would allow you to do some really neat things that are discussed in the book.  You could create time and effort contexts for example.  Then you could sit down at the computer at work between meetings for example and select @Work or @Computer actions that should only take @Time - 15m and see them all in the same list.

Perhaps the next day I'm working from home.  I could select @Work - Computer and @Home since I can get a few things done around the house.  Maybe its been a long week so I only want to select things that are @Easy.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240464</id>
  <importance type="integer">82</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,aKc-daaj0r4kW-eJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">309</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Display multiple contexts in a single list</summary>
  <updated-at type="datetime">2012-04-16T12:09:26Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-06-27T11:12:08Z</created-on>
  <description>I am a Mac user and during the last months I had tried to use kGTD that is built on OmniOutlinerPro as implementation of GTD. Last week I noticed the Tracks implementation and I was very happy to get things working so quickly. Moreover, Tracks does not depend on another commercial software (like OOP), so thats fine. 

One drawback of the Tracks solution is that the Applescript support is yet less developped than in kGTD. I noticed that Applescript support was implemented for the creation of new tasks. Thus I would like to mention that it would be a great enhancement for me if there would be an Applescript way to create a new project. However, I dont know how complicated this might be...

To illustrate the possible value of such a script, I just want to mention 2 ways in which I can speed up my GTD approach in kGTD:

1. Creation of Folders/Mailboxes etc. in different applications. 
I like to use the same project name for a mailbox in Apple&#180;s Mail.app and for a project folder in my documents folder where I collect  electronic documents related to the project. Thus I wrote a small Applescript that prompts for a project name and uses this name to create a new mailbox in Mail, a new folder on the disk, and a new project in kGTD. The applescript is started by a shortkey (using Butler), thus I can initiate a new project &quot;on the fly&quot;.

2. Project templates. 
As described in ticket #92, it is helpful to define some templates for similar projects. E. g., the organisation of a conference visit triggers a specific sequence of actions for the next six months for me (renewal of membership, submission of abstracts, travel planning, ...). So I wrote an Applescript that creates a new project and adds some predefined tasks into this project. From my point of view project templates need not be implemented within Tracks. If the creation of projects is facilitated via Applescript, it might be very easy to write a separate applescript for each template.


Of course, I would be happy to share the corresponding versions of the applescripts for Tracks with you, if there would be a way to create new projects via Applescript in Tracks.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240467</id>
  <importance type="integer">81</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">312</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Applescript for the creation of new projects?</summary>
  <updated-at type="datetime">2012-04-16T12:09:25Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-07-05T18:35:33Z</created-on>
  <description>Is there a way that the box for entering a due date could understand things like &quot;tomorrow,&quot; &quot;friday,&quot; &quot;in 2 weeks,&quot; etc.? In other words, it'd be great if I could use the same natural language to talk to Tracks as it uses to talk to me about due dates!
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240472</id>
  <importance type="integer">80</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">317</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>&quot;relative&quot; due date entry?</summary>
  <updated-at type="datetime">2012-04-16T12:09:25Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-07-17T06:01:53Z</created-on>
  <description>This would consist of a user preference to select among installed themes, plus a system for grouping css and images into a theme.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240479</id>
  <importance type="integer">79</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">324</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>User can apply a variety of visual themes</summary>
  <updated-at type="datetime">2012-04-16T12:09:24Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2006-08-11T22:25:32Z</created-on>
  <description>I'll be downloading and playing with Tracks as soon as I get home.  I'll probably host it both local and online (which gives rise to another task, to be recorded seperately)

Ideally, I'd be adding tasks to my family's accounts and they'd be adding tasks to  mine - but certainly I don't want all tasks to be public - nor do I want all team (rather than personally) tasks to be accepted automatically.

So - if my partner adds a task for me to fix the broken shelf on the bookcase, I'd like to accept it, and prioritize it correctly, or reject it. 

If I add a task to my babysitter's account, asking her to call and make a doctor's appointment with the pedi, I'd like to be able to see if it's accepted, completed, etc.

To me that implies both

1) logins authorized to add tasks - which would be given a status of submitted or pending, and other logins that are not permitted to submit tasks.

2) for logins that are permitted to submit tasks, the ability to review the status of their submitted tasks

3) public tasks that may be seen by all authorized members, and private tasks that are only visible to the account owner

4) in the context of teams - perhaps only tasks of a specified set that are also publicly visible, would be shown - that way the family can see family public tasks, the workgroup can see work public tasks, but not the opposit.  (For my purposes, this is less important, as I intend to use it only for my personal and family productivity.)</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240512</id>
  <importance type="integer">77</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">357</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>wish - team (family) wide tasking</summary>
  <updated-at type="datetime">2012-04-16T12:09:24Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2006-08-11T22:36:46Z</created-on>
  <description>I commute by train with my laptop - no internet access.  I also work at shops where I can't use my laptop, but have internet access.  I have a hosting account where I'll be hosting tracks for my family.  

I'd like to have a local laptop copy of tracks, so I can work with it offline - and I'd like it to sync with the hosted account, when I get back online.

I'm figuring a rest based web service, where, when you push the sync button, it gets all changed tasks from the online site, inserts new, marks complete, and updates based on timestamps.  Once the record sync was completed locally, it would put http the changes back to the host, including any new or updated tasks. 
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240513</id>
  <importance type="integer">76</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">358</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>sync offline laptop with online tracks</summary>
  <updated-at type="datetime">2012-04-16T12:09:24Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-08-24T21:00:47Z</created-on>
  <description>Another great addition to Tracs to bring it up a level would be a goals module where you could match up short term and long term goals with projects.  If implemented, it should also include the ability to match multiple projects per goal and multiple goals per project.  This would allow the higher level views which DA mentiones in the GTD book (30,000 ft. etc.)</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240526</id>
  <importance type="integer">75</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">371</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Goals</summary>
  <updated-at type="datetime">2012-04-06T12:18:57Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-08-28T06:23:51Z</created-on>
  <description>It would be nice if you could create subprojects under projects, and then add actions to those subprojects.  This would allow for tracking really BIG projects that must be broken down into their own smaller subprojects to be able to be managed effectively.  See GTD book pages 156-158.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240528</id>
  <importance type="integer">74</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">373</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Support for subprojects</summary>
  <updated-at type="datetime">2012-04-06T12:18:57Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>bgfq4qA1Gr2QjIaaaHk9wZ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-10-19T18:19:14Z</created-on>
  <description>When editing a prexisting action: if I change (or eliminate, or add) the due date, should it move to the proper place within that box? (Instantly, I mean: a refresh of the page resorts the actions already.)

I can see how this could possibly be confusing, but it would be consistent with the behavior that other edits (in name, context, project, etc.) are reflected immediately.

Tracks 1.042 on Camino 1.0.1</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240549</id>
  <importance type="integer">5</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>bgfq4qA1Gr2QjIaaaHk9wZ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">393</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>resort on change of due date?</summary>
  <updated-at type="datetime">2012-04-16T12:10:25Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2007-02-05T04:27:56Z</created-on>
  <description>Tracks currently has a periodic Ajax check for deferred actions that are ready to be shown. This check should also look for newly added actions, such as those added via the backend or REST APIs.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240590</id>
  <importance type="integer">2</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>c3AHgC1Wyr3A5uab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">434</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>periodic check should add new actions in addition to ready deferred ones</summary>
  <updated-at type="datetime">2012-04-06T12:18:57Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084"></custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084"></CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2007-02-23T10:47:07Z</created-on>
  <description>It would be nice to be able to synchronize my tracks data with my PocketPC or mobile phone. To make it possible there are a couple of simple things that could be done:    
 * add a &quot;date/time of last update&quot; field to todos, projects, contexts, ... tables,  and make sure this field is updated every time a record is changed or created.   
 * update the API so that it would be possible to get all records modified since a given date and to update a record with new information (but never allow the id field to be changed).

These steps leave out the deleted records which is a bit harder. To be able to track that it would be needed to have a table of deleted ids (and, again, date/time of deletion) and some API methods to get deleted records since a given date and to delete a record giving it's id.

These changes would be sufficient to enable synchronization between platforms and would enable the development of &quot;sometimes connected&quot; applications to enable taking our todos with us.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240608</id>
  <importance type="integer">3</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,bgwl_cUj4r4l7keJe5cbLr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">452</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Enable synchronization with mobile devices/other systems</summary>
  <updated-at type="datetime">2012-04-16T12:10:29Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2007-03-25T16:57:39Z</created-on>
  <description>- Show the name of the project next to the title and collapse the body (by default) so that the &quot;Notes&quot; section looks less cluttered and saves space. Clicking a &quot;+&quot; opens the note details.

- Project Status: Right now, even if a project is in hidden or completed state, notes associated with it are listed. Much better not to?

- Ordering: As of now ordering is on the time of creation. Maybe better to order based on project associated with the note? And once ordered on projects, the second order ordering could be the same as the ordering of projects in 'Projects' section?</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240635</id>
  <importance type="integer">73</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">478</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Enhancements to Notes section</summary>
  <updated-at type="datetime">2012-04-16T12:10:41Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2007-04-18T14:31:00Z</created-on>
  <description>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</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240660</id>
  <importance type="integer">2</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">503</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Notes with history</summary>
  <updated-at type="datetime">2012-04-16T12:10:28Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080"></custom-field>
<custom-field type="List" name="Severity" id="3081"></custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084"></custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080"></CustomField>
<CustomField type="List" name="Severity" id="3081"></CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084"></CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2007-04-23T01:52:51Z</created-on>
  <description>It would be nice to be able to create a new action from a bookmarklet putting the current URL in the note field, and perhaps using &quot;read &quot;+the title of the current page as the action name. Ideally would select the read/review context by default.

I'm thinking this would be better than #107 just because it would be really integrated, as opposed to just a sidebar. The whole point of GTD is that you only look at one thing, right? :)

Anyway, thanks for the awesome tool!</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240664</id>
  <importance type="integer">72</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">507</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>bookmarklet to create action including &quot;link:&quot;current url</summary>
  <updated-at type="datetime">2012-04-16T12:09:35Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2007-07-04T02:53:49Z</created-on>
  <description>It'd be nice to be able to attach and upload files to projects/actions such as &quot;Project Summary&quot; or &quot;Programme Budget&quot;... just a thought!
10x for the good work/service!  </description>
  <from-support type="integer">0</from-support>
  <id type="integer">240692</id>
  <importance type="integer">71</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">535</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Attaching files</summary>
  <updated-at type="datetime">2012-04-16T12:10:11Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084"></custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084"></CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2007-09-25T23:06:06Z</created-on>
  <description>BSAG

Hey, I am checking out tracks, and liking it so far, despite the hassle of getting to run on windows. I am currently using My Life Organized http://www.mylifeorganized.net/ as my GTD app. It has 3 panes, your Outline, your To-DO and your places (contexts with many features). 
Now, I like it's outlining features, as it allows you to organize and compartmentalize your planning and task tracking. For instance, Right now I 4 major areas of my Outline, a motivation, a Planning, Execution, and a &quot;Reference&quot;. WIthin the planning and and execution I have it divided into Roles, Professional &amp; creative and and Personal and home. Within those I various headers, inbox, quicklist, standalone events, single step actions, punchlists &amp; routines, etc. And way down there I have my Traditional GTD contexts as @calls, @computer, @errands, etc. 

You can also zoom in on a particular branch or area, say you only want to see/work with Professional &amp; Creative tasks.

I am attemping to do this via Tracks contexts, and it is leading to a rather long lists of contexts. Which brings me to request. MLO uses what it terms Places, which are essentially contexts. However they have two sets of handy properties. First, you can assign hours to each place. You can assign times when this context is open, and will show up in the ToDo list, and when it is closed. This is a very handy feature for setting working time, free time, home time, etc. The todo list also has a toggle to show closed places.  

The other big feature is that you have Places that include other places. So you can setup daily routines that are included in a larger Routines &amp; appointments category, You can have your todo list include various segments of work time. For instance, I have a weekly work time place that is made up of my morning workday, afternoon wrkday , evening workday. As well as for weekends. I also have my free time and home time categories. 

All of these are included in either my ToDo list or Routines &amp; appointments list. Thus, when I look at the To-Do pane under the relevant master place/context, It will show me only the tasks relevant to what I am doing. Or I can focus on specific contexts, such as the traditional @calls etc. (You can also toggle it show closed places, which often leads to information overload.)

So, in short, if you could implement these two features. First a feature allowing contexts to include other contexts. Second, a feature allowing you to assign open &amp; closed hours to a context, that'd make it much more useful as a planning/capturing tool. Especially if it would show the included contexts in a collapsible menu, and would allow you to focus on a particular branch of your outline/context list. 

thanks

Rob</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240721</id>
  <importance type="integer">70</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">564</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Some requested features inspired by My Life Organized</summary>
  <updated-at type="datetime">2011-02-08T09:15:41Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2007-09-26T05:13:14Z</created-on>
  <description>BSAG

hey, putting in my projects, and I notice that you have a dinky little description box, I feel it would be better used, and more GTD centric to use this space as a Successful Outcome box, and make it mandatory (or option to set it mandatory). Thereby requiring more GTD based thinking in creating projects. </description>
  <from-support type="integer">0</from-support>
  <id type="integer">240722</id>
  <importance type="integer">69</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">565</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Change project description field to 'Succesful Outcome&quot;, make it larger and mandatory.</summary>
  <updated-at type="datetime">2012-04-16T12:09:34Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2007-09-26T22:43:45Z</created-on>
  <description>Devteam

Hey, I am currently using a neat little applet called Bubbles, http://www.3d3r.com/bubbles/. It basically provides a mini-browser that runs in systray on windows. (Don't know of mac/linux alternative) I use it with Slimtimer and 30Boxes. Anyway, if we could get a mini-app built for bubbles, or something similar, to allow rapid task entry via a hotkey, similar to the way My Life Organized works, that would really improve  apps usefulness for rapid capture. </description>
  <from-support type="integer">0</from-support>
  <id type="integer">240725</id>
  <importance type="integer">68</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">568</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Add a Next Action Bookmarklet/Mini App that could be used with Bubbles?</summary>
  <updated-at type="datetime">2012-04-16T12:09:33Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2007-09-27T04:53:38Z</created-on>
  <description>Hey, I noticed that collapsing the context list, you lose a sense of how many tasks are in a context. I like apps that add a show me what I need sensibility to them. I think it would be useful if you could include a number of next actions indicator on the header, and maybe a little color block to show the next action with the lowest due date nearness. This way, you could collapse all of your context headers, but still get a good sense of where the bulk of your work lies, and you don't have to expand every context to remember how many tasks are in there. 

This would give you a nice quick at a glance overview of your next actions. I think this would help in setting your work priorities, weekly reviews, etc. </description>
  <from-support type="integer">0</from-support>
  <id type="integer">240726</id>
  <importance type="integer">67</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">569</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Add number of actions/due date color indicator to context lists header block, collapse all toggle</summary>
  <updated-at type="datetime">2012-04-16T12:09:33Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2007-09-27T05:42:41Z</created-on>
  <description>Devteam

Hey, having a tool tip to show the full text of the tags textbox would be handy, my tag sets are fairly lengthy, so not hving to click and End to read  them would help.

</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240728</id>
  <importance type="integer">66</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">571</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Add Tooltip to Tags textbox on Next Action form?</summary>
  <updated-at type="datetime">2011-02-08T09:15:57Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2007-09-27T05:48:07Z</created-on>
  <description>Devteam

So, I am thinking it would be handy if you had a short navbar at top of the indivdual Project pages with links to sections/entry blocks(next actions, defered actions, completed actions, notes, status), and a back to top link at the end of each section, to make data entry &amp; review quicker. On long task list you have to do some scrolling. </description>
  <from-support type="integer">0</from-support>
  <id type="integer">240729</id>
  <importance type="integer">65</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">572</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Add inpage anchor named links to projects/actions page?</summary>
  <updated-at type="datetime">2012-04-16T12:09:32Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>bgfq4qA1Gr2QjIaaaHk9wZ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2008-01-24T16:39:45Z</created-on>
  <description>So, yesterday an action came out of my tickler and into my main view, and I didn't notice it in my casual morning pass over the context it was in. I only noticed it later, when I actually could have taken care of it much earlier.

I'm not sure if this is properly GTD-y, or if I should just do better review ;) but it seems like it would be nice if (on the day something comes out of the tickler/is first shown) there was some sort of visual highlight in the main view that said 'hey, this is new- make sure you take a look!'</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240793</id>
  <importance type="integer">1</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>bgfq4qA1Gr2QjIaaaHk9wZ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">636</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>indication that an action has just 'come from' the tickler</summary>
  <updated-at type="datetime">2012-04-06T12:13:15Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2008-03-13T21:00:06Z</created-on>
  <description>At Tracks 1.5rc1 i have to clear the context field befor i get the drop down. This is really bad if i what to change the context. 

I suggest to open the context drop down ever when the user clicks to the context field and not changed the text.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240825</id>
  <importance type="integer">64</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">668</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Context drop-down should appear too if there is always an context</summary>
  <updated-at type="datetime">2012-04-16T12:09:32Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2008-03-31T09:20:57Z</created-on>
  <description>Does Tracks support encryption at present? If not, are the any unofficial hacks that people who need it resort to, such as using a different HTTP server, and are there plans to implement it? 

I reckon it'd be a pretty important feature; I wouldn't want the entire world to be able to sniff my traffic and learn what I'm up to.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240839</id>
  <importance type="integer">63</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">682</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Encryption?</summary>
  <updated-at type="datetime">2012-04-16T12:09:31Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2008-04-01T07:25:37Z</created-on>
  <description>I'd like for projects to have due dates and for these due dates to be used for their associated actions if the action doesn't have a due date explicitly set.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240844</id>
  <importance type="integer">62</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">686</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Add due dates for projects</summary>
  <updated-at type="datetime">2012-04-16T12:10:03Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2008-04-11T00:33:42Z</created-on>
  <description>Copied from Forum post (http://www.rousette.org.uk/projects/forums/viewthread/212/)

Based on my experience using What&#8217;s Next App, I think I have a suggestion on how to implement re-ordering of Next Actions that should be relatively easy to implement. Not sure if this has been suggested before.

As is (v1.5), I believe that Tracks display Next Actions (group by context) in the order of actions with earliest due date are shown first then actions with no due date are shown in the order they were created. Is this the case?

My suggestion is to have two views in the &#8216;home&#8217; page. One called &#8216;Normal&#8217; or &#8216;Sortable&#8217; and the other called &#8216;Due Date&#8217;. All Next Actions (with or without due date) will have an additional field (in the database) to record the ranking (or positioning order). When in &#8216;Normal/Sortable&#8217; view, all Next Actions (including those with due date) are sortable (within their respective context). So it is up to the user to re-order his Next Actions as he sees fit. To bring focus to actions that are due soon (or in the next few days), show on the right hand side bar &#8216;Actions due in the next 7 days&#8217;. This side bar will be filtered by a drop down combo box to select which context the actions belong to. So if you select &#8216;office&#8217; as the context, then only the actions with context &#8216;office&#8217; with due dates within the next 7 days are shown. This way user can sort next actions as he sees fit, and still be able to easily see actions with due dates approaching.

For those who like things the way they are, click on the &#8216;Due Date&#8217; view and the list will no longer be sortable, and will be displayed as it currently is, actions with nearest due dates before actions with no due dates which are sorted by date of creation. In this view, the list is not sortable, so when going back to the &#8216;Normal/Sortable&#8217; view, the list will again be shown in the order as it was left before.

For tickler tasks, when they need to be displayed, show them at the bottom of the list (in &#8216;Normal/Sortable&#8217; view, while in &#8216;Due Date&#8217; view will be shown depending on due date or creation date).

Moving a task to another context again will cause the task to be shown at the bottom of the list in the new context (in &#8216;Normal/Sortable&#8217; view), while all other tasks below this task in the original context will be moved up by one.

I hope I made myself clear. But I think this is not too difficult to implement. I can understand your problem with sortable action if you still want to show actions with nearest due date at the top. By having the sidebar view, this is no longer necessary. Of course if for those who like things the way it is, they can always default their view to &#8216;Due Date&#8217; and never click on the &#8216;Normal/Sortable&#8217; view. The sidebar view can be shown only in &#8216;Normal/Sortable&#8217; view or in both views although it won&#8217;t be of much use in &#8216;Due Date&#8217; view as the same information is already displayed in the lists themselves.

Check out What&#8217;s Next App (http://www.whatsnextapp.com) for what I meant regarding the side view bar showing actions due in the next 7 days. </description>
  <from-support type="integer">0</from-support>
  <id type="integer">240851</id>
  <importance type="integer">61</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">692</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Suggestions on implementation of sortable Next Actions</summary>
  <updated-at type="datetime">2012-04-16T12:09:31Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2008-05-23T06:58:09Z</created-on>
  <description>Instead of taking me to a new view when I click on the &quot;search icon&quot; which then shows the text box, couldn't we have a small dropdown textbox where we can fill in search query? </description>
  <from-support type="integer">0</from-support>
  <id type="integer">240874</id>
  <importance type="integer">60</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">715</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Dropdown textarea for Search</summary>
  <updated-at type="datetime">2012-04-16T12:09:30Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2008-06-16T09:36:45Z</created-on>
  <description>Alter the YAML export button so that it uses yaml_db. This produces a nicely formatted data.yml file which contains both schema and data for all the tables. This can be used to load the data into another installation via the command line, or to migrate from one database adapter to another. In future, we might be able to hook up import via the web UI, so that data could be imported the same way, but that requires a bit of cleverness with users.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240895</id>
  <importance type="integer">59</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">736</number>
  <priority type="integer">3</priority>
  <reporter-id>czFbRE0eSr3zoYab7jnrAJ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Alter YAML export to use yaml_db plugin</summary>
  <updated-at type="datetime">2012-04-06T12:18:58Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></assigned-to>
  <reporter><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084"></custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084"></CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2008-06-24T22:21:03Z</created-on>
  <description>I started a thread &quot;&quot;:http://www.rousette.org.uk/projects/forums/viewthread/242/ on the forum to find out if there was a way to enter a time value in the Due field. I received a reply to suggest it as a feature request... so here's the request: I would love to see a feature added that allows the addition of a due time added to the an action in the Due field. Thanks.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240900</id>
  <importance type="integer">58</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,dcBQMyccir3ORbeJe5aVNr,bgwl_cUj4r4l7keJe5cbLr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">741</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Possibility to enter a due time</summary>
  <updated-at type="datetime">2012-04-06T12:18:58Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2008-08-22T08:59:56Z</created-on>
  <description>It would be great if staleness could be restarted when something changes in an action, say going from &quot;computer&quot; to &quot;waiting for&quot; since what I care about is the time since I last touched something rather than how long I have worked on it. Related to this, it would also be good to be able to turn off staleness completely for actions in certain contexts (like &quot;agenda&quot; and &quot;someday/maybe&quot;).

Thanks for all the work,

Claus P</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240918</id>
  <importance type="integer">57</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">759</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Staleness options</summary>
  <updated-at type="datetime">2012-04-16T12:09:39Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2008-09-20T16:03:59Z</created-on>
  <description>Ideally the user should be able to apply one action (change due date to tomorrow) to multiple tasks at once. Without this feature, management of even medium sized accounts becomes tedious. It should be considered for the next major release.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240932</id>
  <importance type="integer">56</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">773</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Edit multiple tasks</summary>
  <updated-at type="datetime">2012-04-16T12:09:39Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2008-10-15T22:00:40Z</created-on>
  <description>Google notebook, and for years even php other other blog sites, have given users the ability to do WYSIWYG editing of their text...lets add this to tracks!

Often times i have either specs that i slap in questions into and by the time i'm done, its pages long...in the past ive highlighted my questions in color and the answer in another.

While you can do this using textile and such, its much more work.  Often times in meetings i have to write notes and my thoughts as quickly as possible as presenter keeps speaking.

Google notebook is probably one of the best, simplest examples with its folowing features:

1. Highlight blocks and then apply different format changes
1. Easy link builder (including mailto:)
1. Font class and font weight
1. Alignment
1. etc

This makes tracks much more usable as i believe something like this should be a one stop tool.  A GTD manager and integrated notes/files application.

Happy coding!
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240941</id>
  <importance type="integer">55</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">782</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>WYSIWYG Notes &amp; Action Editor</summary>
  <updated-at type="datetime">2011-02-08T09:17:43Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2008-10-15T22:07:23Z</created-on>
  <description>For me, notes are nearly 50% of my work flow and all work there after comes from those notes.  Lets beef up tracks and make it more complete by adding the concept of notes books that contain notes, list, etc rather than just &quot;one ofs&quot; that are hand cuffed to a project.

One should be able to create a notebook on a business subject and then throughout any project entry or action, reference that.  

Maybe a smart way to do that would be that you can create sections in a note book, then, in a project note or action you can easily reference that somehow in a way that when viewing that project note you could click on the reference and it would expand that section in whatever notebook.

Example:

&quot;So this is an example of a note in a project.  The requirements for this project are X, Y, B.  B is a very complicated, core business methodology that can be referenced here (here would be a enhanced link). Blah blah blah&quot;

So one would then click on here, and either a dialog friendly box would then come up that would allow you to see the reference material and project note.

Just some thoughts that would greatly improve my usage of tracks.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240942</id>
  <importance type="integer">54</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">783</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Notes &amp; Notebooks</summary>
  <updated-at type="datetime">2012-04-16T12:09:38Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2008-12-08T07:07:39Z</created-on>
  <description>Hi!

It would be useful if it was possible to:
* change authorization type
* change/edit OpenID
* disable users (so actions and project stay but user unable to add/edit anything)</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240959</id>
  <importance type="integer">53</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">800</number>
  <priority type="integer">3</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>User management</summary>
  <updated-at type="datetime">2012-04-06T12:18:58Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084"></custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084"></CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2009-01-17T09:04:50Z</created-on>
  <description>Patch
http://github.com/vitaliel/tracks/tree/feb3a44191721acfc29c9bb3085b467f51aa49db

It will makes todo list to look prettier.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">256595</id>
  <importance type="integer">52</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">828</number>
  <priority type="integer">3</priority>
  <reporter-id>cBtTkkPDir2O7YaaeP0Qfc</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[Patch] Convert first letter to upper case for todos.description</summary>
  <updated-at type="datetime">2012-04-16T12:09:38Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cBtTkkPDir2O7YaaeP0Qfc</id><login>lz</login><login_name warning="deprecated">lz</login_name><name>Vitalie Lazu</name><organization>Assembla</organization><website>http://vitalie.webng.md</website><first_im><type>none</type><id></id></first_im></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084">1.7</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084">1.7</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2009-02-09T17:45:26Z</created-on>
  <description>Just a thought here... As you all know, tracks supports attaching notes to individual todos as well as to projects.  The current implementation is not wysiwyg but does support using html tags to do basic formatting.  On other applications I have been using or experimenting with (namely wikimedia and drupal) I have been able to add wysiwyg support to text input fields.  There are two rich text editors that I have used that seem pretty robust - [[url:http://tinymce.moxiecode.com/index.php|TinyMCE]] and [[url:http://www.fckeditor.net/|FckEditor]].  I am interested to know if there is much interest in enabling this type of support in tracks?  
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">276426</id>
  <importance type="integer">51</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>bAHywc2B4r3yj4ab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">837</number>
  <priority type="integer">3</priority>
  <reporter-id>bAHywc2B4r3yj4ab7jnrAJ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>wysiwyg editor for notes</summary>
  <updated-at type="datetime">2012-04-06T12:18:58Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></assigned-to>
  <reporter><id>bAHywc2B4r3yj4ab7jnrAJ</id><login>maddentim</login><login_name warning="deprecated">maddentim</login_name><name>maddentim</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081"></custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084"></custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081"></CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084"></CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2009-02-12T15:16:02Z</created-on>
  <description>I installed the 1.7code from git w/ mysql/apache over this past weekend and love the software.  Unfortunately, if you add a bunch of tasks, projects, recurring tasks etc, then change your time zone, everything gets messed up a bit.  My fiance had an extreme version of this when she migrated over a hundred items from easy task manager to tracks then I pointed out the time zone issue.  She eventually had me create a new account for her so she could just start from scratch rather than try to fix everything.

For 1.7/1.8 perhaps a first time login feature could be added that brings a new user to the preferences tab with on of those slick looking popups to tell them to set their time zone.  Also, maybe some documentation on the install to help admins set their default time zone (I figured out how to do this after the fact.)

Further out, you may want to reconsider how you store the task data.  It seems that it would make more sense to store nearly all dates in terms of absolute time and have your store and query code calculate the offset on the fly.  This would allow for seamless transitions from one timezone to another.   Essentially let program logic tell you what day it is where you are, and the database doesn't bother storing hour/minute timezone stuff, just day/month/year.

Shit, come to think of it, the way time is stored also will also probably cause similar, but less serious issues during DST transitions.

Thank you for the software.  It's fabulous and helping me GTD!  I think I'll put a task in to contribute some documentation.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">279828</id>
  <importance type="integer">50</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>bs8LLc-rqr3BZveJe5afGb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">840</number>
  <priority type="integer">3</priority>
  <reporter-id>bs8LLc-rqr3BZveJe5afGb</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Changing preferences.time_zone mucks up data / setting default preferences.time_zone not easy</summary>
  <updated-at type="datetime">2011-02-08T09:17:59Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bs8LLc-rqr3BZveJe5afGb</id><login>sharefoo</login><login_name warning="deprecated">sharefoo</login_name><name>sharefoo</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081"></custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083">time zone</custom-field>
<custom-field type="List" name="Version" id="3084">1.7RC</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081"></CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083">time zone</CustomField>
<CustomField type="List" name="Version" id="3084">1.7RC</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2009-03-06T09:45:29Z</created-on>
  <description>I think it would be convenient to have possibility to see whole note on a project page like it is for action.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">298542</id>
  <importance type="integer">49</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>dcBQMyccir3ORbeJe5aVNr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">851</number>
  <priority type="integer">3</priority>
  <reporter-id>dcBQMyccir3ORbeJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>viewing notes from project view</summary>
  <updated-at type="datetime">2012-04-16T12:09:42Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dcBQMyccir3ORbeJe5aVNr</id><login>ciekawy</login><login_name warning="deprecated">ciekawy</login_name><name>ciekawy</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081"></custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084">1.7</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081"></CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084">1.7</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2009-03-21T04:29:48Z</created-on>
  <description>I do my weekly review (well, almost weekly reviews) by going through the projects I have. My problem is that a number of tasks really do not fit into any of my projects, mainly because they are smaller things that I need to do that will not be repeated. Tracks provides the &#8220;None&#8221; option for those, but if I choose that the tasks will not show up during my weekly review. Would it be possible to have None as an automatic active project in the next release of Tracks? I guess I could define a project and dump stuff into that, but thought others might have the same problem.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">311670</id>
  <importance type="integer">48</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">864</number>
  <priority type="integer">3</priority>
  <reporter-id>blALOcfDar3ONueJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Actions without a project difficult to get at during weekly review (add a &quot;None&quot; project category)</summary>
  <updated-at type="datetime">2012-04-16T12:09:41Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>blALOcfDar3ONueJe5aVNr</id><login>cportner</login><login_name warning="deprecated">cportner</login_name><name>cportner</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084"></custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084"></CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2009-03-21T04:32:40Z</created-on>
  <description>Tracks 1.7RC2 seems to be working fine for me. Only minor annoyance is that if I go the starred task window (which is how I keep track of my &#8220;next actions&#8221;) the &#8220;Deferred actions tagged with &#8216;starred&#8217; &#8220; view always expands. I can collapse it, but next time I go back to the view by clicking on the star on top it is expanded again.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">311671</id>
  <importance type="integer">47</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">865</number>
  <priority type="integer">3</priority>
  <reporter-id>blALOcfDar3ONueJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>&quot;Deferred actions&quot; in starred view will not stay collapsed</summary>
  <updated-at type="datetime">2011-05-12T13:40:45Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>blALOcfDar3ONueJe5aVNr</id><login>cportner</login><login_name warning="deprecated">cportner</login_name><name>cportner</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">defect</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084">1.7RC</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">defect</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084">1.7RC</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2009-03-28T14:55:22Z</created-on>
  <description>Trying to be honest with GTD methodology I have found that I should convert quite a lot of todos into projects. One of reasons I am quite often not comfortable with creating new project is that it becomes quite a huge list of them on a home page. Using such great tool as tracks is should encourage to create project accordingly to GTD always when possible - even if there are two simple but isolated actions needed e.g. make a call to order a book in local bookstore and then go to a bookstore to take it. I am not sure if actual list of project is correctly presented on a home page.
* I guess list of contexts should be on top, above projects
* there should be some (configurable? of course with reasonable defaults for not advanced users) options to limit number of projects listed on home page, e.g.
** don't show empty projects
** dont't show projects with no actions to show
** show only (configurable?) number of recent projects - projects with recent actions
** sort projects by most recent actions in them  

I have currently almost 300 todos and about 80 projects (numbers are growing still growing as I am still implementing GTD) and I estimate I would have 100-150 projects. 

Also big number of todos on a homepage is not very convenient but probably this is for another ticket.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">319287</id>
  <importance type="integer">46</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>dcBQMyccir3ORbeJe5aVNr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">870</number>
  <priority type="integer">3</priority>
  <reporter-id>dcBQMyccir3ORbeJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>bad user experience on home page with a lot of projects (and/or todos)</summary>
  <updated-at type="datetime">2012-04-16T12:09:41Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dcBQMyccir3ORbeJe5aVNr</id><login>ciekawy</login><login_name warning="deprecated">ciekawy</login_name><name>ciekawy</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084">1.7</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084">1.7</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2009-04-19T13:10:26Z</created-on>
  <description>It would be very convenient to have possibility to create an action on any page - now there are views - e.g. done, calendar where there is no any form and adding new action there would be nice. Also I'd like very much google calendar feature - a shortcut that brings a popup to define an event - maybe it is good idea to have sth similar that some keybord shortcut and/or some icon on the top bar would behave similar to creating new recurring todo - but - on any page using this - new regular todo form would appear?  </description>
  <from-support type="integer">0</from-support>
  <id type="integer">340660</id>
  <importance type="integer">45</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>dcBQMyccir3ORbeJe5aVNr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">881</number>
  <priority type="integer">3</priority>
  <reporter-id>dcBQMyccir3ORbeJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>creating new action on any page?</summary>
  <updated-at type="datetime">2012-04-16T12:09:41Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dcBQMyccir3ORbeJe5aVNr</id><login>ciekawy</login><login_name warning="deprecated">ciekawy</login_name><name>ciekawy</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">1.7</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">1.7</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2009-04-29T18:01:37Z</created-on>
  <description>I really like those guys from MIT time line implementation in javascript
(http://www.simile-widgets.org/timeline/)

and I loved the way Tracks is setup as a webserver.

seeing them both work together would be great.

I have no clue in Ruby, but I once used Timeline inside Microsoft Sharepoint, so I guess integration into Tracks should be easier.

the thing I would like to see:
1. a page the shows all the tasks in a timeline.
2. a way to selective mark some todo not to show on the timelines

this can really help in planning a head with Track, and not just throwing ideas and todos into it.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">352813</id>
  <importance type="integer">44</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>duqK0anoyr3QpkeJe5aVNr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">893</number>
  <priority type="integer">3</priority>
  <reporter-id>duqK0anoyr3QpkeJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Integration of SIMILE: Timeline</summary>
  <updated-at type="datetime">2011-09-07T14:51:18Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>duqK0anoyr3QpkeJe5aVNr</id><login>Fruch</login><login_name warning="deprecated">Fruch</login_name><name>Fruch</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="Text" name="Keywords" id="3083">timeline</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="Text" name="Keywords" id="3083">timeline</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2009-06-16T21:05:09Z</created-on>
  <description>When I have multiple overdue items (it happens) it overwhelms my daily view of my icalendar feed. If an option could consolidate all overdue items into one that would be great.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">407060</id>
  <importance type="integer">43</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>awLoQAwRGr3Q8EeJe5afGb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">912</number>
  <priority type="integer">3</priority>
  <reporter-id>awLoQAwRGr3Q8EeJe5afGb</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Feature Request: Option for Overdue items to appear as one item in iCalendar feed</summary>
  <updated-at type="datetime">2012-04-16T12:10:02Z</updated-at>
  <working-hours type="float">1.0</working-hours>
  <working-hour type="float" warning="deprecated">1.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>awLoQAwRGr3Q8EeJe5afGb</id><login>benjo4u</login><login_name warning="deprecated">benjo4u</login_name><name>benjo4u</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="Text" name="Keywords" id="3083">icalendar, overdue</custom-field>
<custom-field type="List" name="Version" id="3084">1.7</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="Text" name="Keywords" id="3083">icalendar, overdue</CustomField>
<CustomField type="List" name="Version" id="3084">1.7</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2009-06-17T19:41:56Z</created-on>
  <description>There are timestamp fields in the database tracks.todos: created_at, updated_at, completed_at (and the recurring_todos table as well)

I know that the created_at field is used as older items turn yellower as they become more stale

It might be useful to provide gui access to view these values, like an item properties page.  I'd like to see how 'stale' my todo item is, not just how overdue it is.  

It seems the completed_at is used already.

Interestingly, projects and contexts also have these timestamps. Perhaps these can be displayed as well (or accessed optionally in a properties page). Though doing so with tags might (which also have timestamps) may not be as useful.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">408384</id>
  <importance type="integer">42</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>awLoQAwRGr3Q8EeJe5afGb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">913</number>
  <priority type="integer">3</priority>
  <reporter-id>awLoQAwRGr3Q8EeJe5afGb</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Feature Request: Expose timestamp values in todos table</summary>
  <updated-at type="datetime">2012-04-16T12:10:02Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>awLoQAwRGr3Q8EeJe5afGb</id><login>benjo4u</login><login_name warning="deprecated">benjo4u</login_name><name>benjo4u</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="Text" name="Keywords" id="3083">timestamp, staleness</custom-field>
<custom-field type="List" name="Version" id="3084">1.7</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="Text" name="Keywords" id="3083">timestamp, staleness</CustomField>
<CustomField type="List" name="Version" id="3084">1.7</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2009-06-18T18:58:29Z</created-on>
  <description>As nice as I find the Webapp front-end to use, the iCal export currently does not add much functionality because it is read-only; that means the user can view actions in a calendar app, but cannot make changes to them or delete them.  The specification supports all of the necessary features to implement actions as VTODOs, projects as &quot;categories&quot;, and contexts as feeds.  Most &quot;todo&quot; managers in generic calendar apps don't even attempt to take advantage of any of these attributes of VTODO; they just implement plain lists.  Full implementation of the spec isn't necessary: it would just be much easier to manage GTDs inside of PIM and email apps -- even just to mark progress and edit notes -- if the iCal feed produced by Tracks was read-write.  I know there are several Rails calendar apps already; perhaps integrating the required code would not be too painful.

This discussion: http://www.ruby-forum.com/topic/22922 lists several: http://icalendar.rubyforge.org/, http://vpim.rubyforge.org/, notably.  Although the thread was started a while ago, the projects are still active, as is RiCal: http://www.infoq.com/news/2009/05/rical

What would be required in the backend?</description>
  <from-support type="integer">0</from-support>
  <id type="integer">409689</id>
  <importance type="integer">41</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>cG8PU8xdCr3R3seJe5afGb,bgwl_cUj4r4l7keJe5cbLr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">914</number>
  <priority type="integer">3</priority>
  <reporter-id>cG8PU8xdCr3R3seJe5afGb</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Add read/write iCal support</summary>
  <updated-at type="datetime">2012-04-16T12:10:01Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cG8PU8xdCr3R3seJe5afGb</id><login>n8willis</login><login_name warning="deprecated">n8willis</login_name><name>n8willis</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2009-06-24T01:11:12Z</created-on>
  <description>It would be great to be able to drag and drop to reorder tasks on the home page, and to also be able to move them to different contexts.

For example, I'll have a context called &quot;Today&quot; and at the start of the day I'll assign the actions I want to get done in that day to this context.  Being able to easily move the actions to the &quot;Today&quot; context and order them in my planned order of attack would be fantastic.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">415046</id>
  <importance type="integer">40</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>dZj9cayfGr3OiKeJe5aVNr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">916</number>
  <priority type="integer">3</priority>
  <reporter-id>dZj9cayfGr3OiKeJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Drag &amp; Drop actions on home page to reorder, or move to a different context</summary>
  <updated-at type="datetime">2012-04-16T12:10:01Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dZj9cayfGr3OiKeJe5aVNr</id><login>evmc</login><login_name warning="deprecated">evmc</login_name><name>evmc</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Version" id="3084">1.7</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Version" id="3084">1.7</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-06-24T01:18:02Z</created-on>
  <description>When entering a new action, I often get to the context, which is pre-filled with the first context, and want to change it, which requires clearing the field, and start typing to trigger auto-complete.
If there was a little button to the right of the field that I could click to make the drop-down appear with all available contexts that would be really useful.  Can quickly update this with a couple of mouse clicks then.

The same would also be useful for the project field (although given this is initially blank, is not as big a hassle as you click on it to get all possible values.  Editing an existing Action would be different though.)

This effectively implements an editable combo-box, giving the best of both worlds IMO.

You would also want these buttons when editing an existing Action inline.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">415049</id>
  <importance type="integer">39</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>dZj9cayfGr3OiKeJe5aVNr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">917</number>
  <priority type="integer">3</priority>
  <reporter-id>dZj9cayfGr3OiKeJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Drop-down buttons on project and context</summary>
  <updated-at type="datetime">2012-04-16T12:10:00Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dZj9cayfGr3OiKeJe5aVNr</id><login>evmc</login><login_name warning="deprecated">evmc</login_name><name>evmc</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2009-09-08T01:21:22Z</created-on>
  <description>Added the ability to sort to do items in either a context list or a project list to set a sequence.  Or, you can drag an item to other contexts on the same page (on home page.)

This does &quot;break&quot; the current sort by due date&quot; view - but I really wanted to be able to put my items in sequence that makes sense to me.

Looks like this is related to open &quot;someday/maybe&quot; tickets 
* &quot;Reorder Next Actions&quot; (#91)
* &quot;Drag and Drop Between Contexts&quot; (#220 )

Hope this is something others can use.  Probably need to provide a way to sort by due date before incorporating into the main stream..so people that rely on that can still do it.

It doesn't look like too much more work to drag items into the &quot;completed&quot; container to mark them as complete (or out, if you change your mind), and dragging to defer makes a lot of sense, to visually sort what you will do tomorrow vs. today..But I'll leave that for someday/maybe :-)</description>
  <from-support type="integer">0</from-support>
  <id type="integer">507519</id>
  <importance type="integer">38</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>ck8ijory4r3RM4eJe5aVNr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">937</number>
  <priority type="integer">3</priority>
  <reporter-id>ck8ijory4r3RM4eJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Patch Adds Sortable and Dragable Todo Items</summary>
  <updated-at type="datetime">2011-09-21T16:58:13Z</updated-at>
  <working-hours type="float">6.0</working-hours>
  <working-hour type="float" warning="deprecated">6.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">8.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>ck8ijory4r3RM4eJe5aVNr</id><login>tom_v</login><login_name warning="deprecated">tom_v</login_name><name>tom_v</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-09-12T20:58:02Z</created-on>
  <description>If you create an action from the home page it appears at the bottom of the relevant context rather than being sorted into the proper spot.  This is similar to bug #393 (resort on edit)</description>
  <from-support type="integer">0</from-support>
  <id type="integer">514990</id>
  <importance type="integer">37</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>d8ViwmN9Wr3QwpeJe5aVNr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">938</number>
  <priority type="integer">3</priority>
  <reporter-id>d8ViwmN9Wr3QwpeJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>new task from home page adds task at end rather than sorting</summary>
  <updated-at type="datetime">2012-04-16T12:10:05Z</updated-at>
  <working-hours type="float">1.0</working-hours>
  <working-hour type="float" warning="deprecated">1.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>d8ViwmN9Wr3QwpeJe5aVNr</id><login>bjj</login><login_name warning="deprecated">bjj</login_name><name>Ben Jackson</name><website>http://www.ben.com/</website></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">defect</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">defect</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2009-09-12T21:09:22Z</created-on>
  <description>I haven't delved into the source to see if there's already a secondary key, but I expected that tasks with no due-date in the home page (context view) would be grouped by project and sorted in project order.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">514993</id>
  <importance type="integer">36</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>d8ViwmN9Wr3QwpeJe5aVNr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">939</number>
  <priority type="integer">3</priority>
  <reporter-id>d8ViwmN9Wr3QwpeJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>task sort within context should use project order as secondary key</summary>
  <updated-at type="datetime">2012-04-16T12:10:04Z</updated-at>
  <working-hours type="float">0.5</working-hours>
  <working-hour type="float" warning="deprecated">0.5</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>d8ViwmN9Wr3QwpeJe5aVNr</id><login>bjj</login><login_name warning="deprecated">bjj</login_name><name>Ben Jackson</name><website>http://www.ben.com/</website></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="Text" name="Keywords" id="3083">sort, unGTD</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="Text" name="Keywords" id="3083">sort, unGTD</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2009-09-12T21:26:13Z</created-on>
  <description>The home page groups all actions by context.  Contexts are edited under 'Organize|Contexts'.

There is no view which groups all actions by project.  Projects are edited under 'Projects'.

The 'starred' page and other keyword results page filters by tag but groups by context.  There is no central view of tags unless you count the very bottom of the statistics page.

Here are some ideas for making the presentation more consistent:
1)  Display actions grouped by project on the 'project' tab (just like 'home' groups by context) and move project editing to 'organize|projects'.  Perhaps add a hint that you can create an action with a new project to create a project to smooth over the transition.

2)  Replace the 'starred' page with a page that groups by tags, with 'starred' first and then the rest by frequency of use (or whatever) and then untagged tasks.  Some tasks may appear multiple times.

3)  Add an 'organize|tags' view even if its only purpose is to provide a better clickable list of tags.
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">514997</id>
  <importance type="integer">35</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>d8ViwmN9Wr3QwpeJe5aVNr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">940</number>
  <priority type="integer">3</priority>
  <reporter-id>d8ViwmN9Wr3QwpeJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>context, project and tag view/edit inconsistency</summary>
  <updated-at type="datetime">2012-04-16T12:10:04Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>d8ViwmN9Wr3QwpeJe5aVNr</id><login>bjj</login><login_name warning="deprecated">bjj</login_name><name>Ben Jackson</name><website>http://www.ben.com/</website></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2009-09-12T21:28:05Z</created-on>
  <description>In the Organize|Contexts view it should be possible to drag a visible task into the hidden and set the visibility and the sort order simultaneously.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">514999</id>
  <importance type="integer">34</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>d8ViwmN9Wr3QwpeJe5aVNr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">941</number>
  <priority type="integer">3</priority>
  <reporter-id>d8ViwmN9Wr3QwpeJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>should be able to drag contexts between visible/hidden</summary>
  <updated-at type="datetime">2012-04-16T12:10:04Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>d8ViwmN9Wr3QwpeJe5aVNr</id><login>bjj</login><login_name warning="deprecated">bjj</login_name><name>Ben Jackson</name><website>http://www.ben.com/</website></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">minor</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">minor</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2009-09-12T21:30:24Z</created-on>
  <description>I created a project 'Christmas' to record gift ideas.  I want them all to be due on Dec 25 and not to appear until about mid Nov.  It's tedious to do that manually.  There's not even a 'clone action' button that could help me.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">515001</id>
  <importance type="integer">33</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>d8ViwmN9Wr3QwpeJe5aVNr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">942</number>
  <priority type="integer">3</priority>
  <reporter-id>d8ViwmN9Wr3QwpeJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>projects need default due date, default 'show from'</summary>
  <updated-at type="datetime">2012-04-16T12:10:03Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>d8ViwmN9Wr3QwpeJe5aVNr</id><login>bjj</login><login_name warning="deprecated">bjj</login_name><name>Ben Jackson</name><website>http://www.ben.com/</website></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2009-09-12T21:35:55Z</created-on>
  <description>This is kind of a pie-in-the-sky idea, but it would be nice if I could have one context ordering for Work, one for Home, etc.  Almost a context context.  Since I thought of this I did notice that collapsing contexts does 'stick', so if it's by session that may be sufficient.

The slightly watered down version of this is to assume that your location corresponds 1:1 with some context and it should be displayed first (rather than your location implying a whole new ordering of contexts).  If it's just saved in your session, it could be a button (up arrow) to promote a context on your home page only within that session.  I was also imagining more elaborate ideas where the promotion is recorded with the client IP address and a sufficiently 'near' IP match of a new session would select a primary context.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">515004</id>
  <importance type="integer">32</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>d8ViwmN9Wr3QwpeJe5aVNr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">943</number>
  <priority type="integer">3</priority>
  <reporter-id>d8ViwmN9Wr3QwpeJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>context sort order by session or IP or ?</summary>
  <updated-at type="datetime">2012-04-16T12:09:46Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>d8ViwmN9Wr3QwpeJe5aVNr</id><login>bjj</login><login_name warning="deprecated">bjj</login_name><name>Ben Jackson</name><website>http://www.ben.com/</website></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">1.7</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">1.7</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2009-09-13T21:17:14Z</created-on>
  <description>If a context is collapsed on the home page and you reload the page, the context renders and then collapses (complete with animation as if you'd clicked the button).  It should just load already closed.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">515522</id>
  <importance type="integer">31</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>d8ViwmN9Wr3QwpeJe5aVNr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">946</number>
  <priority type="integer">3</priority>
  <reporter-id>d8ViwmN9Wr3QwpeJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>context collapse animates after page reload</summary>
  <updated-at type="datetime">2012-04-16T12:09:46Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>d8ViwmN9Wr3QwpeJe5aVNr</id><login>bjj</login><login_name warning="deprecated">bjj</login_name><name>Ben Jackson</name><website>http://www.ben.com/</website></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">defect</custom-field>
<custom-field type="List" name="Severity" id="3081">minor</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">defect</CustomField>
<CustomField type="List" name="Severity" id="3081">minor</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2009-09-16T18:19:35Z</created-on>
  <description>When an action is displayed with a hilited 'due in X days' box, clicking that box should pop up a calendar to edit the due date (a shortcut to opening edit, clicking on the date, clicking commit).  Or maybe even fancier you should be able to hover over the date and it should get [&lt;] and [&gt;] arrow &quot;ears&quot; that you can click on to move the date back and forth.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">520298</id>
  <importance type="integer">29</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>d8ViwmN9Wr3QwpeJe5aVNr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">950</number>
  <priority type="integer">3</priority>
  <reporter-id>d8ViwmN9Wr3QwpeJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>clicking 'due in 2 days' should pop up calendar to edit date</summary>
  <updated-at type="datetime">2012-04-16T12:10:06Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>d8ViwmN9Wr3QwpeJe5aVNr</id><login>bjj</login><login_name warning="deprecated">bjj</login_name><name>Ben Jackson</name><website>http://www.ben.com/</website></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="Text" name="Keywords" id="3083">unGTD</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="Text" name="Keywords" id="3083">unGTD</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2010-01-03T09:56:44Z</created-on>
  <description>This is about right to left language support. Hebrew, Arabic and Persian languages and some others need this.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">795317</id>
  <importance type="integer">28</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>dKrk6m97Kr3QVEeJe5aVNr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">980</number>
  <priority type="integer">3</priority>
  <reporter-id>dKrk6m97Kr3QVEeJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>RTL support</summary>
  <updated-at type="datetime">2012-04-16T12:09:45Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dKrk6m97Kr3QVEeJe5aVNr</id><login>DawnLight</login><login_name warning="deprecated">DawnLight</login_name><name>Shahar Or</name><email>email@shahar-or.co.il</email></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="Text" name="Keywords" id="3083">i18n</custom-field>
<custom-field type="List" name="Version" id="3084">1.7</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="Text" name="Keywords" id="3083">i18n</CustomField>
<CustomField type="List" name="Version" id="3084">1.7</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2010-01-04T13:30:55Z</created-on>
  <description>Would be nice to be able to type in the Due and Show from fields only the day of month.

Behavior:
If the day entered is today or later, assume user means current month. If the day entered is before before today, assume user means next month.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">797569</id>
  <importance type="integer">27</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">983</number>
  <priority type="integer">3</priority>
  <reporter-id>dKrk6m97Kr3QVEeJe5aVNr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Allow entering partial dates</summary>
  <updated-at type="datetime">2012-04-16T12:09:45Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dKrk6m97Kr3QVEeJe5aVNr</id><login>DawnLight</login><login_name warning="deprecated">DawnLight</login_name><name>Shahar Or</name><email>email@shahar-or.co.il</email></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2010-07-21T12:05:54Z</created-on>
  <description>Either I would like to be able to assign multiple contexts to an action, or be able to show lists of actions having &quot;visible on front page&quot; tags (just like is currently done for contexts).

The main thing I'm trying to get is a list of actions belonging to a tag (or context) on the front page, where a single action can appear under more than one context/tag.

As an example (on the front page):
[tag1]
action1
action2

[tag2]
action5
action2
action7

...
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1776569</id>
  <importance type="integer">26</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>dbG5FyLlSr35kVeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1050</number>
  <priority type="integer">3</priority>
  <reporter-id>dbG5FyLlSr35kVeJe5cbCb</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>allow tags to be shown on front-page like contexts</summary>
  <updated-at type="datetime">2012-04-16T12:10:12Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dbG5FyLlSr35kVeJe5cbCb</id><login>edgimar</login><login_name warning="deprecated">edgimar</login_name><name>edgimar</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">major</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">major</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2010-08-05T08:30:30Z</created-on>
  <description>There's a nice javascript SVG editor available at http://code.google.com/p/svg-edit/, which I think would be very cool if it were integrated with tracks, so that instead of just adding &quot;notes&quot; to a project / etc., you could add a &quot;visual note&quot; which just fires up the svg-editor instead of opening a textbox.  See the editor demo at http://svg-edit.googlecode.com/svn/branches/2.5/editor/svg-editor.html -- it's quite nice.

</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1851661</id>
  <importance type="integer">25</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>dbG5FyLlSr35kVeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1057</number>
  <priority type="integer">3</priority>
  <reporter-id>dbG5FyLlSr35kVeJe5cbCb</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>allow adding of &quot;visual-notes&quot; via javascript SVG editor</summary>
  <updated-at type="datetime">2012-04-16T12:10:11Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dbG5FyLlSr35kVeJe5cbCb</id><login>edgimar</login><login_name warning="deprecated">edgimar</login_name><name>edgimar</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2010-08-22T15:02:10Z</created-on>
  <description>I've been using Tracks for some time now, and I really love its simplicity and ease of use.  The only problem is that our company uses Basecamp for all project and task management so I have to work in two systems. I've started working on integrating Tracks with Basecamp, and you can see the latest where I forked Tracks on github.com: http://github.com/treyconnell/tracks

Project integration is largely complete, and task list integration is next on my list (working on it today).

I'm hoping you'll find this integration useful and something that might make sense to allow core users of Tracks to turn on. Basecamp has a HUGE following and it may very well serve to garner more users and more attention for Tracks if the two systems can talk.

Best,
Trey Connell
http://www.treyconnell.com</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1984783</id>
  <importance type="integer">24</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>aR73OURF0r34X2eJe5cbCb,czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1061</number>
  <priority type="integer">3</priority>
  <reporter-id>aR73OURF0r34X2eJe5cbCb</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Integration with Basecamp would be Really Valuable</summary>
  <updated-at type="datetime">2012-04-16T12:10:11Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aR73OURF0r34X2eJe5cbCb</id><login>tconnell</login><login_name warning="deprecated">tconnell</login_name><name>tconnell</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="Text" name="Keywords" id="3083">integration, basecamp</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="Text" name="Keywords" id="3083">integration, basecamp</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2010-11-15T14:01:59Z</created-on>
  <description>http://live.gnome.org/Tasque is a pretty cool TODO editor that plugs into various backends (see webpage). It would be nice to be able to view, add and complete tasks from Tasque with a Tracks backend. I don't really know if the work has to be done on the Tracks side (implementing and existing API) or on the Tasque side (new backend).</description>
  <from-support type="integer">0</from-support>
  <id type="integer">2552161</id>
  <importance type="integer">23</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>b4n_sG8mar36__eJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1079</number>
  <priority type="integer">3</priority>
  <reporter-id>b4n_sG8mar36__eJe5cbCb</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Interact (display&amp;edit) with tasque</summary>
  <updated-at type="datetime">2012-04-16T12:10:11Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>b4n_sG8mar36__eJe5cbCb</id><login>arthur.lutz</login><login_name warning="deprecated">arthur.lutz</login_name><name>arthur.lutz</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2010-11-16T13:04:44Z</created-on>
  <description>Print Button &#8211; Place a print button on the page that feeds directly to built-in print function of the browser.  You have done a great job with making the pages printable and they are really clean and nice. We should let people know that the function IS there for that by adding a button.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">2560557</id>
  <importance type="integer">22</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1080</number>
  <priority type="integer">3</priority>
  <reporter-id>cF8gq42n4r3zEZab7jnrAJ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>add print button</summary>
  <updated-at type="datetime">2010-11-16T13:04:44Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2011-02-05T18:24:32Z</created-on>
  <description>Add an option to disable the CFRS token on the login page.
Add an url like login?user=XXX&amp;password=YYY that will log the user XXX in.

This is because Tracks can be used on a secure network (behind a https proxy doing HTTP-Auth at my place for example), and because it's anoying to have to type lots of passords !

For instance, I integrate Track in a frame with my menu in a top-frame, my user is already logged in when he sees my menu, I know his tracks password, I want to log him in and then show tracks in the southframe.

Next step would then be the possibility to login with a SSO.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">3078619</id>
  <importance type="integer">21</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1093</number>
  <priority type="integer">3</priority>
  <reporter-id>d03rVGmvar4l3yeJe5cbCb</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Login &amp; CSFR</summary>
  <updated-at type="datetime">2012-04-16T12:10:14Z</updated-at>
  <working-hours type="float">0.5</working-hours>
  <working-hour type="float" warning="deprecated">0.5</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>d03rVGmvar4l3yeJe5cbCb</id><login>toxic0</login><login_name warning="deprecated">toxic0</login_name><name>toxic0</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="Text" name="Keywords" id="3083">CSRF &amp; GET-login url</custom-field>
<custom-field type="List" name="Version" id="3084">1.7.2</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="Text" name="Keywords" id="3083">CSRF &amp; GET-login url</CustomField>
<CustomField type="List" name="Version" id="3084">1.7.2</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2011-02-08T20:21:01Z</created-on>
  <description>Add a configuration option to show/hide the deferred/pending actions in starred view.

Reference: http://www.getontracks.org/forums/viewreply/2691/</description>
  <from-support type="integer">0</from-support>
  <id type="integer">3096757</id>
  <importance type="integer">20</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1099</number>
  <priority type="integer">3</priority>
  <reporter-id>ajOv0IZiCr35MDeJe5cbLA</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Configurable visibility of deferred/pending actions in starred view</summary>
  <updated-at type="datetime">2012-04-16T12:10:14Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>ajOv0IZiCr35MDeJe5cbLA</id><login>mhn</login><login_name warning="deprecated">mhn</login_name><name>mhn</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2011-04-05T20:27:27Z</created-on>
  <description>I have Tracks set as my browser home page. If I open a browser window/tab with the intent of visiting somewhere other than my Tracks installation, the form steals focus from the browser's URL and/or search bars before I can finish typing an address or search term. I would like to disable the autofocus on the main page.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">3549925</id>
  <importance type="integer">19</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>d9-njOu-Gr4j6EeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1139</number>
  <priority type="integer">3</priority>
  <reporter-id>d9-njOu-Gr4j6EeJe5cbCb</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Option to disable form autofocus</summary>
  <updated-at type="datetime">2012-04-16T12:10:14Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>d9-njOu-Gr4j6EeJe5cbCb</id><login>zoombody</login><login_name warning="deprecated">zoombody</login_name><name>zoombody</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2011-04-12T12:42:53Z</created-on>
  <description>This is a reposted ticket from forum post [[url:http://www.getontracks.org/forums/viewthread/839/P30/|Tracks 2.0RC2 is out]]:

* Ideally everything should be drag&#8217;n'dropable - for lazy people, like me, for example.
** You should be able to drag action to a context, tag (cloud) or a project on the right sidebar (not only on the action list, because if I have many actions defined in all contexts, there might be a long-long way up/down to drag the action from one context to other).
** Thicker/Due feature. There could be a little calendar (current and next month) on the sidebar. One should be able to drag&#8217;n'drop an action on a specific date, or a week (a little square drop-field in front of each week in the calendar), or a month (to drop the action on the &#8220;month name&#8221; field of the calendar). 
** Ability to collapse/expand context/tag/project lists and calendar in case all expanded lists do not fit in the screen.
* Date stamps. When was the action created/updated (At least in the action/project &#8220;notes&#8221; section, automatically). If I want to see when the action/project was created, I can &#8220;toggle notes&#8221; for all or particular action/project to find this information.
* Missing tickler buttons +1 and +7 on the right. I know they are now in the context menu, I just so liked them right there on the line...
* Context groups in Project view. To see specific context in each project. There could also be a context picture/icon on the left/right of each action (like a little home, computer, phone etc.)
* Hide/unhide a context by clicking on the Visible/Hidden button on the right. Similarly in projects one could click the Active/Hidden/Completed button to change the status without going in the edit section.
* Sort by tags alphabetically or by number of actions per tag. Right now we can display action from one tag by clicking on a tag in the action. I would also appreciate a tag cloud in the sidebar.
* Nested projects. Ability to make project in project, also dependencies for projects, so that depending project would be hidden until specific projects have been completed.
* Add files option. Add files to an action or project notes. Even more sophisticated if we could link to AmazonS3 bucket and store all files there. (*Update* There seems to be a simple solution to do that: [[url:http://www.getontracks.org/?URL=http%3A%2F%2Fwww.railstoolkit.com%2Fposts%2Ffancyupload-amazon-s3-uploader-with-paperclip|Amazon S3 Uploader with Paperclip]])
* Left sidebar could be sticky - stay in place even if I scroll trough my actions. This feature would be especially relevant if I could drag&#8217;n'drop actions on contexts, tags, dates. Also in this case there should be the ability to collapse/expand context/tag/project lists and calendar in case all expanded lists do not fit in the screen.
* Inbox section. A dedicated section for adding actions/notes without context. Made to get actions/tasks in system as soon, as simple and as easy as possible. For example - a shortcut key (alt+n or something) to start new record(action). First line should be automatically converted to a title but next lines to a description of a note/action. When I have all my actions in INBOX section I can start organizing them by project, context, due, someday/maybe, calendar, waiting, next action or a reference (according to GTD). The simplest way to organize would of course be dragging and dropping on a context, project, calendar, tag etc.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">3600823</id>
  <importance type="integer">18</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1141</number>
  <priority type="integer">3</priority>
  <reporter-id>dF5760zpSr4jFxeJe5cbCb</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Feature Suggestions for 2.0-2.1</summary>
  <updated-at type="datetime">2012-04-16T12:10:13Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>dF5760zpSr4jFxeJe5cbCb</id><login>Swan</login><login_name warning="deprecated">Swan</login_name><name>Swan</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">2.0RC2</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">2.0RC2</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2011-04-26T12:01:37Z</created-on>
  <description>I want to suggest an alternative visualization for the diagrams on the statistics site. The JavaScript based SVG library [[url:http://raphaeljs.com/|Raphael]] could be nice to get rid of Flash. Check out the demos on the homepage, esp. for diagrams.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">3704598</id>
  <importance type="integer">17</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1153</number>
  <priority type="integer">3</priority>
  <reporter-id>aQmhwCB_Sr4kgfeJe5cbCb</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>get rid of Flash for statistics page</summary>
  <updated-at type="datetime">2012-04-16T12:10:13Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aQmhwCB_Sr4kgfeJe5cbCb</id><login>voxspox</login><login_name warning="deprecated">voxspox</login_name><name>voxspox</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="Text" name="Keywords" id="3083">flash, statistics, javascript</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="Text" name="Keywords" id="3083">flash, statistics, javascript</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2011-09-06T13:31:54Z</created-on>
  <description>Another GTD application has the following very handy feature: you can define perspectives. For tracks, a perspective is a set of contexts that are visible at the moment. It is essentially the home page with some contexts hidden.

The point is that you could be right now at your office and only a subset of the contexts is relevant to you (e.g., office, errand, offline, etc). Hence, you only want to see the contexts you can actually do something for.

I understand that you could can mimik this with defining tags (e.g., an @work tag), however, you would have to always remember when you enter a new action whether it should have that tag.

Tracks would need:

* A configuration table which contexts are visible in which perspective
* A way to select a perspective on the home screen
* A home screen with accesskey for the 'all' perspective, which shows everything. This is essentially the current home screen.
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">6052371</id>
  <importance type="integer">16</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>aUkc3w1Y0r4jEseJe4gwI3,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1193</number>
  <priority type="integer">3</priority>
  <reporter-id>aUkc3w1Y0r4jEseJe4gwI3</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Perspectives (=Home with defined sets of visible contexts)</summary>
  <updated-at type="datetime">2012-04-16T12:10:36Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aUkc3w1Y0r4jEseJe4gwI3</id><login>popsch</login><login_name warning="deprecated">popsch</login_name><name>popsch</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">8</component-id>
  <created-on type="datetime">2011-09-12T11:59:54Z</created-on>
  <description>I would like to see the ability to share specific contexts with people, both on the running tracks instance, and via the REST API, using an authentication token, like google does for its ical API.

That way, you can integrate  non tracks users, on other systems, without giving access to your whole tracks database.
I.E. having to sync everything

I'm guessing this is a change/addition to the REST API authentication mechanism, and possibly adding local/remote tracks&lt;-&gt;tracks server sync via REST</description>
  <from-support type="integer">0</from-support>
  <id type="integer">6315831</id>
  <importance type="integer">15</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>,aQmhwCB_Sr4kgfeJe5cbCb,bJxdBEGXar4yo2acwqjQXA,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1201</number>
  <priority type="integer">3</priority>
  <reporter-id>cet16y3tqr4k3qeJe4gwI3</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Use contexts to share tasks with other users.</summary>
  <updated-at type="datetime">2012-04-21T16:49:38Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cet16y3tqr4k3qeJe4gwI3</id><login>timoc</login><login_name warning="deprecated">timoc</login_name><name>timoc</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2011-10-01T00:17:53Z</created-on>
  <description>The project view (ALT-P) should have a checkbox next to the project to mark a project as complete. </description>
  <from-support type="integer">0</from-support>
  <id type="integer">7407993</id>
  <importance type="integer">14</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>aUkc3w1Y0r4jEseJe4gwI3,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1213</number>
  <priority type="integer">3</priority>
  <reporter-id>aUkc3w1Y0r4jEseJe4gwI3</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>'done' checkbox in project view</summary>
  <updated-at type="datetime">2012-04-16T12:10:19Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aUkc3w1Y0r4jEseJe4gwI3</id><login>popsch</login><login_name warning="deprecated">popsch</login_name><name>popsch</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2011-11-20T17:35:13Z</created-on>
  <description>A request like this will only work is 'newcontextcomputer' is actually a new context:
&lt;pre&gt;&lt;code&gt;&lt;todo&gt;
&lt;description&gt;task 1 in 11111111, 11111&lt;/description&gt;
&lt;project_id&gt;31&lt;/project_id&gt;
&lt;notes&gt;my notes here&lt;/notes&gt;
&lt;tags&gt;
  &lt;tag&gt;&lt;name&gt;starred&lt;/name&gt;&lt;/tag&gt;
  &lt;tag&gt;&lt;name&gt;blue&lt;/name&gt;&lt;/tag&gt;&lt;/tags&gt;
&lt;context&gt;&lt;name&gt;newcontextcomputer&lt;/name&gt;&lt;/context&gt;
&lt;/todo&gt;
&lt;/code&gt;&lt;/pre&gt;

This is awkward, because to use the REST API properly, one has to follow this:

1) Check if context already exists.
2) If context exists, then get context_id and use &lt;context_id&gt;#id&lt;/context_id&gt;
3) If context doesn't exist, then use &lt;context&gt;&lt;name&gt;#name&lt;/name&gt;&lt;/context&gt;

To improve usability, the following should be the two options for defining a context in a call:
&lt;pre&gt;&lt;code&gt;&lt;context&gt;&lt;name&gt;#new_or_existing_name&lt;/name&gt;&lt;/context&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;pre&gt;&lt;code&gt;&lt;context&gt;&lt;id&gt;#existing_id_only&lt;/id&gt;&lt;/context&gt;
&lt;/code&gt;&lt;/pre&gt;


</description>
  <from-support type="integer">1</from-support>
  <id type="integer">10180223</id>
  <importance type="integer">13</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>aUkc3w1Y0r4jEseJe4gwI3,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1224</number>
  <priority type="integer">3</priority>
  <reporter-id>aUkc3w1Y0r4jEseJe4gwI3</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>REST API for todo context is awkward</summary>
  <updated-at type="datetime">2011-11-23T10:07:37Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>cF8gq42n4r3zEZab7jnrAJ</id><login>lrbalt</login><login_name warning="deprecated">lrbalt</login_name><name>lrbalt</name></assigned-to>
  <reporter><id>aUkc3w1Y0r4jEseJe4gwI3</id><login>popsch</login><login_name warning="deprecated">popsch</login_name><name>popsch</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2011-11-27T13:14:43Z</created-on>
  <description>It would be nice to be able to use the markdown format in the project description and the task description.

Markdown: http://daringfireball.net/projects/markdown/

ruby markdown interpreter: http://stackoverflow.com/questions/373002/better-ruby-markdown-interpreter
</description>
  <from-support type="integer">1</from-support>
  <id type="integer">10506413</id>
  <importance type="integer">12</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>aUkc3w1Y0r4jEseJe4gwI3,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1226</number>
  <priority type="integer">3</priority>
  <reporter-id>aUkc3w1Y0r4jEseJe4gwI3</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>markdown mode in the description fields</summary>
  <updated-at type="datetime">2012-04-16T12:10:17Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aUkc3w1Y0r4jEseJe4gwI3</id><login>popsch</login><login_name warning="deprecated">popsch</login_name><name>popsch</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2011-11-28T14:19:32Z</created-on>
  <description>1) Create a project
2) Add two todos with arbitrary due-dates
3) Mark the project as 'completed'
4) Go to the calendar view

The two todos will still show up, although the project is no longer active. </description>
  <from-support type="integer">1</from-support>
  <id type="integer">10546493</id>
  <importance type="integer">11</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>aUkc3w1Y0r4jEseJe4gwI3,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1227</number>
  <priority type="integer">3</priority>
  <reporter-id>aUkc3w1Y0r4jEseJe4gwI3</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>when marking a project 'complete', then all todos should be treated as complete</summary>
  <updated-at type="datetime">2012-04-16T12:10:16Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aUkc3w1Y0r4jEseJe4gwI3</id><login>popsch</login><login_name warning="deprecated">popsch</login_name><name>popsch</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">8</component-id>
  <created-on type="datetime">2011-12-16T15:03:32Z</created-on>
  <description>I understand that it's a lot of work, however, the application should have an undo functionality. Using the command pattern this would be straightforward to implement, but it needs a lot of restructuring of the code.

Command pattern for undo: http://mattberther.com/2004/09/16/using-the-command-pattern-for-undo-functionality</description>
  <from-support type="integer">1</from-support>
  <id type="integer">11568133</id>
  <importance type="integer">10</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>aUkc3w1Y0r4jEseJe4gwI3,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1228</number>
  <priority type="integer">3</priority>
  <reporter-id>aUkc3w1Y0r4jEseJe4gwI3</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Tracks needs 'undo' </summary>
  <updated-at type="datetime">2012-04-16T12:10:23Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aUkc3w1Y0r4jEseJe4gwI3</id><login>popsch</login><login_name warning="deprecated">popsch</login_name><name>popsch</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">major</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">major</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2011-12-20T15:41:02Z</created-on>
  <description>Tracks needs assert statements in the code to check preconditions and postconditions for functions. They help uncover errors that have a long delay until they cause a failure, and they would also be the first step towards automated testing of the code.

I assume that this will need some discussion.</description>
  <from-support type="integer">1</from-support>
  <id type="integer">11748813</id>
  <importance type="integer">9</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>aUkc3w1Y0r4jEseJe4gwI3,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1233</number>
  <priority type="integer">3</priority>
  <reporter-id>aUkc3w1Y0r4jEseJe4gwI3</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>need assert statements in the code</summary>
  <updated-at type="datetime">2012-04-16T12:10:22Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aUkc3w1Y0r4jEseJe4gwI3</id><login>popsch</login><login_name warning="deprecated">popsch</login_name><name>popsch</name></reporter>
<custom-fields>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2012-01-17T16:30:07Z</created-on>
  <description>Hi,

I've been using Tracks for a few months by way of tracks.tra.in and love it.  Thanks so much for your work.
I've seen Tracks slow down dramatically lately and suspected resource constraint server-side, but I've done side-by-side comparisons of normal Tracks activities (creating new actions, resolving old ones) today in Chrome (at 16.0.912.75) and Firefox, and Firefox is snappy, while actions in Chrome can take many seconds and often require page refreshes.

Thanks,
-Jessica</description>
  <from-support type="integer">1</from-support>
  <id type="integer">13008023</id>
  <importance type="integer">8</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>cPOuYwqser4z-7acwqjQXA,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ,dK-axMW8Cr4jBpeJe5cbCb</notification-list>
  <number type="integer">1236</number>
  <priority type="integer">3</priority>
  <reporter-id>cPOuYwqser4z-7acwqjQXA</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Tracks is very slow in latest version of Chrome</summary>
  <updated-at type="datetime">2012-04-06T12:09:14Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cPOuYwqser4z-7acwqjQXA</id><login>greer.jessica</login><login_name warning="deprecated">greer.jessica</login_name><name>greer.jessica</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">defect</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">defect</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2012-02-11T21:24:05Z</created-on>
  <description>The REST interface seems to eat up any kind of HTML code in the note text.
&lt;pre&gt;&lt;code&gt;curl -u test:test -H &quot;Content-Type: text/xml&quot; -d \
&quot;&lt;todo&gt;&lt;description&gt;desc&lt;/description&gt;&lt;notes&gt;muh &lt;a href='www.cnn.com'&gt;cnn&lt;/a&gt;&lt;/notes&gt;&lt;context_id&gt;1&lt;/context_id&gt;&lt;/todo&gt;&quot; \
    http://localhost:3000/todos.xml -i
&lt;/code&gt;&lt;/pre&gt;
 
</description>
  <from-support type="integer">1</from-support>
  <id type="integer">14788273</id>
  <importance type="integer">7</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>aUkc3w1Y0r4jEseJe4gwI3,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1243</number>
  <priority type="integer">3</priority>
  <reporter-id>aUkc3w1Y0r4jEseJe4gwI3</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>REST doesn't permit links in notes</summary>
  <updated-at type="datetime">2012-03-19T03:24:29Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aUkc3w1Y0r4jEseJe4gwI3</id><login>popsch</login><login_name warning="deprecated">popsch</login_name><name>popsch</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2012-02-14T04:32:48Z</created-on>
  <description>Currently TRACKS has no interface for managing the set of tags known in the system.</description>
  <from-support type="integer">1</from-support>
  <id type="integer">14924033</id>
  <importance type="integer">6</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>aUkc3w1Y0r4jEseJe4gwI3,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1246</number>
  <priority type="integer">3</priority>
  <reporter-id>aUkc3w1Y0r4jEseJe4gwI3</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>missing interface for managing tags</summary>
  <updated-at type="datetime">2012-02-22T13:50:35Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aUkc3w1Y0r4jEseJe4gwI3</id><login>popsch</login><login_name warning="deprecated">popsch</login_name><name>popsch</name></reporter>
<custom-fields>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>bAHywc2B4r3yj4ab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">9</component-id>
  <created-on type="datetime">2012-02-22T16:29:13Z</created-on>
  <description>I have been experimenting with jquery mobile to drive the mobile interface.  it actually was not to hard to get it running.

I think it maybe a great way to quickly make tracks very touch screen friendly.

There is still some weirdness here and there so I don't think it is ready for merging into master as yet, but thought it was far enough along that I thought there would be value in sharing it with the community.  Can we pull it in as a branch of TracksApp maybe so it is more accessible to folks?

Some things off the top of mind that would need to be addressed:

* Since jquery mobile is oriented at modern, touchbased devices that support HTML5, we would need a way to make it available while still having the old mobile interface available.  I believe new :format would work, but I am concerned that this would make our views cluttered with another set of files to maintain...  Another option might to trigger on the user agent or leverage [[url:http://en.wikipedia.org/wiki/WURFL|WURLF]]
* Tests.  I haven't tried them.  I assume that some are broken by this...
* We might want to rethink the flow of things.  We could probably take advantage of things jquerymobile provides for things like editing todos.  For example, instead of going to the show.m.erb page now when you click a link, we might want to reveal some buttons on the current page...  Probably lots of cool things.

So check it out !  Here is the branch: https://github.com/maddentim/tracks/tree/jqm
</description>
  <from-support type="integer">1</from-support>
  <id type="integer">15491553</id>
  <importance type="integer">5</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>bAHywc2B4r3yj4ab7jnrAJ,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1250</number>
  <priority type="integer">3</priority>
  <reporter-id>bAHywc2B4r3yj4ab7jnrAJ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>jquery mobile based interface</summary>
  <updated-at type="datetime">2012-02-27T06:14:06Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>bAHywc2B4r3yj4ab7jnrAJ</id><login>maddentim</login><login_name warning="deprecated">maddentim</login_name><name>maddentim</name></assigned-to>
  <reporter><id>bAHywc2B4r3yj4ab7jnrAJ</id><login>maddentim</login><login_name warning="deprecated">maddentim</login_name><name>maddentim</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Version" id="3084">git-devel</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Version" id="3084">git-devel</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2005-06-25T02:33:47Z</created-on>
  <description>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...
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240211</id>
  <importance type="integer">11</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">74</number>
  <priority type="integer">4</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>open Finder (Mac) or File Manager (Windows) at specific location depending on the action</summary>
  <updated-at type="datetime">2012-04-16T12:10:37Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2005-09-29T14:35:53Z</created-on>
  <description>reading publications about personal information management and personal organisation for many years now, I always found the so called &quot;&quot;Covey Quadrant&quot;:http://c2.com/cgi/wiki?FourQuadrants&quot; more than useful.
But I have seen it integrated into software rarely although it shouldn't be too complex (or complicated).
I am wondering if there is some more interest to have a look if that could be realized with tracks. As I am not a ruby person I just could express from the point of user: providing a possibility to set either an &quot;urgency&quot; and an &quot;importance&quot; value within the todo entry dialog and either order by a calculation of both values or provide a view, where both are recognized.

A graphical view, like at &quot;still cool ancient] and [http://www.brandnewbox.co.uk/lab/fridge.html very rough newer&quot;:http://www.doc.ic.ac.uk/~np2/software/todo.html examples would be nice but probably too far away from this projects' targets...</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240263</id>
  <importance type="integer">10</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">123</number>
  <priority type="integer">4</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>&quot;Covey Quadrant&quot; - some brainstorming</summary>
  <updated-at type="datetime">2012-04-16T12:10:36Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-03-28T03:06:35Z</created-on>
  <description>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 &quot;Notes&quot; 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.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240394</id>
  <importance type="integer">3</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">242</number>
  <priority type="integer">4</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Documentation Modification: Information on the use of &quot;Notes&quot; tab is missing</summary>
  <updated-at type="datetime">2012-04-16T12:10:33Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2006-04-23T10:33:47Z</created-on>
  <description>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</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240418</id>
  <importance type="integer">2</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">265</number>
  <priority type="integer">4</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Change layout for Edit Action box</summary>
  <updated-at type="datetime">2012-04-16T12:10:32Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-05-17T09:07:27Z</created-on>
  <description>Wouldn't it be cool to set the collapsed/expanded state of the contexts at &quot;Home&quot; section based on the IP address of the client accessing the page? The user would be allowed to set an IP address and the state of each context for that IP address, in his preference screen.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240446</id>
  <importance type="integer">9</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">291</number>
  <priority type="integer">4</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Change context state based on IP address of client</summary>
  <updated-at type="datetime">2012-04-16T12:10:36Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-06-25T23:43:13Z</created-on>
  <description>It would be nice to be able to keep a category list and assign categories to projects.  This would allow viewing by category (i.e. Home, Chores, Work, etc.)</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240465</id>
  <importance type="integer">8</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">310</number>
  <priority type="integer">4</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Feature Request: Add category tags and views to Projects</summary>
  <updated-at type="datetime">2012-04-16T12:10:36Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084"></custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084"></CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-09-23T09:03:17Z</created-on>
  <description>If you add, change or complete an action in a project, the action counts in the side bar should be updated to reflect this change.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240538</id>
  <importance type="integer">7</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">383</number>
  <priority type="integer">4</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>completing or adding actions should update sidebar counts</summary>
  <updated-at type="datetime">2012-04-16T12:10:35Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2007-02-03T03:16:56Z</created-on>
  <description>I just tweaked app/views/shared/_add_new_item_form.rhtml to hardcode the todo title and description at 65 characters instead of 25, which fit my screen better.  I'd love to be able to set this as a preference.
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240587</id>
  <importance type="integer">6</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">431</number>
  <priority type="integer">4</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Sidebar: todo and notes fields too narrow. Optional width?</summary>
  <updated-at type="datetime">2012-04-16T12:10:35Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2007-02-08T08:48:20Z</created-on>
  <description>As far as I can see (please correct me if this is wrong), the only way to add notes is to go to the concerned project's page and use the &quot;Add a note&quot; link. Wouldn't it be easier if the &quot;Notes&quot; section (which as of now only lists all the current notes) had a &quot;Add a new note&quot; section too?</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240593</id>
  <importance type="integer">1</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">437</number>
  <priority type="integer">4</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Adding Notes</summary>
  <updated-at type="datetime">2012-04-16T12:10:32Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2007-02-15T09:33:28Z</created-on>
  <description>Once in a while (due to my indecisive nature I guess) when I create an action, I do not associate a project with it. It could also be that I forgot to create the project before creating the action.

Later, when I go to the edit mode of the action (in the front page), I see that &quot;None&quot; is filled in the Project section. Changing this becomes a pain - I need to select the whole text and then delete it and then enter a new one. Couldn't Tracks do this instead:

In the edit mode of an action, whenever the curson/mouse is in the Context or the Project field:

- If the value is &quot;None&quot;, the whole value is deleted

- If the value is anything else, the value is highlighted/selected</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240596</id>
  <importance type="integer">5</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">440</number>
  <priority type="integer">4</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>'Project' field in action's edit mode should be highlighted</summary>
  <updated-at type="datetime">2012-04-16T12:10:34Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2007-03-29T07:40:35Z</created-on>
  <description>Letting users know of how to use/fill a field (eg shortcuts in due date, Textile in notes field) would improve the usability of Tracks.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240640</id>
  <importance type="integer">4</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">483</number>
  <priority type="integer">4</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>(context based) help</summary>
  <updated-at type="datetime">2012-04-16T12:10:33Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2011-08-03T13:06:25Z</created-on>
  <description>The context field on task enter screen is set to autocomplete via ajax. This request takes long time and slows down task entering. 
I suggest to preload them (don't do a _remote_ autocomplete), because users normally won't have a huge load of contexts. This could also be done for projects.

I can implement this, if there aren't any objections.

Some notes for the implementer:
List has to be extended if a new context is created.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">4610674</id>
  <importance type="integer">1</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>bgwl_cUj4r4l7keJe5cbLr,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1188</number>
  <priority type="integer">4</priority>
  <reporter-id>bgwl_cUj4r4l7keJe5cbLr</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Task enter screen: Don't load contexts via ajax (autocomplete)</summary>
  <updated-at type="datetime">2012-04-16T11:37:10Z</updated-at>
  <working-hours type="float">3.0</working-hours>
  <working-hour type="float" warning="deprecated">3.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bgwl_cUj4r4l7keJe5cbLr</id><login>u2ix</login><login_name warning="deprecated">u2ix</login_name><name>u2ix</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2011-09-05T13:40:23Z</created-on>
  <description>It would be nice to have a preference setting for the default state of the 'new entry' element in the sidebar (either open or closed on refresh).  </description>
  <from-support type="integer">0</from-support>
  <id type="integer">6009091</id>
  <importance type="integer">12</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>aUkc3w1Y0r4jEseJe4gwI3,aQmhwCB_Sr4kgfeJe5cbCb,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">1191</number>
  <priority type="integer">4</priority>
  <reporter-id>aUkc3w1Y0r4jEseJe4gwI3</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Preference settings for 'new entry' in sidebar</summary>
  <updated-at type="datetime">2012-03-21T13:22:50Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aUkc3w1Y0r4jEseJe4gwI3</id><login>popsch</login><login_name warning="deprecated">popsch</login_name><name>popsch</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>bgfq4qA1Gr2QjIaaaHk9wZ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2005-08-04T16:44:36Z</created-on>
  <description>The TXT feed is so much like YAML, could we make it just be YAML?

I'm hacking feed_helper#build_text_page...</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240231</id>
  <importance type="integer">8</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>bgfq4qA1Gr2QjIaaaHk9wZ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">94</number>
  <priority type="integer">5</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>TXT as YAML</summary>
  <updated-at type="datetime">2012-04-16T12:10:42Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2005-10-01T11:16:55Z</created-on>
  <description>wouldn&#8217;t it be better (more intuitive) to name the notes &#8220;calculation example&#8221;, &#8220;brainstorming of xyz project&#8221; instead of &#8220;note 1&#8221;, &#8220;note 2&#8221;? ...</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240267</id>
  <importance type="integer">7</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">127</number>
  <priority type="integer">5</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>&quot;Project Notes&quot; appearance - suggestion</summary>
  <updated-at type="datetime">2012-04-16T12:10:41Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-04-17T13:01:30Z</created-on>
  <description>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.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240408</id>
  <importance type="integer">2</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">256</number>
  <priority type="integer">5</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>next actions with sensitive due-date doesn't automatically sorted with Ajax</summary>
  <updated-at type="datetime">2012-04-16T12:10:39Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2006-04-19T13:41:34Z</created-on>
  <description>I currently share my Tracks install with my other half, what would make our lives much easier is a way to transfer next items between users setup on Tracks. Maybe you can edit the action, select a user it needs to goto then save... and it appears in a &quot;Unassigned&quot; context in the other user's login.

If i remember correctly GTD does mention about the deligation of next actions...</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240410</id>
  <importance type="integer">1</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,bgwl_cUj4r4l7keJe5cbLr,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">258</number>
  <priority type="integer">5</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>1</status>
  <status-name>Accepted</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Transfer next actions between users</summary>
  <updated-at type="datetime">2012-04-16T12:10:39Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2007-06-13T16:18:34Z</created-on>
  <description>I'm pretty new to the Getting things done (GTD) system, but my brother is a big fan.
Tracks seems to support the process as he explained it, but it's a little disappointing that I can't delegate action to other users on my system.

I could do that I could imagine this becoming a killer app for my home system, as my wife could 'remind' me to do things and Vs versa.

I've very impressed with the look of your application, although it was a bit of a fiddle to get it working under debian linux.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240684</id>
  <importance type="integer">6</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>beAXGWk5ir35jEeJe5aVNr,czFbRE0eSr3zoYab7jnrAJ,bJxdBEGXar4yo2acwqjQXA,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">527</number>
  <priority type="integer">5</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Delegate actions to other users</summary>
  <updated-at type="datetime">2012-04-16T12:10:41Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">3</component-id>
  <created-on type="datetime">2008-01-05T07:10:43Z</created-on>
  <description>This is totally trivial, and purely a matter of taste (so feel free to ignore) but the two large dark grey areas (nav bar and new item entry) on the main page in trunk are really overwhelming to me. 1.04* always felt light and colorful to me, and this doesn't, and that somehow makes it slightly less fun to use. If I had my way, I'd strongly suggest dropping the grey-black in favor of the lighter gray that dominated the old layout.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240778</id>
  <importance type="integer">5</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">621</number>
  <priority type="integer">5</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>too dark?</summary>
  <updated-at type="datetime">2012-04-16T12:10:40Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2008-02-12T18:22:07Z</created-on>
  <description>Here's a quick and dirty patch which enables in place editor for preferences. Currently simple values and collections with boolean values are supported. Complex select fields like time zone, week start and due style don't work yet.
This patch doesn't contain any tests!

Patch it, go to &quot;Preferences&quot; and click on the yellow fields. Edit and press &quot;ok&quot;. That's it ;)</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240800</id>
  <importance type="integer">4</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>czFbRE0eSr3zoYab7jnrAJ,cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">643</number>
  <priority type="integer">5</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>[PATCH] Fun: Edit preferences in place using prototype's InPlaceEditor and InPlaceCollectionEditor</summary>
  <updated-at type="datetime">2012-04-16T12:10:40Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>czFbRE0eSr3zoYab7jnrAJ</id><login>bsag</login><login_name warning="deprecated">bsag</login_name><name>bsag</name><email>butshesagirl@rousette.org.uk</email></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
</custom-fields>
<CustomFields deprecated="use custom-fields">
</CustomFields>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer">2</component-id>
  <created-on type="datetime">2008-10-30T14:34:14Z</created-on>
  <description>Hi!

I have several hidden contexts. In sidebar a number of actions within that context is displayed.

However I find it very misleading to have (9 actions) near a context and after clicking it &quot;Currently there are no incomplete actions in this context&quot;...

I always think that I have something to be done but is not so. Can it be made configurable if actions count contain uncompleted, completed and total number of actions?</description>
  <from-support type="integer">0</from-support>
  <id type="integer">240947</id>
  <importance type="integer">3</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">54242</milestone-id>
  <notification-list>cF8gq42n4r3zEZab7jnrAJ</notification-list>
  <number type="integer">788</number>
  <priority type="integer">5</priority>
  <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
  <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Number of actions contains completed actions. Should be configurable</summary>
  <updated-at type="datetime">2011-02-08T09:23:53Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bgfq4qA1Gr2QjIaaaHk9wZ</id><login>Anonymous</login><login_name warning="deprecated">Anonymous</login_name><name>Anonymous</name></reporter>
<custom-fields>
<custom-field type="List" name="Type" id="3080">enhancement</custom-field>
<custom-field type="List" name="Severity" id="3081">normal</custom-field>
<custom-field type="List" name="Resolution" id="3082"></custom-field>
<custom-field type="Text" name="Keywords" id="3083"></custom-field>
<custom-field type="List" name="Version" id="3084"></custom-field>
</custom-fields>
<CustomFields deprecated="use custom-fields">
<CustomField type="List" name="Type" id="3080">enhancement</CustomField>
<CustomField type="List" name="Severity" id="3081">normal</CustomField>
<CustomField type="List" name="Resolution" id="3082"></CustomField>
<CustomField type="Text" name="Keywords" id="3083"></CustomField>
<CustomField type="List" name="Version" id="3084"></CustomField>
</CustomFields>
</ticket>
</tickets>

