<?xml version="1.0" encoding="UTF-8"?>
<tickets type="array">
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">4</component-id>
    <created-on type="datetime">2009-09-14T04:21:43+00:00</created-on>
    <description>tracks is frequently failing for me with:

Status: 500 Internal Server Error
  SQLite3::BusyException: database is locked: UPDATE &quot;sessions&quot; SET &quot;updated_at&quot; = '2009-09-14 04:08:16', &quot;data&quot; = 'BAh7CiIMdXNlcl9pZGkGIg5yZXR1cm4tdG8wIg1ub2V4cGlyeSIHb24iCmZs...

or related accesses to the &quot;sessions&quot; table.  I have not worked out exactly how to cause it, but I just hit it when going to the stats views page and only about half of the stats applets filled with data.  Sometimes I have to manually kill off fastcgi ruby processes to recover, but not this time.  Here's a stack from the most recent, followed by the collection of exception lines:

&lt;pre&gt;
Rendering /usr/local/www/tracks/public/500.html (500 Internal Server Error)
/!\ FAILSAFE /!\  Sun Sep 13 21:08:16 -0700 2009
  Status: 500 Internal Server Error
  SQLite3::BusyException: database is locked: UPDATE &quot;sessions&quot; SET &quot;updated_at&quot; = '2009-09-14 04:08:16', &quot;data&quot; = 'BAh7CiIMdXNlcl9pZGkGIg5yZXR1cm4tdG8wIg1ub2V4cGlyeSIH
b24iCmZs
YXNoSUM6J0FjdGlvbkNvbnRyb2xsZXI6OkZsYXNoOjpGbGFzaEhhc2h7AAY6
CkB1c2VkewA6EmpzX2JlaGF2aW91cnN7BzoMb3B0aW9uc3sHOhdyZWFwcGx5
X2FmdGVyX2FqYXhUOgpjYWNoZTA6CnJ1bGVzWwA=
' WHERE &quot;id&quot; = 6
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb:188:in `log'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:132:in `execute'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:372:in `catch_schema_changes'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:132:in `execute'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:177:in `update_sql'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:136:in `update_sql'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:49:in `update_without_query_dirty'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:18:in `update'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/base.rb:2708:in `update_without_lock'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/locking/optimistic.rb:70:in `update_without_dirty'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/dirty.rb:146:in `update_without_callbacks'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/callbacks.rb:253:in `update_without_timestamps'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/timestamp.rb:38:in `update'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/base.rb:2699:in `create_or_update_without_callbacks'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/callbacks.rb:222:in `create_or_update'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/base.rb:2383:in `save_without_validation'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/validations.rb:1009:in `save_without_dirty'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/dirty.rb:79:in `save_without_transactions'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/transactions.rb:179:in `send'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/transactions.rb:179:in `with_transaction_returning_status'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:66:in `transaction'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/transactions.rb:129:in `transaction'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/transactions.rb:138:in `transaction'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/transactions.rb:178:in `with_transaction_returning_status'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/transactions.rb:146:in `save'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/transactions.rb:158:in `rollback_active_record_state!'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/transactions.rb:146:in `save'
    /usr/local/www/tracks/vendor/rails/actionpack/lib/action_controller/session/active_record_store.rb:314:in `update'
    /usr/local/www/tracks/vendor/rails/activerecord/lib/active_record/base.rb:1398:in `silence'
    /usr/local/www/tracks/vendor/rails/actionpack/lib/action_controller/session/active_record_store.rb:314:in `update'
    /usr/local/www/tracks/vendor/rails/actionpack/lib/action_controller/session/active_record_store.rb:321:in `close'
    /usr/local/lib/ruby/1.8/cgi/session.rb:330:in `close'
    /usr/local/www/tracks/vendor/rails/actionpack/lib/action_controller/base.rb:1309:in `close_session'
    /usr/local/www/tracks/vendor/rails/actionpack/lib/action_controller/base.rb:1337:in `process_cleanup_without_session_management_support'
    /usr/local/www/tracks/vendor/rails/actionpack/lib/action_controller/session_management.rb:144:in `process_cleanup_without_components'
    /usr/local/www/tracks/vendor/rails/actionpack/lib/action_controller/components.rb:165:in `process_cleanup'
    /usr/local/www/tracks/vendor/rails/actionpack/lib/action_controller/base.rb:528:in `process_without_filters'
    /usr/local/www/tracks/vendor/rails/actionpack/lib/action_controller/filters.rb:606:in `process_without_session_management_support'
    /usr/local/www/tracks/vendor/rails/actionpack/lib/action_controller/session_management.rb:134:in `process'
    /usr/local/www/tracks/vendor/rails/actionpack/lib/action_controller/base.rb:392:in `process'
    /usr/local/www/tracks/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:183:in `handle_request'
    /usr/local/www/tracks/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:110:in `dispatch_unlocked'
    /usr/local/www/tracks/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:123:in `dispatch'
    /usr/local/www/tracks/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:122:in `synchronize'
    /usr/local/www/tracks/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:122:in `dispatch'
    /usr/local/www/tracks/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:132:in `dispatch_cgi'
    /usr/local/www/tracks/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:39:in `dispatch'
    /usr/local/www/tracks/vendor/rails/railties/lib/fcgi_handler.rb:101:in `process_request'
    /usr/local/www/tracks/vendor/rails/railties/lib/fcgi_handler.rb:151:in `with_signal_handler'
    /usr/local/www/tracks/vendor/rails/railties/lib/fcgi_handler.rb:99:in `process_request'
    /usr/local/www/tracks/vendor/rails/railties/lib/fcgi_handler.rb:76:in `process_each_request'
    /usr/local/lib/ruby/site_ruby/1.8/fcgi.rb:612:in `each_cgi'
    /usr/local/lib/ruby/site_ruby/1.8/fcgi.rb:609:in `each'
    /usr/local/lib/ruby/site_ruby/1.8/fcgi.rb:609:in `each_cgi'
    /usr/local/www/tracks/vendor/rails/railties/lib/fcgi_handler.rb:75:in `process_each_request'
    /usr/local/www/tracks/vendor/rails/railties/lib/fcgi_handler.rb:74:in `catch'
    /usr/local/www/tracks/vendor/rails/railties/lib/fcgi_handler.rb:74:in `process_each_request'
    /usr/local/www/tracks/vendor/rails/railties/lib/fcgi_handler.rb:49:in `process!'
    /usr/local/www/tracks/vendor/rails/railties/lib/fcgi_handler.rb:23:in `process!'
    /usr/local/www/tracks/public/dispatch.fcgi:24
&lt;/pre&gt;

Here are the different exceptions:

&lt;pre&gt;
kronos /usr/local/www/tracks/log $ grep Exception production.log | sed -e 's/2009-............../2009-xx-xx xx:xx:xx/' -e &quot;s/'BAh.*//&quot; | sort | uniq -c | sort -n
   1   SQLite3::BusyException: database is locked: SELECT * FROM &quot;sessions&quot; WHERE (session_id = 'd31cd8a4327ed49bfd34a7e12b43e9a0')  LIMIT 1
   1 ActiveRecord::StatementInvalid (SQLite3::BusyException: database is locked: SELECT * FROM &quot;sessions&quot; WHERE (session_id = '0f79bb1d804843e863c31a1dec8b566d')  LIMIT 1):
   1 ActiveRecord::StatementInvalid (SQLite3::BusyException: database is locked: SELECT * FROM &quot;sessions&quot; WHERE (session_id = 'd31cd8a4327ed49bfd34a7e12b43e9a0')  LIMIT 1):
   6 ActiveRecord::StatementInvalid (SQLite3::BusyException: database is locked: DELETE FROM &quot;sessions&quot; WHERE &quot;id&quot; = 9):
  12 ActiveRecord::StatementInvalid (SQLite3::BusyException: database is locked: DELETE FROM &quot;sessions&quot; WHERE &quot;id&quot; = 8):
  46 SQLite3::BusyException (database is locked):
  91 SQLite3::SQLException (cannot start a transaction within a transaction):
 121   SQLite3::BusyException: database is locked: UPDATE &quot;sessions&quot; SET &quot;updated_at&quot; = '2009-xx-xx xx:xx:xx', &quot;data&quot; =
 126 ActiveRecord::StatementInvalid (SQLite3::BusyException: database is locked: UPDATE &quot;sessions&quot; SET &quot;updated_at&quot; = '2009-xx-xx xx:xx:xx', &quot;data&quot; =
&lt;/pre&gt;

I just spotted the 'transaction within a transaction' error which might be easier to track down, here's a full stack:

&lt;pre&gt;
SQLite3::SQLException (cannot start a transaction within a transaction):
    /usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.4/lib/sqlite3/errors.rb:62:in `check'
    /usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.4/lib/sqlite3/resultset.rb:56:in `check'
    /usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.4/lib/sqlite3/resultset.rb:48:in `commence'
    /usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.4/lib/sqlite3/resultset.rb:38:in `initialize'
    /usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.4/lib/sqlite3/statement.rb:135:in `new'
    /usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.4/lib/sqlite3/statement.rb:135:in `execute'
    /usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.4/lib/sqlite3/database.rb:182:in `execute'
    /usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.4/lib/sqlite3/database.rb:157:in `prepare'
    /usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.4/lib/sqlite3/database.rb:181:in `execute'
    /usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.4/lib/sqlite3/database.rb:558:in `transaction'
    /vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:156:in `begin_db_transaction'
    /vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:372:in `catch_schema_changes'
    /vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:156:in `begin_db_transaction'
    /vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:63:in `transaction'
    /vendor/rails/activerecord/lib/active_record/transactions.rb:129:in `transaction'
    /vendor/rails/activerecord/lib/active_record/transactions.rb:138:in `transaction'
    /vendor/rails/activerecord/lib/active_record/transactions.rb:178:in `with_transaction_returning_status'
    /vendor/rails/activerecord/lib/active_record/transactions.rb:146:in `save'
    /vendor/rails/activerecord/lib/active_record/transactions.rb:158:in `rollback_active_record_state!'
    /vendor/rails/activerecord/lib/active_record/transactions.rb:146:in `save'
    /vendor/rails/actionpack/lib/action_controller/session/active_record_store.rb:314:in `update'
    /vendor/rails/activerecord/lib/active_record/base.rb:1398:in `silence'
    /vendor/rails/actionpack/lib/action_controller/session/active_record_store.rb:314:in `update'
    /vendor/rails/actionpack/lib/action_controller/session/active_record_store.rb:321:in `close'
    /usr/local/lib/ruby/1.8/cgi/session.rb:330:in `close'
    /vendor/rails/actionpack/lib/action_controller/base.rb:1309:in `close_session'
    /vendor/rails/actionpack/lib/action_controller/base.rb:1337:in `process_cleanup_without_session_management_support'
    /vendor/rails/actionpack/lib/action_controller/session_management.rb:144:in `process_cleanup_without_components'
    /vendor/rails/actionpack/lib/action_controller/components.rb:165:in `process_cleanup'
    /vendor/rails/actionpack/lib/action_controller/base.rb:528:in `process_without_filters'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:606:in `process_without_session_management_support'
    /vendor/rails/actionpack/lib/action_controller/session_management.rb:134:in `process'
    /vendor/rails/actionpack/lib/action_controller/base.rb:392:in `process'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:183:in `handle_request'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:110:in `dispatch_unlocked'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:123:in `dispatch'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:122:in `synchronize'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:122:in `dispatch'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:132:in `dispatch_cgi'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:39:in `dispatch'
    /vendor/rails/railties/lib/fcgi_handler.rb:101:in `process_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:151:in `with_signal_handler'
    /vendor/rails/railties/lib/fcgi_handler.rb:99:in `process_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:76:in `process_each_request'
    /usr/local/lib/ruby/site_ruby/1.8/fcgi.rb:612:in `each_cgi'
    /usr/local/lib/ruby/site_ruby/1.8/fcgi.rb:609:in `each'
    /usr/local/lib/ruby/site_ruby/1.8/fcgi.rb:609:in `each_cgi'
    /vendor/rails/railties/lib/fcgi_handler.rb:75:in `process_each_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:74:in `catch'
    /vendor/rails/railties/lib/fcgi_handler.rb:74:in `process_each_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:49:in `process!'
    /vendor/rails/railties/lib/fcgi_handler.rb:23:in `process!'
    /public/dispatch.fcgi:24
&lt;/pre&gt;</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">515698</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">947</number>
    <priority type="integer">2</priority>
    <reporter-id>d8ViwmN9Wr3QwpeJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>SQLite3::BusyException: database is locked:</summary>
    <updated-at type="datetime">2009-09-14T04:21:43+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-09-16T06:46:34+00:00</created-on>
    <description>Under Firefox 3.5.3:  Sometimes when the home page loads the first item on the page is 'checked'.  In this state the action can be completed by clicking on the checkmark anyway.  I've examined the source and the checkbox element isn't checked in the source.  I think it happens every time the tracks homepage is part of a session restored by Firefox.  It sometimes happens when reloading the homepage normally after it has been idle for some time (a habit I'm in because it seems like the 'new action' sidebar does not work on very stale loads of the home page).</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">519349</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">949</number>
    <priority type="integer">3</priority>
    <reporter-id>d8ViwmN9Wr3QwpeJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>sometimes first action is checked on home page</summary>
    <updated-at type="datetime">2009-09-16T06:46:34+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer" nil="true"></component-id>
    <created-on type="datetime">2009-09-19T19:22:03+00:00</created-on>
    <description>When you go to the Completed Tasks view (by clicking Done at the top), completed actions don't have tags that show up on the side. This is odd, since they do show up in the list of most recent completed actions on the home page.

It would be awesome if this could be included, either as a standard feature or as something that can be customized in preferences.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">524294</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">951</number>
    <priority type="integer">3</priority>
    <reporter-id>crGZ2wPvar3OzoeJe5afGb</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Tags don't show up in Completed Tasks view</summary>
    <updated-at type="datetime">2009-09-19T19:22:03+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer" nil="true"></component-id>
    <created-on type="datetime">2009-09-27T15:51:56+00:00</created-on>
    <description>Hello,
The http://my.tracks.url/todos.xml and other xml files that refert to task doesn't provid the tags of the todos.
Can be confirm using:
$ curl -u username:p4ssw0rd -H &quot;Content-Type: text/xml&quot; http://0.0.0.0:3000/todos.xml</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">534159</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">953</number>
    <priority type="integer">3</priority>
    <reporter-id>b3DcQQqbOr3RMteJe5afGb</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>REST API doesn't provite tags</summary>
    <updated-at type="datetime">2009-09-27T15:51:56+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
      <CustomField type="Text" name="Keywords" id="3083">api, tag</CustomField>
      <CustomField type="List" name="Version" id="3084">1.7</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-09-28T06:08:14+00:00</created-on>
    <description>I created a todo with an annual recurrence to start on a day in October of this year.  I accidentally made the 'recurring date' (distinct from the 'start') a month earlier, in September.  I realized this when I saw the event in the tickler as being in 2010.  I fixed the recurrence to be on the date matching the starting date (this year) but the upcoming event was still in 2010.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">534523</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">955</number>
    <priority type="integer">3</priority>
    <reporter-id>d8ViwmN9Wr3QwpeJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>modifying a recurrence doesn't update the next event</summary>
    <updated-at type="datetime">2009-09-28T06:08:14+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2009-12-04T04:28:56+00:00</created-on>
    <description>From an usage stand point, the previous layout without the drop box for edit /delete/ticklers was more convenient for every days use.
IMO, the best would be to have the star, completed box, delete and edit always visible on the left side and the 2 ticklers on the right as they were.
I use to update the tasks frequently, using the comment as a quick notepad, change the date, specially when a task is spread on several days.
I miss the drop box half the time as you have to go straight down then make a right to get into the box and click one of the 4 operations.
The instinct is to go diagonally to reach the edit, and then the box close before you reach it....
Or let the edit and star always visible (those are the most used buttons) and put the rest in the drop box.
(don't know what milestone, using Epall-Track downloaded on 12/02. Browser Chrome) </description>
    <from-support type="boolean">false</from-support>
    <id type="integer">719297</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">961</number>
    <priority type="integer">3</priority>
    <reporter-id>dQExfC38Cr3RlweJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Previous layout without drop box was more convenient to use</summary>
    <updated-at type="datetime">2009-12-04T04:28:56+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">enhancement</CustomField>
      <CustomField type="List" name="Version" id="3084">git-devel</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer" nil="true"></component-id>
    <created-on type="datetime">2009-12-08T16:46:20+00:00</created-on>
    <description>in config/site.yml, the comment implies that open_signup is about allowing 'anyone' to sign up for a username, whereas in my experience if open_signup=false even admins can't create new users.

So either there is a bug (open_signup=false should allow admins but not the general public to create users) or the description should be fixed.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">733241</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">962</number>
    <priority type="integer">3</priority>
    <reporter-id>ch8NGi5bGr3QkVeJe5afGb</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>config/site.yml implies that 'open_signup' is open</summary>
    <updated-at type="datetime">2009-12-08T16:46:20+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">6</component-id>
    <created-on type="datetime">2009-12-08T17:35:01+00:00</created-on>
    <description>We had to remove three tests in the migration to Rails 2.3.5 because we no longer have the right hooks at the Test::Unit layer to test these pieces of functionality. We should test them, though, at some other layer or with another tool.
&lt;pre&gt;&lt;code&gt;#in test/functional/todos_controller_test.rb
  def test_create_todo_via_xml_show_from
    login_as(:admin_user)

    assert_difference 'Todo.count' do
      xml = &quot;&lt;todo&gt;&lt;description&gt;Call Warren Buffet to find out how much he makes per day&lt;/description&gt;&lt;project_id&gt;#{projects(:timemachine).id}&lt;/project_id&gt;&lt;context_id&gt;#{contexts(:agenda).id}&lt;/context_id&gt;&lt;show-from type=\&quot;datetime\&quot;&gt;#{1.week.from_now.xmlschema}&lt;/show-from&gt;&lt;/todo&gt;&quot;

      # p parse_xml_body(xml)
      post :create, parse_xml_body(xml).update(:format =&gt; &quot;xml&quot;)
      assert_response :created
    end
  end

  def parse_xml_body(body)
    env = { 'rack.input' =&gt; StringIO.new(body),
      'HTTP_X_POST_DATA_FORMAT' =&gt; 'xml',
      'CONTENT_LENGTH'          =&gt; body.size.to_s }
    ActionController::RackRequest.new(env).request_parameters
  end&lt;/code&gt;&lt;/pre&gt;

&lt;pre&gt;&lt;code&gt;#in test/integration/context_xml_api_test.rb
  def test_fails_with_401_if_not_authorized_user
    authenticated_post_xml_to_context_create @@valid_postdata, 'nobody', 'nohow'
    assert_401_unauthorized
  end&lt;/code&gt;&lt;/pre&gt;


&lt;pre&gt;&lt;code&gt;# in test/integration/project_xml_api_test.rb
  def test_fails_with_401_if_not_authorized_user
    authenticated_post_xml_to_project_create @@valid_postdata, 'nobody', 'nohow'
    assert_401_unauthorized
  end&lt;/code&gt;&lt;/pre&gt;

</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">733443</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">965</number>
    <priority type="integer">3</priority>
    <reporter-id>c3AHgC1Wyr3A5uab7jnrAJ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Re-create tests deleted in Rails 2.3.5 migration</summary>
    <updated-at type="datetime">2009-12-08T17:35:01+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-12-09T17:51:39+00:00</created-on>
    <description>Running the latest dev master branch.  When I go into the repeating todos and click the edit icon, it just blinks.  If I click to add one, i get the form to fill out, but clicking &quot;create&quot; just blanks out the fields I had filled out with out adding the todo.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">737705</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">967</number>
    <priority type="integer">3</priority>
    <reporter-id>bAHywc2B4r3yj4ab7jnrAJ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>Recurring Todos Broken</summary>
    <updated-at type="datetime">2009-12-11T08:04:57+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
      <CustomField type="List" name="Version" id="3084">git-devel</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer" nil="true"></component-id>
    <created-on type="datetime">2009-12-15T18:07:46+00:00</created-on>
    <description>Reading a note of any length in mobile view is a bit of a pain, especially for first-time users- they won't realize that you have to edit and scroll, since the editable text area doesn't have a scroll bar (at least here.) (I just watched my wife fumble around with exactly this.) I'm not sure i have a good idea on how to deal with this, but it seems worth looking into; filing this so that it doesn't get lost in my head.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">756059</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">969</number>
    <priority type="integer">3</priority>
    <reporter-id>ch8NGi5bGr3QkVeJe5afGb</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>hard to read notes in mobile view</summary>
    <updated-at type="datetime">2009-12-15T18:07:46+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-12-20T00:11:34+00:00</created-on>
    <description>This was suspected by Henrik [[url:http://www.assembla.com/spaces/tracks-tickets/tickets/903-GUI-mockup-for-action-dependencies|here]].  If there are commas in the todo description, then that todo cannot be used as a &quot;depends on&quot; todo.  

here is the error you get: 
&lt;pre&gt;&lt;code&gt;1 error prohibited this action from being saved
There were problems with the following fields: 
Depends on: Could not find action '&quot;get drill,level,screw driver,velcro&quot; &lt;&quot;house&quot;; &quot;Shades are mounted&quot;&gt;'
&lt;/code&gt;&lt;/pre&gt;

Is there a way to escape the commas in the &quot;depends on&quot; field?  Or maybe filter them out of the description when saved?  Substitute a semicolon?</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">769801</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">975</number>
    <priority type="integer">3</priority>
    <reporter-id>bAHywc2B4r3yj4ab7jnrAJ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>todos with commas in description cannot be used as a dependency</summary>
    <updated-at type="datetime">2009-12-20T00:11:34+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
      <CustomField type="List" name="Version" id="3084">git-devel</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer" nil="true"></component-id>
    <created-on type="datetime">2009-12-27T21:34:55+00:00</created-on>
    <description>If I try to add an action through the API with its status set to completed and completed-at set to a date, this apparently succeeds but the action is actually added as active rather than completed, though its completed-at date remains set. I've tested that this wasn't merely bad XML or something by getting a completed action through the API, changing its ID, and putting it back in. I'll attach an XML file that should add a completed action when POSTed to http://localhost:3000/todos.xml but instead adds an active action.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">784797</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">977</number>
    <priority type="integer">3</priority>
    <reporter-id>djJKkQ8Y0r3OSceJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Can't add completed actions through API</summary>
    <updated-at type="datetime">2009-12-27T21:34:55+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer" nil="true"></component-id>
    <created-on type="datetime">2010-01-02T01:28:58+00:00</created-on>
    <description>So... it finally figured out why autocompletion not drawing from hidden projects/contexts bugs me. Basically, if I'm hiding a project, that is because I want to not be bothered by seeing it on a regular basis. But I still want to be able to quickly add tasks to that context- if anything, I want to add them *faster* because I want not to think about the project until later :)

So... yeah, autocomplete of project names should also look at hidden projects, and allow me to autocomplete from them.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">793867</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">979</number>
    <priority type="integer">3</priority>
    <reporter-id>ch8NGi5bGr3QkVeJe5afGb</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>autocomplete should complete from hidden projects/contexts</summary>
    <updated-at type="datetime">2010-01-02T01:28:58+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2010-01-04T13:27:11+00:00</created-on>
    <description>1. Fill in the new task form.
2. Either in the Due or Show from fields type in a number. Not a date, just a number.
3. Click Add action

There's a message saying &quot;An error occurred on the server.&quot;.

I think that it should say &quot;Invalid date&quot; or something more helpful.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">797561</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">982</number>
    <priority type="integer">3</priority>
    <reporter-id>dKrk6m97Kr3QVEeJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Server error when Due/Show from aren't legal</summary>
    <updated-at type="datetime">2010-01-04T13:31:24+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
      <CustomField type="List" name="Version" id="3084">1.7</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2010-01-04T13:30:55+00:00</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="boolean">false</from-support>
    <id type="integer">797569</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Allow entering partial dates</summary>
    <updated-at type="datetime">2010-01-04T13:30:55+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">enhancement</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2010-01-04T14:10:16+00:00</created-on>
    <description>1. In the new task form click in the Due or Show from fields to pop up the date selection thingo.
2. It is supposed to have little menus for easy months/years selection. Click and hold on the &quot;&gt;&gt;&quot; for the next years selection.

The menu doesn't appear. The other menus do. I guess it is off-screen or something.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">797715</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">984</number>
    <priority type="integer">3</priority>
    <reporter-id>dKrk6m97Kr3QVEeJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Year selection menu not visible</summary>
    <updated-at type="datetime">2010-01-04T14:10:16+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
      <CustomField type="List" name="Version" id="3084">1.7</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2010-01-07T11:03:33+00:00</created-on>
    <description>Preferences are set to have Sunday as the first day of the week.

In the calendar, though, sunday is still considered the last day of the week as shown by screen shot. See that the second task in &quot;Due in rest of this week&quot;. is due Monday. Monday is supposed to be in &quot;Due next week&quot;.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">810159</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">985</number>
    <priority type="integer">3</priority>
    <reporter-id>dKrk6m97Kr3QVEeJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Calendar still considers Monday as first day</summary>
    <updated-at type="datetime">2010-01-07T11:03:33+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
      <CustomField type="List" name="Version" id="3084">1.7</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2010-01-10T12:40:30+00:00</created-on>
    <description>1. Go to a project's page.
2. Mark it as completed.
It is marked as completed but it is still on the list of active projects in the sidebar.

I think it should move to the list of completed projects upon being marked.

I guess that this is also true for any project status change.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">820245</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">986</number>
    <priority type="integer">3</priority>
    <reporter-id>dKrk6m97Kr3QVEeJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>When project marked as completed it remains in the active list</summary>
    <updated-at type="datetime">2010-01-10T12:40:30+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
      <CustomField type="List" name="Version" id="3084">1.7</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer" nil="true"></component-id>
    <created-on type="datetime">2010-01-10T12:46:34+00:00</created-on>
    <description>At the bottom of the /integrations page there's a link to /feeds.m . Should that be so, and not it point to /feeds ?

The text it &quot;feeds provided by Tracks&quot;.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">820249</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">987</number>
    <priority type="integer">3</priority>
    <reporter-id>dKrk6m97Kr3QVEeJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>link to /feeds.m from /integrations</summary>
    <updated-at type="datetime">2010-01-10T12:46:34+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</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" nil="true"></completed-date>
    <component-id type="integer">6</component-id>
    <created-on type="datetime">2010-01-19T17:41:02+00:00</created-on>
    <description>Our current selenium-on-rails testing situation is sub-optimal and becoming unsupported. We've been talking about migrating to Selenium RC for a while, so let's make it happen!</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">853089</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">990</number>
    <priority type="integer">3</priority>
    <reporter-id>c3AHgC1Wyr3A5uab7jnrAJ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Migrate integration testing to Cucumber  + Selenium RC</summary>
    <updated-at type="datetime">2010-01-19T17:41:02+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Severity" id="3081">normal</CustomField>
      <CustomField type="Text" name="Keywords" id="3083">selenium</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2010-01-31T20:48:04+00:00</created-on>
    <description>When going to /feeds there is this Javascript error:
dateFormat is not defined in
http://tracks.kombinat-berlin.de/javascripts/cache/tracks_js.js?1264881129 on Line 37

On page /feeds when choosing another context/project for 'Feeds for incomplete actions in a specific context/project' there is also this Javascript error:
$(&quot;feeds-for-context&quot;).startWaiting is not a function or
$(&quot;feeds-for-project&quot;).startWaiting is not a function.



</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">900405</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">993</number>
    <priority type="integer">3</priority>
    <reporter-id>dypkjwdQGr35j8eJe5afGb</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>jQuery Error und page /feeds</summary>
    <updated-at type="datetime">2010-01-31T20:48:04+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
      <CustomField type="List" name="Severity" id="3081">normal</CustomField>
      <CustomField type="Text" name="Keywords" id="3083">jquery ajax</CustomField>
      <CustomField type="List" name="Version" id="3084">git-devel</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2010-02-09T20:01:43+00:00</created-on>
    <description>On the mobile add a new todo form [[url:http://tracks.homedns.org/todos/new?format=m|http://tracks.homedns.org/todos/new?format=m]] the month shows up in the drop down box as a number instead of the name of the month (at least on my tracks install).  I poked around, but nothing jumped out to me as the root cause.  If I create a todo and pick the 3rd number it comes out as March....

The _edit_mobile.rhtml is where the select list is created.  The select list has these numbers instead of the months (114 97 110 115 108 115 108 97 116 105 111 110).  I have pulled in the latest upstream changes and did rake db:migrate and rake gems:install...  the date select statement is below. 

&lt;pre&gt;&lt;code&gt;&lt;%= date_select(&quot;todo&quot;, &quot;due&quot;, {:order =&gt; [:day, :month, :year],
                    :start_year =&gt; this_year, :include_blank =&gt; '--'}, :tabindex =&gt; 7) %&gt;
&lt;/code&gt;&lt;/pre&gt;

</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">951489</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer" nil="true"></milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">995</number>
    <priority type="integer">3</priority>
    <reporter-id>bAHywc2B4r3yj4ab7jnrAJ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Month on mobile todo edit form does not show month names</summary>
    <updated-at type="datetime">2010-02-09T20:01:43+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
      <CustomField type="List" name="Version" id="3084">git-devel</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2005-09-02T01:12:51+00:00</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="boolean">false</from-support>
    <id type="integer">240253</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">140665</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>A smart &quot;Someday Maybe&quot; context.</summary>
    <updated-at type="datetime">2009-12-20T18:39:38+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2006-03-17T21:19:55+00:00</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="boolean">false</from-support>
    <id type="integer">240383</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">140665</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">233</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>add a 'followup' button next to 'delete' and 'edit'</summary>
    <updated-at type="datetime">2010-01-17T19:12:22+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-08-02T08:11:24+00:00</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="boolean">false</from-support>
    <id type="integer">240499</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">140665</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>group tasks by context in project view</summary>
    <updated-at type="datetime">2010-01-02T01:30:40+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2007-05-16T02:36:33+00:00</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="boolean">false</from-support>
    <id type="integer">240672</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">140665</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Project page UI needs to be streamlined</summary>
    <updated-at type="datetime">2009-12-20T18:42:27+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-01-18T16:05:54+00:00</created-on>
    <description>Sometimes, when looking at 'done' actions, I'd like to make actions active again- I closed one by accident, for example, or I want to add a note for later reference even after I've finished. I can't do this in the current 'done' view; it doesn't allow interaction with the actions. So:

it would be good if the 'done' view allowed editing and reopening of actions.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240790</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">140665</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">633</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>make the 'done' view more interactive</summary>
    <updated-at type="datetime">2010-01-17T19:14:48+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-02-09T17:45:26+00:00</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="boolean">false</from-support>
    <id type="integer">276426</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">140665</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>wysiwyg editor for notes</summary>
    <updated-at type="datetime">2009-12-20T18:43:21+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-02-24T21:44:16+00:00</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="boolean">false</from-support>
    <id type="integer">290132</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">140665</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">845</number>
    <priority type="integer">3</priority>
    <reporter-id>cw4_VCaRSr3QekeJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>addition of selectors to feed urls</summary>
    <updated-at type="datetime">2010-01-02T01:32:13+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">4</component-id>
    <created-on type="datetime">2009-04-18T13:29:35+00:00</created-on>
    <description>Hi,

I get the above error &quot;ActionView::TemplateError undefined method `name' for NullProject&quot; in the latest git version of Tracks on my Debian Lenny system when accessing a certain tagged todo item via http://tracksinstallation/tracks/todos/tag/foo.

However, the following patch fixes the issue for me:

http://cakelab.org/~kaner/tracks.diff
</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">340161</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">68514</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">880</number>
    <priority type="integer">2</priority>
    <reporter-id>bk95gqlbWr3PmReJe5afGb</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>&quot;ActionView::TemplateError undefined method `name' for NullProject&quot;</summary>
    <updated-at type="datetime">2009-05-18T18:21:00+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</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>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-05-02T21:44:57+00:00</created-on>
    <description>*Description*
When trying to view the tickler page, a 500 error was displayed, and the log revealed an error in 

&lt;code&gt;app/helpers/application_helper.rb:115:in `link_to_project'&lt;/code&gt;

*Probable cause*
An unknown (not easily reproducible) chain of editing events caused an inconsistency in the database, such that a NullProject reached the link_to_project method.

Changing the link_to_project method to:
&lt;pre&gt;&lt;code&gt;
  def link_to_project(project, descriptor = sanitize(project.name))
    if project.kind_of?(NullProject)
      return &quot;this is a null project&quot;
    end
    link_to( descriptor, project_path(project), :title =&gt; &quot;View project: #{project.name}&quot; )
  end
&lt;/code&gt;&lt;/pre&gt;
renders the tickler page without crashing, but the database is still in an inconsistent state and trying to edit the item (a recurring item) triggers another error:

&lt;code&gt;
ActiveRecord::RecordNotFound (Couldn't find Project with ID=24 AND (`projects`.user_id = 2)):
    /vendor/rails/activerecord/lib/active_record/base.rb:1528:in `find_one'
 &lt;/code&gt;

*Steps to reproduce*
This is not exactly the way to reproduce the behavior, but a similar inconsistent database state can be created by these steps:
1. Create a recurring action named t1, project t1, context any
2. Delete the project t1
3. Go to recurring actions and uncheck the done checkbox.
4. Search for t1 items
This will crash the search result page in a similar way.
</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">355635</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">68514</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">895</number>
    <priority type="integer">2</priority>
    <reporter-id>agEkPqn1Sr3On0eJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>Database inconsistency causes tickler page to crash</summary>
    <updated-at type="datetime">2009-05-18T18:21:38+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
      <CustomField type="List" name="Severity" id="3081">major</CustomField>
      <CustomField type="List" name="Version" id="3084">1.7RC</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-05-26T22:38:47+00:00</created-on>
    <description>In config/site.yml, I am setting a value for the &quot;subdirectory you're hosting tracks in&quot;:  subdir: &quot;/tracks&quot;

Accessing the mobile interface (&quot;/tracks/mobile&quot;) works for most things with two notable exceptions, when updating or canceling out of a todo and when logging in. The action works, but I am then redirected to a URL that does not contain the subdir setting.  For example, if I am edit a new todo, I click on the &quot;0-New Action&quot; link, and it correctly takes me to the &quot;/tracks/todos/new.m&quot; page.  If I then click &quot;Back&quot;, I am taken to the &quot;/mobile&quot; page.  I should be taken to the &quot;/tracks/mobile&quot; page.     This only happens when updating todos in the mobile interface.  The regular interface honors the subdir setting.

For the login redirection, it seems that the first time I log into tracks in both the mobile view and the regular view, it also does not honor the subdir setting.  For the mobile interface, I am taken to &quot;/mobile&quot;.  For the regular interface, I am taken to &quot;/&quot;.

I have mostly worked around this by adding specific rewrite rules in my apache config to deal with the various URLs that are generated from tracks.  This seems to work for all but the &quot;/&quot; redirect from the initial regular login page.  (I need to point that to something else, which is why I am running under a subdir in the first place.)

This problem was present in v1.6.  I recently upgraded to v1.7 hoping it was fixed.  But it is not, so I am opening the bug.  

I am available to answer any questions about the problem and any particulars about my install that might be helpful in solving the problem.

Thanks.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">382831</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">68514</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">908</number>
    <priority type="integer">3</priority>
    <reporter-id>cTLcBGsKer3Re8eJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>mobile todo update / cancel,back does not honor the subdir: config setting</summary>
    <updated-at type="datetime">2009-12-30T11:46:15+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
      <CustomField type="List" name="Severity" id="3081">normal</CustomField>
      <CustomField type="Text" name="Keywords" id="3083">mobile interface</CustomField>
      <CustomField type="List" name="Version" id="3084">1.7</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-07-14T11:37:48+00:00</created-on>
    <description>This error message shows up frequently in the log:

Processing ApplicationController#index (for 192.168.1.30 at 2009-07-14 21:35:09) [GET]
  Session ID: ee30ed54dc3b96de04c92bf047711c4a


ActionController::RoutingError (No route matches &quot;/tracks/images/menuarrow.gif&quot; with {:method=&gt;:get}):
    /vendor/rails/actionpack/lib/action_controller/routing/recognition_optimisation.rb:66:in `recognize_path'
    /vendor/rails/actionpack/lib/action_controller/routing/route_set.rb:386:in `recognize'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:182:in `handle_request'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:110:in `dispatch_unlocked'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:123:in `dispatch'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:122:in `synchronize'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:122:in `dispatch'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:132:in `dispatch_cgi'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:39:in `dispatch'
    /vendor/rails/railties/lib/fcgi_handler.rb:101:in `process_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:151:in `with_signal_handler'
    /vendor/rails/railties/lib/fcgi_handler.rb:99:in `process_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:76:in `process_each_request'
    /usr/lib/ruby/site_ruby/1.8/fcgi.rb:612:in `each_cgi'
    /usr/lib/ruby/site_ruby/1.8/fcgi.rb:609:in `each'
    /usr/lib/ruby/site_ruby/1.8/fcgi.rb:609:in `each_cgi'
    /vendor/rails/railties/lib/fcgi_handler.rb:75:in `process_each_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:74:in `catch'
    /vendor/rails/railties/lib/fcgi_handler.rb:74:in `process_each_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:49:in `process!'
    /vendor/rails/railties/lib/fcgi_handler.rb:23:in `process!'
    /public/dispatch.fcgi:24

Rendering /var/www/tracks/public/404.html (404 Not Found)

</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">436549</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">68514</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">925</number>
    <priority type="integer">3</priority>
    <reporter-id>cEbgCiCeGr3Q76eJe5afGb</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>No route matches &quot;/tracks/images/menuarrow.gif&quot;</summary>
    <updated-at type="datetime">2009-07-28T00:37:11+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
      <CustomField type="List" name="Severity" id="3081">normal</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-07-15T01:34:52+00:00</created-on>
    <description>I leave a browser with Tracks on it running continuously.  After a period of inactivity, the interface stops working.  For example, I can enter the details for a new task but it does not save.

Looking in the log I see messages like:

Processing LoginController#check_expiry (for 192.168.1.30 at 2009-07-15 10:54:42) [POST]
  Session ID: cfddf3714c8ae31ed63e16f6907421cd
  Parameters: {&quot;action&quot;=&gt;&quot;check_expiry&quot;, &quot;authenticity_token&quot;=&gt;&quot;3346e374707cbe0000a8d402b985ce852391e27c&quot;, &quot;controller&quot;=&gt;&quot;login&quot;}


ActionController::InvalidAuthenticityToken (ActionController::InvalidAuthenticityToken):
    /vendor/rails/actionpack/lib/action_controller/request_forgery_protection.rb:86:in `verify_authenticity_token'
    /vendor/rails/activesupport/lib/active_support/callbacks.rb:178:in `send'
    /vendor/rails/activesupport/lib/active_support/callbacks.rb:178:in `evaluate_method'
    /vendor/rails/activesupport/lib/active_support/callbacks.rb:166:in `call'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:225:in `call'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:629:in `run_before_filters'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:615:in `call_filters'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:610:in `perform_action_without_benchmark'
    /vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
    /usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
    /vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
    /vendor/rails/actionpack/lib/action_controller/rescue.rb:136:in `perform_action_without_caching'
    /vendor/rails/actionpack/lib/action_controller/caching/sql_cache.rb:13:in `perform_action'
    /vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache'
    /vendor/rails/activerecord/lib/active_record/query_cache.rb:8:in `cache'
    /vendor/rails/actionpack/lib/action_controller/caching/sql_cache.rb:12:in `perform_action'
    /vendor/rails/actionpack/lib/action_controller/base.rb:524:in `send'
    /vendor/rails/actionpack/lib/action_controller/base.rb:524:in `process_without_filters'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:606:in `process_without_session_management_support'
    /vendor/rails/actionpack/lib/action_controller/session_management.rb:134:in `process'
    /vendor/rails/actionpack/lib/action_controller/base.rb:392:in `process'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:183:in `handle_request'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:110:in `dispatch_unlocked'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:123:in `dispatch'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:122:in `synchronize'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:122:in `dispatch'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:132:in `dispatch_cgi'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:39:in `dispatch'
    /vendor/rails/railties/lib/fcgi_handler.rb:101:in `process_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:151:in `with_signal_handler'
    /vendor/rails/railties/lib/fcgi_handler.rb:99:in `process_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:76:in `process_each_request'
    /usr/lib/ruby/site_ruby/1.8/fcgi.rb:612:in `each_cgi'
    /usr/lib/ruby/site_ruby/1.8/fcgi.rb:609:in `each'
    /usr/lib/ruby/site_ruby/1.8/fcgi.rb:609:in `each_cgi'
    /vendor/rails/railties/lib/fcgi_handler.rb:75:in `process_each_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:74:in `catch'
    /vendor/rails/railties/lib/fcgi_handler.rb:74:in `process_each_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:49:in `process!'
    /vendor/rails/railties/lib/fcgi_handler.rb:23:in `process!'
    /public/dispatch.fcgi:24



Processing TodosController#check_deferred to js (for 192.168.1.30 at 2009-07-15 10:54:42) [POST]
  Session ID: cfddf3714c8ae31ed63e16f6907421cd
  Parameters: {&quot;authenticity_token&quot;=&gt;&quot;3346e374707cbe0000a8d402b985ce852391e27c&quot;}


ActionController::InvalidAuthenticityToken (ActionController::InvalidAuthenticityToken):
    /vendor/rails/actionpack/lib/action_controller/request_forgery_protection.rb:86:in `verify_authenticity_token'
    /vendor/rails/activesupport/lib/active_support/callbacks.rb:178:in `send'
    /vendor/rails/activesupport/lib/active_support/callbacks.rb:178:in `evaluate_method'
    /vendor/rails/activesupport/lib/active_support/callbacks.rb:166:in `call'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:225:in `call'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:629:in `run_before_filters'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:615:in `call_filters'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:610:in `perform_action_without_benchmark'
    /vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
    /usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
    /vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
    /vendor/rails/actionpack/lib/action_controller/rescue.rb:136:in `perform_action_without_caching'
    /vendor/rails/actionpack/lib/action_controller/caching/sql_cache.rb:13:in `perform_action'
    /vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache'
    /vendor/rails/activerecord/lib/active_record/query_cache.rb:8:in `cache'
    /vendor/rails/actionpack/lib/action_controller/caching/sql_cache.rb:12:in `perform_action'
    /vendor/rails/actionpack/lib/action_controller/base.rb:524:in `send'
    /vendor/rails/actionpack/lib/action_controller/base.rb:524:in `process_without_filters'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:606:in `process_without_session_management_support'
    /vendor/rails/actionpack/lib/action_controller/session_management.rb:134:in `process'
    /vendor/rails/actionpack/lib/action_controller/base.rb:392:in `process'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:183:in `handle_request'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:110:in `dispatch_unlocked'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:123:in `dispatch'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:122:in `synchronize'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:122:in `dispatch'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:132:in `dispatch_cgi'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:39:in `dispatch'
    /vendor/rails/railties/lib/fcgi_handler.rb:101:in `process_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:151:in `with_signal_handler'
    /vendor/rails/railties/lib/fcgi_handler.rb:99:in `process_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:76:in `process_each_request'
    /usr/lib/ruby/site_ruby/1.8/fcgi.rb:612:in `each_cgi'
    /usr/lib/ruby/site_ruby/1.8/fcgi.rb:609:in `each'
    /usr/lib/ruby/site_ruby/1.8/fcgi.rb:609:in `each_cgi'
    /vendor/rails/railties/lib/fcgi_handler.rb:75:in `process_each_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:74:in `catch'
    /vendor/rails/railties/lib/fcgi_handler.rb:74:in `process_each_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:49:in `process!'
    /vendor/rails/railties/lib/fcgi_handler.rb:23:in `process!'
    /public/dispatch.fcgi:24

Processing TodosController#auto_complete_for_tag (for 192.168.1.30 at 2009-07-15 11:21:31) [POST]
  Session ID: cfddf3714c8ae31ed63e16f6907421cd
  Parameters: {&quot;tag_list&quot;=&gt;&quot;st&quot;}
Completed in 22ms (View: 4, DB: 230) | 200 OK [http://www/tracks/todos/auto_complete_for_tag]


Processing TodosController#create (for 192.168.1.30 at 2009-07-15 11:21:39) [POST]
  Session ID: cfddf3714c8ae31ed63e16f6907421cd
  Parameters: {&quot;_source_view&quot;=&gt;&quot;tag&quot;, &quot;authenticity_token&quot;=&gt;&quot;3346e374707cbe0000a8d402b985ce852391e27c&quot;, &quot;default_context_name&quot;=&gt;&quot;@Inbox&quot;, &quot;default_project_name&quot;=&gt;&quot;&quot;, &quot;context_name&quot;=&gt;&quot;Shopping&quot;, &quot;tag_list&quot;=&gt;&quot;starred&quot;, &quot;todo&quot;=&gt;{&quot;show_from&quot;=&gt;&quot;&quot;, &quot;notes&quot;=&gt;&quot;&quot;, &quot;description&quot;=&gt;&quot;Buy colour cartidge 95&quot;, &quot;due&quot;=&gt;&quot;&quot;}, &quot;project_name&quot;=&gt;&quot;&quot;}


ActionController::InvalidAuthenticityToken (ActionController::InvalidAuthenticityToken):
    /vendor/rails/actionpack/lib/action_controller/request_forgery_protection.rb:86:in `verify_authenticity_token'
    /vendor/rails/activesupport/lib/active_support/callbacks.rb:178:in `send'
    /vendor/rails/activesupport/lib/active_support/callbacks.rb:178:in `evaluate_method'
    /vendor/rails/activesupport/lib/active_support/callbacks.rb:166:in `call'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:225:in `call'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:629:in `run_before_filters'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:615:in `call_filters'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:610:in `perform_action_without_benchmark'
    /vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
    /usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
    /vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
    /vendor/rails/actionpack/lib/action_controller/rescue.rb:136:in `perform_action_without_caching'
    /vendor/rails/actionpack/lib/action_controller/caching/sql_cache.rb:13:in `perform_action'
    /vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache'
    /vendor/rails/activerecord/lib/active_record/query_cache.rb:8:in `cache'
    /vendor/rails/actionpack/lib/action_controller/caching/sql_cache.rb:12:in `perform_action'
    /vendor/rails/actionpack/lib/action_controller/base.rb:524:in `send'
    /vendor/rails/actionpack/lib/action_controller/base.rb:524:in `process_without_filters'
    /vendor/rails/actionpack/lib/action_controller/filters.rb:606:in `process_without_session_management_support'
    /vendor/rails/actionpack/lib/action_controller/session_management.rb:134:in `process'
    /vendor/rails/actionpack/lib/action_controller/base.rb:392:in `process'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:183:in `handle_request'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:110:in `dispatch_unlocked'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:123:in `dispatch'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:122:in `synchronize'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:122:in `dispatch'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:132:in `dispatch_cgi'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:39:in `dispatch'
    /vendor/rails/railties/lib/fcgi_handler.rb:101:in `process_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:151:in `with_signal_handler'
    /vendor/rails/railties/lib/fcgi_handler.rb:99:in `process_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:76:in `process_each_request'
    /usr/lib/ruby/site_ruby/1.8/fcgi.rb:612:in `each_cgi'
    /usr/lib/ruby/site_ruby/1.8/fcgi.rb:609:in `each'
    /usr/lib/ruby/site_ruby/1.8/fcgi.rb:609:in `each_cgi'
    /vendor/rails/railties/lib/fcgi_handler.rb:75:in `process_each_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:74:in `catch'
    /vendor/rails/railties/lib/fcgi_handler.rb:74:in `process_each_request'
    /vendor/rails/railties/lib/fcgi_handler.rb:49:in `process!'
    /vendor/rails/railties/lib/fcgi_handler.rb:23:in `process!'
    /public/dispatch.fcgi:24


No error message is given to the user as to why the task was not saved.  Reloading the page fixes the problem until it times out again.

The application should give some indication that a timeout has occurred.  If this timeout is for 'security reasons' then the information shown on the screen should be removed.
</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">437861</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">68514</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">927</number>
    <priority type="integer">3</priority>
    <reporter-id>cEbgCiCeGr3Q76eJe5afGb</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Web interface stops working after a period of inactivity</summary>
    <updated-at type="datetime">2009-07-15T01:34:52+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
      <CustomField type="List" name="Severity" id="3081">normal</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-11-12T22:03:51+00:00</created-on>
    <description>Environment:
Running Tracks 1.7 from the Turnkey Linux, the ISO can be downloaded from the following location: http://www.turnkeylinux.org/tracks

Problem:
There are GUI/Functionality issues with Internet Explorer v.7.0.5730.13

Please reference the attached AVI file to get a better understanding of the issues.

In short, the drag and drop features are not functional and editing a 'Context' topic doesn't work.  Tracks works great within the Firefox browser, but is plagued with functionality issues within IE.

Thanks,
Roy Hernandez</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">626777</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">68514</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">959</number>
    <priority type="integer">3</priority>
    <reporter-id>bQZGVIZ9mr3R0meJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>IE7 Problems</summary>
    <updated-at type="datetime">2009-11-12T22:03:51+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
      <CustomField type="List" name="Severity" id="3081">major</CustomField>
      <CustomField type="Text" name="Keywords" id="3083">IE7</CustomField>
      <CustomField type="List" name="Version" id="3084">1.7</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer" nil="true"></component-id>
    <created-on type="datetime">2010-01-31T15:27:07+00:00</created-on>
    <description>I have a running and working Tracks 1.7 server with lighttpd and FastCGI with following configuration:
http://dominikschuermann.de/index.php/2010/01/lighttpd-fastcgi-rails-tracks-on-debian-lenny/

I want to sync between Shuffle ( http://code.google.com/p/android-shuffle/ ) and this Tracks installation.

When I start the server using webrick over 3000 everything works.
When I am using the installation over lighttpd as described above only the items from tracks are synced to Shuffle but the items from shuffle are not synced back to tracks.
I think the problem is lighttpd, one possibility is that the POST reqeust are not getting through.

Is there anything wrong in my configuration over lighttpd as described in my blogpost? Any ideas what can cause this problems?</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">899761</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">68514</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">992</number>
    <priority type="integer">3</priority>
    <reporter-id>cn5VVadNSr34h7eJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Sync failing between Tracks on Lighttpd and Shuffle</summary>
    <updated-at type="datetime">2010-01-31T21:08:47+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
      <CustomField type="List" name="Version" id="3084">1.7</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id>d1FPhUbMSr3QZReJe5aVNr</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer" nil="true"></component-id>
    <created-on type="datetime">2009-03-01T14:34:38+00:00</created-on>
    <description>When trying to edit an action while in &quot;Home page&quot; view, the following output appears:


&lt;pre&gt;&lt;code&gt;
$(&quot;form_todo_105&quot;).down(&quot;.placeholder&quot;).update(&quot;\u003Cdiv id=\&quot;error_status\&quot;\u003E\u003C/div\u003E\n\n\u003Cinput id=\&quot;todo_id\&quot; name=\&quot;todo[id]\&quot; type=\&quot;hidden\&quot; value=\&quot;105\&quot; /\u003E\u003Cinput id=\&quot;_source_view\&quot; name=\&quot;_source_view\&quot; type=\&quot;hidden\&quot; value=\&quot;todo\&quot; /\u003E\n\u003Clabel for=\&quot;description_todo_105\&quot;\u003EDescription\u003C/label\u003E\n\u003Cinput id=\&quot;todo_description\&quot; maxlength=\&quot;100\&quot; name=\&quot;todo[description]\&quot; size=\&quot;30\&quot; tabindex=\&quot;8\&quot; type=\&quot;text\&quot; value=\&quot;test2\&quot; /\u003E\n\n\u003Clabel for=\&quot;notes_todo_105\&quot;\u003ENotes\u003C/label\u003E\n\u003Ctextarea cols=\&quot;29\&quot; id=\&quot;todo_notes\&quot; name=\&quot;todo[notes]\&quot; rows=\&quot;4\&quot; tabindex=\&quot;9\&quot;\u003E\u003C/textarea\u003E\n\n\u003Cdiv class=\&quot;project_input\&quot;\u003E\n\u003Clabel for=\&quot;project_name_todo_105\&quot;\u003EProject\u003C/label\u003E\n\u003Cinput id=\&quot;project_name_todo_105\&quot; name=\&quot;project_name\&quot; autocomplete=\&quot;off\&quot; tabindex=\&quot;10\&quot; size=\&quot;30\&quot; type=\&quot;text\&quot; value=\&quot;None\&quot; /\u003E\n\u003Cdiv class=\&quot;page_name_auto_complete\&quot; id=\&quot;project_list_todo_105\&quot; style=\&quot;display:none\&quot;\u003E\u003C/div\u003E\n\n\u003Cscript type=\&quot;text/javascript\&quot;\u003E\nproject_autocompleter_todo_105 = new Autocompleter.Local('project_name_todo_105', 'project_list_todo_105', ['None'], {choices:100,autoSelect:false});\nfunction selectDefaultContext() {\n  todoContextNameElement = $('context_name_todo_105');\n  defaultContextName = $('todo_context_name').projectDefaultContextsMap[this.value];\n  if (defaultContextName \u0026\u0026 !todoContextNameElement.editedByTracksUser) {\n    todoContextNameElement.value = defaultContextName;\n  }\n}\nEvent.observe($('project_name_todo_105'), \&quot;focus\&quot;, project_autocompleter_todo_105.activate.bind(project_autocompleter_todo_105));\nEvent.observe($('project_name_todo_105'), \&quot;click\&quot;, project_autocompleter_todo_105.activate.bind(project_autocompleter_todo_105));\nEvent.observe($('project_name_todo_105'), \&quot;blur\&quot;, selectDefaultContext.bind($('project_name_todo_105')));\n\u003C/script\u003E\n\u003C/div\u003E\n\n\u003Cdiv class=\&quot;context_input\&quot;\u003E\n\u003Clabel for=\&quot;context_name_todo_105\&quot;\u003EContext\u003C/label\u003E\n\u003Cinput id=\&quot;context_name_todo_105\&quot; name=\&quot;context_name\&quot; autocomplete=\&quot;off\&quot; tabindex=\&quot;11\&quot; size=\&quot;30\&quot; type=\&quot;text\&quot; value=\&quot;2\&quot; /\u003E\n\u003Cdiv class=\&quot;page_name_auto_complete\&quot; id=\&quot;context_list_todo_105\&quot; style=\&quot;display:none\&quot;\u003E\u003C/div\u003E\n\n\u003Cscript type=\&quot;text/javascript\&quot;\u003E\ncontext_autocompleter_todo_105 = new Autocompleter.Local('context_name_todo_105', 'context_list_todo_105', ['1','2'], {choices:100,autoSelect:false});\nEvent.observe($('context_name_todo_105'), \&quot;focus\&quot;, function(){ $('context_name_todo_105').editedByTracksUser = true; });\nEvent.observe($('context_name_todo_105'), \&quot;focus\&quot;, context_autocompleter_todo_105.activate.bind(context_autocompleter_todo_105));\nEvent.observe($('context_name_todo_105'), \&quot;click\&quot;, context_autocompleter_todo_105.activate.bind(context_autocompleter_todo_105));\n\u003C/script\u003E\n\u003C/div\u003E\n\n\u003Clabel class=\&quot;tag_list_label\&quot; for=\&quot;tag_list_todo_105\&quot;\u003ETags (separate with commas)\u003C/label\u003E\n\u003Cinput id=\&quot;tag_list_todo_105\&quot; name=\&quot;tag_list\&quot; size=\&quot;30\&quot; tabindex=\&quot;12\&quot; type=\&quot;text\&quot; value=\&quot;\&quot; /\u003E \n\n\u003Cdiv class=\&quot;due_input\&quot;\u003E\n\u003Clabel for=\&quot;due_label_todo_105\&quot;\u003EDue\u003C/label\u003E\n\u003Cinput autocomplete=\&quot;off\&quot; class=\&quot;Date\&quot; id=\&quot;due_todo_105\&quot; name=\&quot;todo[due]\&quot; onfocus=\&quot;Calendar.setup\&quot; size=\&quot;12\&quot; tabindex=\&quot;13\&quot; type=\&quot;text\&quot; value=\&quot;\&quot; /\u003E\n\u003Ca href=\&quot;#\&quot; id=\&quot;due_x_todo_105\&quot; class=\&quot;date_clear\&quot; title=\&quot;Clear due date\&quot;\u003E\n\t\u003Cimg alt=\&quot;Clear due date\&quot; src=\&quot;/images/delete_off.png?1234167236\&quot; /\u003E\n\u003C/a\u003E\n\u003C/div\u003E\n\n\u003Cdiv class=\&quot;show_from_input\&quot;\u003E\n\u003Clabel for=\&quot;show_from_todo_105\&quot;\u003EShow from\u003C/label\u003E\n\u003Cinput autocomplete=\&quot;off\&quot; class=\&quot;Date\&quot; id=\&quot;show_from_todo_105\&quot; name=\&quot;todo[show_from]\&quot; onfocus=\&quot;Calendar.setup\&quot; size=\&quot;12\&quot; tabindex=\&quot;14\&quot; type=\&quot;text\&quot; value=\&quot;\&quot; /\u003E\n\u003Ca href=\&quot;#\&quot; id=\&quot;show_from_x_todo_105\&quot; class=\&quot;date_clear\&quot; title=\&quot;Clear show from date\&quot;\u003E\n\t\u003Cimg alt=\&quot;Clear show from date\&quot; src=\&quot;/images/delete_off.png?1234167236\&quot; /\u003E\n\u003C/a\u003E\n\u003C/div\u003E\n\n\n\u003Cdiv class=\&quot;submit_box\&quot;\u003E\n  \u003Cdiv class=\&quot;widgets\&quot;\u003E\n    \u003Cbutton type=\&quot;submit\&quot; class=\&quot;positive\&quot; id=\&quot;submit_todo_105\&quot; tabindex=\&quot;15\&quot;\u003E\n        \u003Cimg alt=\&quot;\&quot; src=\&quot;/images/accept.png?1234167236\&quot; /\u003E\n        Update\n    \u003C/button\u003E\n    \u003Ca href=\&quot;javascript:void(0);\&quot; onclick=\&quot;Element.toggle('line_todo_105');Element.toggle('edit_todo_105');\&quot; class=\&quot;negative\&quot;\u003E\n        \u003Cimg alt=\&quot;\&quot; src=\&quot;/images/cancel.png?1234167236\&quot; /\u003E\n        Cancel\n    \u003C/a\u003E\n  \u003C/div\u003E\n\u003C/div\u003E\n        \n\u003Cscript type=\&quot;text/javascript\&quot;\u003E\n//\u003C![CDATA[\nCalendar.setup({ ifFormat:\&quot;%d/%m/%Y\&quot;,firstDay:0,showOthers:true,range:[2004, 2010],step:1,inputField:\&quot;due_todo_105\&quot;,cache:true,align:\&quot;TR\&quot; })\n\n//]]\u003E\n\u003C/script\u003E\n\u003Cscript type=\&quot;text/javascript\&quot;\u003E\n//\u003C![CDATA[\nCalendar.setup({ ifFormat:\&quot;%d/%m/%Y\&quot;,firstDay:0,showOthers:true,range:[2004, 2010],step:1,inputField:\&quot;show_from_todo_105\&quot;,cache:true,align:\&quot;TR\&quot; })\n\n//]]\u003E\n\u003C/script\u003E\n&quot;);
$(&quot;line_todo_105&quot;).hide();
$(&quot;edit_todo_105&quot;).show();
$(&quot;form_todo_105&quot;).down(&quot;input#todo_description&quot;).focus();
&lt;/code&gt;&lt;/pre&gt;

This will occur if the action is assigned to a Context different from the first one displayed on the Home page (for example the second or third context displayed).
If you try to edit the action from &quot;Context&quot; view, or from &quot;Project&quot; view (if a project is assigned) - the edit of the action is possible.
</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">293782</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">68514</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">847</number>
    <priority type="integer">4</priority>
    <reporter-id>d1FPhUbMSr3QZReJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Opera: Can't edit actions directly from &quot;Home&quot; page when the action is assigned to a context different from the first one displayed.</summary>
    <updated-at type="datetime">2009-05-18T18:20:24+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
      <CustomField type="List" name="Severity" id="3081">major</CustomField>
      <CustomField type="List" name="Resolution" id="3082"></CustomField>
      <CustomField type="Text" name="Keywords" id="3083">action, context, error, opera</CustomField>
      <CustomField type="List" name="Version" id="3084">1.7RC</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-04-09T16:03:56+00:00</created-on>
    <description>Illustrate by example: In creating a new action - the context &quot;write&quot; is the defaulted context. When using tab from project to context the drop-down appears (sometimes - often first in the session) with selection of contexts starting with &quot;W&quot; (the &quot;W&quot; is in bold&quot;). Then I select &quot;Write&quot; - however then &quot;rite&quot; is added in the context line - creating &quot;Writerite&quot;.

In theory - there should be no drop-down as default context is inserted already

This did not occur in pre 1.7 versions. I'm using firefox (latest).</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">330855</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">68514</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">874</number>
    <priority type="integer">4</priority>
    <reporter-id>dZ9lwYjr0r3Rl6eJe5afGb</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Context drop-downs not recognizing default word</summary>
    <updated-at type="datetime">2009-05-18T18:19:52+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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.7</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-05-25T07:49:25+00:00</created-on>
    <description>There is no edit icon, I can only remove or star the tasks.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240875</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">716</number>
    <priority type="integer">2</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Todos on the search results page cannot be eddited</summary>
    <updated-at type="datetime">2009-04-07T19:44:14+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-11-30T19:27:03+00:00</created-on>
    <description>from: http://github.com/bsag/tracks/commit/35ae5fc43109ecbc6bc8796753bbe63ff7c9309d

Hack to flashobject_helper plugin (upgrade to Rails 2.2-compatible 
version if/when it comes out.)
</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240955</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">796</number>
    <priority type="integer">2</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>upgrade to Rails 2.2-compatible  version of flashobject_helper plugin</summary>
    <updated-at type="datetime">2009-04-07T19:55:49+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">task</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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-04-20T07:59:34+00:00</created-on>
    <description>js not synced with changes in active and hidden contexts</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">341247</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">886</number>
    <priority type="integer">2</priority>
    <reporter-id>cF8gq42n4r3zEZab7jnrAJ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>added context from context page does not show up</summary>
    <updated-at type="datetime">2010-01-13T01:44:59+00:00</updated-at>
    <working-hours type="float">1.0</working-hours>
    <working-hour type="float">1.0</working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2009-05-10T02:25:12+00:00</created-on>
    <description>When I hover over the triangle to open the popup to edit/delete things, I find I have to do it a few times because it disappears too quickly. last commit I have 0938....6ca0
Firefox 3.5 Beta 4. Seems okay on Epiphany.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">363789</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">898</number>
    <priority type="integer">2</priority>
    <reporter-id>dNOMkopqGr3Qs_eJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Edit popup for actions goes away too quickly</summary>
    <updated-at type="datetime">2010-01-13T01:58:48+00:00</updated-at>
    <working-hours type="float">0.75</working-hours>
    <working-hour type="float">0.75</working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-12-29T05:11:17+00:00</created-on>
    <description>This seems similar to ticket 825.

After upgrading to today's git rev, the cached CSS files have paths like /tracks/tracks/images/...  This diff fixes the problem but I don't know if it's really the right thing:

&lt;pre&gt;&lt;code&gt;
kronos /usr/local/www/tracks $ git diff
diff --git a/vendor/plugins/bundle-fu/lib/bundle_fu.rb b/vendor/plugins/bundle-f
index 8cc20b4..75e795f 100644
--- a/vendor/plugins/bundle-fu/lib/bundle_fu.rb
+++ b/vendor/plugins/bundle-fu/lib/bundle_fu.rb
@@ -19,7 +19,7 @@ class BundleFu
           next
         end

-        output &lt;&lt; (yield(filename, content)||&quot;&quot;)
+        output &lt;&lt; (yield(filename_no_root, content)||&quot;&quot;)
       }
       output
     end
&lt;/code&gt;&lt;/pre&gt;</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">787445</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">978</number>
    <priority type="integer">2</priority>
    <reporter-id>d8ViwmN9Wr3QwpeJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>bundle-fu relative urls incorrect</summary>
    <updated-at type="datetime">2009-12-29T05:11:17+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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>c3AHgC1Wyr3A5uab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2005-06-10T18:29:16+00:00</created-on>
    <description>When you've got a next-action that is really a project, it would be nice to one-button convert it from actions to project, so allow multiple actions on that item.  Sub-projects might need to implemented to do this right, but that makes sense...

I have Project A, and realize that Action item B isn't really an action item, so it's really Project B.  Right now, I have to manually do that, create a Project B... </description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240198</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">64</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">4</status>
    <story-importance type="integer">0</story-importance>
    <summary>Convert Actions to Project </summary>
    <updated-at type="datetime">2009-12-20T18:36:53+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2007-02-05T04:27:56+00:00</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="boolean">false</from-support>
    <id type="integer">240590</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></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">1</status>
    <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">2009-04-07T19:41:26+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-02-20T10:59:31+00:00</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="boolean">false</from-support>
    <id type="integer">240802</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">645</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>add 'Done' state to contexts</summary>
    <updated-at type="datetime">2009-04-07T19:43:54+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-06-16T09:36:45+00:00</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="boolean">false</from-support>
    <id type="integer">240895</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></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">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>Alter YAML export to use yaml_db plugin</summary>
    <updated-at type="datetime">2009-04-07T19:45:00+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-08-28T13:42:38+00:00</created-on>
    <description>Notes need html sanitization. I've just wrote down a note with an unpaird xml tag and my browser stopped displaying the notes properly.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240924</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">765</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>sanitize html output in toggle_notes</summary>
    <updated-at type="datetime">2009-04-07T19:47:07+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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"></CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-10-14T19:58:35+00:00</created-on>
    <description>When I add a link to a note with the format:
&quot;this is a link&quot;:http://www.sitetolinkto.com/foo/bar/baz.html
The link url gets cut off at 30 chars. However, if I open the note up, the link has the entire url and it works.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240939</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">780</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Links in Notes get cut off on project home page</summary>
    <updated-at type="datetime">2009-04-07T19:48:31+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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.7</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-11-11T12:59:59+00:00</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="boolean">false</from-support>
    <id type="integer">240949</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">790</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>add a &quot;dropped&quot;-state for actions</summary>
    <updated-at type="datetime">2009-04-07T19:51:05+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-11-30T19:29:15+00:00</created-on>
    <description>Hacks to resource_feeder plugin, for Rails 2.2 compatibility. Should 
check for official release (not likely) or move off it.
</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240957</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">798</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Should  check for official release resource_feeder plugin</summary>
    <updated-at type="datetime">2009-04-07T19:53:30+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">task</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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-01-11T18:45:56+00:00</created-on>
    <description>The '&gt;' and '&lt;' characters are not displayed properly in todo descriptions. Due to a double sanitation with both h() and sanitize() the characters are shown as literal HTML entities, e.g. &amp;gt; is shown in the todo description. The naive fix is to remove the h() call, but unfortunately that would introduce #740 again, so it looks like we need a bit more advanced sanitation here.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">251705</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">824</number>
    <priority type="integer">3</priority>
    <reporter-id>bBp5Jm2mOr3yFdab7jnrAJ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>The '&gt;' and '&lt;' characters are not displayed properly in todo descriptions</summary>
    <updated-at type="datetime">2009-02-15T20:54:47+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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">sanitation</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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-01-17T09:11:16+00:00</created-on>
    <description>It will be easier to deffer tasks on wide screens.

http://github.com/vitaliel/tracks/commits/master
commit  e1a13fffcc22ac4376ae2d1a864a32b17ab9bdba

PS: I receive github error for commit page, but it is there.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">256597</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">829</number>
    <priority type="integer">3</priority>
    <reporter-id>cBtTkkPDir2O7YaaeP0Qfc</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>[Patch] use alternate colors for todo list</summary>
    <updated-at type="datetime">2009-04-08T07:53:51+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-02-20T00:02:45+00:00</created-on>
    <description>Double newlines create p tags but single new lines fail to make br tags.  The end result is that notes don't render the way they are entered.  According to some notes in /lib/redcloth.rb, it looks like a change of default behavior.  Adding hard_breaks fixes it.

&lt;pre&gt;
--- ./app/controllers/application.rb.dist       2009-02-19 17:53:32.000000000 -0600
+++ ./app/controllers/application.rb    2009-02-19 17:53:59.000000000 -0600
@@ -125,7 +125,7 @@
   # otherwise it only handles Textile
   #
   def markdown(text)
-    RedCloth.new(text).to_html
+    RedCloth.new(text, [:hard_breaks]).to_html
   end

   def build_default_project_context_name_map(projects)
&lt;/pre&gt;</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">285850</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">843</number>
    <priority type="integer">3</priority>
    <reporter-id>bs8LLc-rqr3BZveJe5afGb</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Newline rendering in notes is scetchy.</summary>
    <updated-at type="datetime">2009-02-22T11:11:28+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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">git-devel</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2009-03-05T13:43:05+00:00</created-on>
    <description>trying to using bullet lists (beginning with star '* ') does not gives bullets in notes view. Also text is too big and there is no indentation on '**'. Another thing is that I'd like to have possibility to see whole note on a project page like it is for action - now it is only possible to go to separate view and it has some problem with styles.
</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">297600</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">849</number>
    <priority type="integer">3</priority>
    <reporter-id>dcBQMyccir3ORbeJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>problem with textile formatting in notes view </summary>
    <updated-at type="datetime">2009-03-10T13:37:55+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-03-21T04:29:48+00:00</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="boolean">false</from-support>
    <id type="integer">311670</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></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>
    <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">2009-03-21T07:37:07+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-03-21T04:32:40+00:00</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="boolean">false</from-support>
    <id type="integer">311671</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>&quot;Deferred actions&quot; in starred view will not stay collapsed</summary>
    <updated-at type="datetime">2009-03-27T14:49:17+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-04-22T07:12:25+00:00</created-on>
    <description>put more info in 500 error message. We get quite a few support questions that start with 'I got an error 500. Could you help?&quot; In several cases just pointing them to the log file is enough. So why not mention this in the error 500 message?</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">344050</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">887</number>
    <priority type="integer">3</priority>
    <reporter-id>cF8gq42n4r3zEZab7jnrAJ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>put more info in 500 error message</summary>
    <updated-at type="datetime">2009-04-22T07:12:25+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-06-30T07:18:27+00:00</created-on>
    <description>enable downloading of a gmail module so you can add tracks to the gmail sidebar. Thanks to GTDify for the code

http://www.getontracks.org/forums/viewthread/434/ </description>
    <from-support type="boolean">false</from-support>
    <id type="integer">421691</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">920</number>
    <priority type="integer">3</priority>
    <reporter-id>cF8gq42n4r3zEZab7jnrAJ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>add tracks to gmail sidebar</summary>
    <updated-at type="datetime">2009-06-30T07:18:27+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">enhancement</CustomField>
      <CustomField type="List" name="Severity" id="3081">normal</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id>dvyFKeAw0r3QaieJe5aVNr</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-07-05T14:16:54+00:00</created-on>
    <description>I want to close actions from the tickler, so that I don't have to delete them.

I think this is just copy &amp; paste of the code in the home-view, i set the severity to trivial.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">427201</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">922</number>
    <priority type="integer">3</priority>
    <reporter-id>dvyFKeAw0r3QaieJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>Add &quot;completed-checkbox&quot; to the tickler-view</summary>
    <updated-at type="datetime">2009-07-05T14:17:12+00:00</updated-at>
    <working-hours type="float">1.0</working-hours>
    <working-hour type="float">1.0</working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">enhancement</CustomField>
      <CustomField type="List" name="Severity" id="3081">trivial</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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-08-20T08:36:43+00:00</created-on>
    <description>After editing and updating an action, editing and cancelling any action makes the menu for that action impossible to activate again.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">480242</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">932</number>
    <priority type="integer">3</priority>
    <reporter-id>agEkPqn1Sr3On0eJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Action item menu not working after edit/update-&gt;edit/cancel</summary>
    <updated-at type="datetime">2009-08-21T07:17:52+00:00</updated-at>
    <working-hours type="float">4.0</working-hours>
    <working-hour type="float">4.0</working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
      <CustomField type="List" name="Severity" id="3081">minor</CustomField>
      <CustomField type="Text" name="Keywords" id="3083">gui, javascript, ajax</CustomField>
      <CustomField type="List" name="Version" id="3084">git-devel</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-08-25T13:01:04+00:00</created-on>
    <description>I'm in the context view. The new-todo-form defaults to the current context. I start to enter new todo and select a project. The context is changes to the default context of the project. I think it is more logical to not change the context if you are in the context view because if you are working in a specific context it is most likely that you want to add a new todo to that context.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">487147</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">934</number>
    <priority type="integer">3</priority>
    <reporter-id>cF8gq42n4r3zEZab7jnrAJ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>defaults in new-todo-form in context view not logical</summary>
    <updated-at type="datetime">2009-08-25T13:01:04+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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>cF8gq42n4r3zEZab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">4</component-id>
    <created-on type="datetime">2009-09-07T10:53:05+00:00</created-on>
    <description>we query on state column quite often, so we could use a index on them</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">505695</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">936</number>
    <priority type="integer">3</priority>
    <reporter-id>cF8gq42n4r3zEZab7jnrAJ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>add indexes to state columns</summary>
    <updated-at type="datetime">2009-09-07T10:53:25+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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>c3AHgC1Wyr3A5uab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-09-08T01:21:22+00:00</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="boolean">false</from-support>
    <id type="integer">507519</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></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">4</status>
    <story-importance type="integer">0</story-importance>
    <summary>Patch Adds Sortable and Dragable Todo Items</summary>
    <updated-at type="datetime">2009-10-24T17:27:41+00:00</updated-at>
    <working-hours type="float">6.0</working-hours>
    <working-hour type="float">6.0</working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer" nil="true"></component-id>
    <created-on type="datetime">2009-12-14T07:20:51+00:00</created-on>
    <description>It would be good if the blank database:

* didn't include bsag's email as the admin email; maybe blank or an obviously dummy email? (People who don't know about bsag's involvement are likely to be confused by it.)

* had default contexts for new users: home, office, computer, phone, errands, waitingfor, someday-maybe (hidden by default) might be a good default set?</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">750113</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">968</number>
    <priority type="integer">3</priority>
    <reporter-id>ch8NGi5bGr3QkVeJe5afGb</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>suggested improvements to 'blank' db</summary>
    <updated-at type="datetime">2009-12-14T07:20:51+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Severity" id="3081">minor</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-12-17T10:04:38+00:00</created-on>
    <description>in project view with one todo A. The todo has a dependency B. When I add a new todo and drag it on B, todo A is not updated to reflect change.

The resulting js should replace todo A with updated partial</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">762953</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">972</number>
    <priority type="integer">3</priority>
    <reporter-id>cF8gq42n4r3zEZab7jnrAJ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>todo not updates when dependency added to dependency</summary>
    <updated-at type="datetime">2009-12-17T10:04:38+00:00</updated-at>
    <working-hours type="float">1.0</working-hours>
    <working-hour type="float">1.0</working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer" nil="true"></component-id>
    <created-on type="datetime">2009-12-22T22:33:51+00:00</created-on>
    <description>After living with the drop-down menu for todos for some time now, I'm thinking we might want to move the edit button back out of it. Editing todos happens a lot (at least for me), whereas the other actions are secondary. Hitting the dropdown mouseover can be annoying, and I think moving edit out will get rid of most of the complaints.

What do you think?</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">777059</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">976</number>
    <priority type="integer">3</priority>
    <reporter-id>c3AHgC1Wyr3A5uab7jnrAJ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Move edit button out of menu?</summary>
    <updated-at type="datetime">2009-12-22T22:33:51+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>c3AHgC1Wyr3A5uab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2010-01-19T10:14:06+00:00</created-on>
    <description>loading the feeds page results in js errors. selecting a feed does not update links.

we need tests for this :-) Got to get selenium-rc running...</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">851291</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">989</number>
    <priority type="integer">3</priority>
    <reporter-id>cF8gq42n4r3zEZab7jnrAJ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>selecting context or project in feeds page does not update links</summary>
    <updated-at type="datetime">2010-01-19T10:14:06+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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>c3AHgC1Wyr3A5uab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2010-02-02T00:46:17+00:00</created-on>
    <description>Install from the latest zipball yields the following error on startup, likely due to an incompatibility of the packaged soap version and ruby 1.9.

&lt;pre&gt;&lt;code&gt;prompt&gt; rails -v
Rails 2.3.5
prompt&gt; gem -v
1.3.5
prompt&gt; ruby -v
ruby 1.9.1p243 (2009-07-16 revision 24175) [arm-linux]
prompt&gt; script/server -e production
=&gt; Booting WEBrick
=&gt; Rails 2.3.5 application starting on http://0.0.0.0:3000
/opt/lib/ruby/gems/1.9.1/gems/soap4r-1.5.8/lib/xsd/charset.rb:13: warning: variable $KCODE is no longer effective
/opt/lib/ruby/gems/1.9.1/gems/soap4r-1.5.8/lib/xsd/charset.rb:132: warning: encoding option is ignored - NONE
/opt/lib/ruby/gems/1.9.1/gems/soap4r-1.5.8/lib/xsd/charset.rb:137: warning: encoding option is ignored - NONE
/opt/lib/ruby/gems/1.9.1/gems/soap4r-1.5.8/lib/xsd/charset.rb:137:in `initialize': invalid multibyte escape: /\A(?:[\x9\xa\xd\x20-\x7F]|(?:[\x8E\xA1-\xFE][\xA1-\xFE])|(?:\x8F[\xA1-\xFE][\xA1-\xFE]))*\z/ (RegexpError)
    from /opt/lib/ruby/gems/1.9.1/gems/soap4r-1.5.8/lib/xsd/charset.rb:137:in `new'
    from /opt/lib/ruby/gems/1.9.1/gems/soap4r-1.5.8/lib/xsd/charset.rb:137:in `&lt;module:Charset&gt;'
    from /opt/lib/ruby/gems/1.9.1/gems/soap4r-1.5.8/lib/xsd/charset.rb:12:in `&lt;module:XSD&gt;'
    from /opt/lib/ruby/gems/1.9.1/gems/soap4r-1.5.8/lib/xsd/charset.rb:9:in `&lt;top (required)&gt;'
    from /volume1/web/tracks/vendor/rails/activesupport/lib/active_support/dependencies.rb:158:in `require'
    from /volume1/web/tracks/vendor/rails/activesupport/lib/active_support/dependencies.rb:158:in `require'
    from /opt/lib/ruby/gems/1.9.1/gems/soap4r-1.5.8/lib/soap/soap.rb:10:in `&lt;top (required)&gt;'
    from /volume1/web/tracks/vendor/rails/activesupport/lib/active_support/dependencies.rb:158:in `require'
    from /volume1/web/tracks/vendor/rails/activesupport/lib/active_support/dependencies.rb:158:in `require'
    from /opt/lib/ruby/gems/1.9.1/gems/soap4r-1.5.8/lib/soap/rpc/driver.rb:9:in `&lt;top (required)&gt;'
    from /volume1/web/tracks/vendor/rails/activesupport/lib/active_support/dependencies.rb:158:in `require'
    from /volume1/web/tracks/vendor/rails/activesupport/lib/active_support/dependencies.rb:158:in `require'
    from /volume1/web/tracks/vendor/gems/datanoise-actionwebservice-2.3.2/lib/action_web_service/client/soap_client.rb:1:in `&lt;top (required)&gt;'
    from /volume1/web/tracks/vendor/rails/activesupport/lib/active_support/dependencies.rb:158:in `require'
    from /volume1/web/tracks/vendor/rails/activesupport/lib/active_support/dependencies.rb:158:in `require'
    from /volume1/web/tracks/vendor/gems/datanoise-actionwebservice-2.3.2/lib/action_web_service/client.rb:2:in `&lt;top (required)&gt;'
    from /volume1/web/tracks/vendor/rails/activesupport/lib/active_support/dependencies.rb:158:in `require'
    from /volume1/web/tracks/vendor/rails/activesupport/lib/active_support/dependencies.rb:158:in `require'
    from /volume1/web/tracks/vendor/gems/datanoise-actionwebservice-2.3.2/lib/action_web_service.rb:40:in `&lt;top (required)&gt;'
    from /volume1/web/tracks/vendor/rails/activesupport/lib/active_support/dependencies.rb:158:in `require'
    from /volume1/web/tracks/vendor/rails/activesupport/lib/active_support/dependencies.rb:158:in `require'
    from /volume1/web/tracks/vendor/gems/datanoise-actionwebservice-2.3.2/lib/actionwebservice.rb:1:in `&lt;top (required)&gt;'
    from /volume1/web/tracks/vendor/rails/activesupport/lib/active_support/dependencies.rb:158:in `require'
    from /volume1/web/tracks/vendor/rails/activesupport/lib/active_support/dependencies.rb:158:in `require'
    from /volume1/web/tracks/vendor/rails/railties/lib/rails/gem_dependency.rb:208:in `load'
    from /volume1/web/tracks/vendor/rails/railties/lib/initializer.rb:307:in `block in load_gems'
    from /volume1/web/tracks/vendor/rails/railties/lib/initializer.rb:307:in `each'
    from /volume1/web/tracks/vendor/rails/railties/lib/initializer.rb:307:in `load_gems'
    from /volume1/web/tracks/vendor/rails/railties/lib/initializer.rb:169:in `process'
    from /volume1/web/tracks/vendor/rails/railties/lib/initializer.rb:113:in `run'
    from /volume1/web/tracks/config/environment.rb:17:in `&lt;top (required)&gt;'
    from /volume1/web/tracks/vendor/rails/activesupport/lib/active_support/dependencies.rb:156:in `require'
    from /volume1/web/tracks/vendor/rails/activesupport/lib/active_support/dependencies.rb:156:in `block in require'
    from /volume1/web/tracks/vendor/rails/activesupport/lib/active_support/dependencies.rb:521:in `new_constants_in'
    from /volume1/web/tracks/vendor/rails/activesupport/lib/active_support/dependencies.rb:156:in `require'
    from /volume1/web/tracks/vendor/rails/railties/lib/commands/server.rb:84:in `&lt;top (required)&gt;'
    from script/server:3:in `require'
    from script/server:3:in `&lt;main&gt;'  
&lt;/code&gt;&lt;/pre&gt;
</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">905751</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">994</number>
    <priority type="integer">3</priority>
    <reporter-id>a2qznuQtur3RTceJe5afGb</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Soap incompatibility with ruby 1.9</summary>
    <updated-at type="datetime">2010-02-02T10:04:32+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
      <CustomField type="List" name="Severity" id="3081">major</CustomField>
      <CustomField type="Text" name="Keywords" id="3083">soap ruby 1.9</CustomField>
      <CustomField type="List" name="Version" id="3084">git-devel</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2007-07-04T02:53:49+00:00</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="boolean">false</from-support>
    <id type="integer">240692</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">535</number>
    <priority type="integer">4</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Attaching files</summary>
    <updated-at type="datetime">2009-04-07T19:41:47+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-01-19T17:35:31+00:00</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="boolean">false</from-support>
    <id type="integer">240792</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">635</number>
    <priority type="integer">4</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>Show created_at on todo items.</summary>
    <updated-at type="datetime">2009-04-07T19:43:15+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-06-04T19:24:27+00:00</created-on>
    <description>The N810 contains a browser based on Firefox 3 Alpha 1.  When connecting to Tracks, I get a http login prompt (not the normal login webpage) then end up at a page titled XML Feed.  It is a long string of data unformatted, and I see my tasks, html tags, as well as some additional information.  It is not interactive or usable.  IIRC, it did the same on my N800 with the Opera 8.5 browser, so perhaps something Nokia-specific in the useragent is causing the output to change?  I just want the standard desktop interface - right now using the mobile one but the full one should be theoretically compatible with the browser.  (It apparently worked sometime pre-1.5 sine I saw screenshots online.)</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240884</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">725</number>
    <priority type="integer">4</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Standard Tracks interface does not load on Nokia N810 browser</summary>
    <updated-at type="datetime">2009-04-07T19:44:37+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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"></CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-12-08T07:07:39+00:00</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="boolean">false</from-support>
    <id type="integer">240959</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">800</number>
    <priority type="integer">4</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>User management</summary>
    <updated-at type="datetime">2009-04-07T19:53:56+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2009-04-24T04:28:34+00:00</created-on>
    <description>After my adjustment of Tracks to take up the entire window width using absolute positioning of the sidebar (instead of percentages), it ends up looking bad on wide screens. The best I could do to fix this was to set up auto margins on the #content div and give it a max-width, but that left the sidebar detached over on the right side (see attached image). I've attached a patch with the small changes I tried, but I'm really not enough of a CSS guru to do this.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">346639</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">889</number>
    <priority type="integer">4</priority>
    <reporter-id>c3AHgC1Wyr3A5uab7jnrAJ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>Maximum width with good layout</summary>
    <updated-at type="datetime">2009-04-25T08:02:05+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">defect</CustomField>
      <CustomField type="List" name="Severity" id="3081">minor</CustomField>
      <CustomField type="Text" name="Keywords" id="3083">CSS,layout,design</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" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2009-09-28T06:05:30+00:00</created-on>
    <description>The blue 'tag' boxes on the recurring task view look like you could click them, but you cannot.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">534521</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">954</number>
    <priority type="integer">4</priority>
    <reporter-id>d8ViwmN9Wr3QwpeJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>tags in the recurring task view are not clickable</summary>
    <updated-at type="datetime">2010-01-02T01:28:04+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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">tags, recurring</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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-10-30T14:34:14+00:00</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="boolean">false</from-support>
    <id type="integer">240947</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54252</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Number of actions contains completed actions. Should be configurable</summary>
    <updated-at type="datetime">2009-04-07T19:50:44+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-08-24T21:00:47+00:00</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="boolean">false</from-support>
    <id type="integer">240526</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">371</number>
    <priority type="integer">2</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Goals</summary>
    <updated-at type="datetime">2008-12-25T22:02:18+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-08-28T06:23:51+00:00</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="boolean">false</from-support>
    <id type="integer">240528</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">373</number>
    <priority type="integer">2</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Support for subprojects</summary>
    <updated-at type="datetime">2009-05-07T18:01:38+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2007-07-30T21:45:04+00:00</created-on>
    <description>I'm using the truck version. Performance of the home page seems much slower then previous versions. Included is the log of rendering the home page.
hajee004s:/Library/WebServer/Documents/tracks/current root# script/server
=&gt; Booting Mongrel (use 'script/server webrick' to force WEBrick)
=&gt; Rails application starting on http://0.0.0.0:3000
=&gt; Call with -d to detach
=&gt; Ctrl-C to shutdown server
** Starting Mongrel listening at 0.0.0.0:3000
** Starting Rails with development environment...
has_many_polymorphs: Rails environment detected
has_many_polymorphs: loaded ok
SwitchEnvironmentController: missing default helper path switch_environment_helper
UnobtrusiveJavascriptController: missing default helper path unobtrusive_javascript_helper
has_many_polymorphs: autoload hook invoked
has_many_polymorphs: INIT
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready.  TERM =&gt; stop.  USR2 =&gt; restart.  INT =&gt; stop (no restart).
** Rails signals registered.  HUP =&gt; reload (without restart).  It might not work well.
** Mongrel available at 0.0.0.0:3000
** Use CTRL-C to stop.
  SQL (0.000479)   SET SQL_AUTO_IS_NULL=0
  Tagging Columns (0.004406)   SHOW FIELDS FROM taggings
  Todo Columns (0.005293)   SHOW FIELDS FROM todos
has_many_polymorphs: injecting dependencies
has_many_polymorphs: preloaded parent model Tag


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


Processing
  Session ID: 055722f63fe444e76e91c24f5c92e09b
  Parameters: {&quot;page_path&quot;=&gt;[&quot;index.js&quot;], &quot;action&quot;=&gt;&quot;generate&quot;, &quot;controller&quot;=&gt;&quot;unobtrusive_javascript&quot;}
Completed in 0.00646 (154 reqs/sec) | Rendering: 0.00018 (2%) | DB: 0.00000 (0%) | 200 OK &quot;&quot;:http://hajee004s/behaviours/index.js
</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240699</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">542</number>
    <priority type="integer">2</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>Performance of the home page, seems slow</summary>
    <updated-at type="datetime">2008-12-25T22:18:55+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2005-04-09T22:05:54+00:00</created-on>
    <description>Feature request.  It would be useful to view, in chronological order, a list of next actions assigned a due date across all contexts and projects.  </description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240165</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">31</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>View of date-assigned actions</summary>
    <updated-at type="datetime">2008-12-25T21:25:29+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>bgfq4qA1Gr2QjIaaaHk9wZ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2005-04-27T06:49:43+00:00</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="boolean">false</from-support>
    <id type="integer">240181</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>True Multi-User Capability</summary>
    <updated-at type="datetime">2009-01-16T18:04:41+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2005-04-29T12:29:31+00:00</created-on>
    <description>It will be convenient to do assignment of responsible persons for task</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240183</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Do assignment of responsible persons</summary>
    <updated-at type="datetime">2008-12-25T21:27:41+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2005-07-14T05:50:50+00:00</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="boolean">false</from-support>
    <id type="integer">240220</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Ideas for better context selection</summary>
    <updated-at type="datetime">2008-12-25T21:32:23+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2005-07-29T12:57:08+00:00</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="boolean">false</from-support>
    <id type="integer">240228</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Reorder next actions</summary>
    <updated-at type="datetime">2009-05-07T17:35:42+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2005-08-07T02:55:39+00:00</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="boolean">false</from-support>
    <id type="integer">240234</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Smarter sidebar</summary>
    <updated-at type="datetime">2009-01-16T18:04:43+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2005-08-10T11:52:34+00:00</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="boolean">false</from-support>
    <id type="integer">240241</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Context at top in sidebar</summary>
    <updated-at type="datetime">2008-12-25T21:34:50+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2005-08-25T17:28:16+00:00</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="boolean">false</from-support>
    <id type="integer">240245</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>display feed in sidebar</summary>
    <updated-at type="datetime">2009-01-08T10:16:50+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2005-09-08T20:50:19+00:00</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="boolean">false</from-support>
    <id type="integer">240257</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Feature Request: Grid View of actions</summary>
    <updated-at type="datetime">2009-01-08T10:16:50+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2005-09-30T09:58:20+00:00</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="boolean">false</from-support>
    <id type="integer">240265</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Move complete project to another context</summary>
    <updated-at type="datetime">2009-01-08T10:16:50+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2005-10-01T06:46:11+00:00</created-on>
    <description>For my periodic actions such as paying bills, I like to be able to move them forward a month after i pay the bill for this month without having to manually edit, edit date, and update.

This just provides a &quot;&gt;&gt;&quot; link for dated actions that causes the action to be advanced by 1 month.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240266</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">126</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>patch: move action forward 1 month behavior</summary>
    <updated-at type="datetime">2009-01-08T10:16:51+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2005-12-10T06:08:47+00:00</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="boolean">false</from-support>
    <id type="integer">240322</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>view for projects with no active next actions.</summary>
    <updated-at type="datetime">2008-12-25T21:43:57+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2005-12-12T20:30:42+00:00</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="boolean">false</from-support>
    <id type="integer">240324</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>currnetly working on item:</summary>
    <updated-at type="datetime">2009-01-08T10:16:51+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2005-12-29T17:59:22+00:00</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="boolean">false</from-support>
    <id type="integer">240330</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Adding Tree (Parent/Child) Relationships to Contexts &amp; Projects</summary>
    <updated-at type="datetime">2009-01-08T10:16:52+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-01-01T14:37:15+00:00</created-on>
    <description>I find that when I create a project, I often come up with several future actions. However, these actions are sequential, i.e. action 3 depends upon the completion of action 2, action 2 on action 1, etc. As such, I only want to see the next action (action 1), and not the follow-up actions (2,3).  Looking through previous tickets, I noticed that others have requested a similar feature, though it appears that the current version of Tracks (svn revision 170) does not yet support this.

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

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

A side benefit of adding an active flag to actions/projects is that it could also be used to for the Someday/Maybe context; any actions/projects added to Someday/Maybe could be marked as inactive so that they are not shown in the 'Home' display.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240332</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">185</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>Add support for follow-up/sequential actions.</summary>
    <updated-at type="datetime">2009-01-08T10:16:52+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2006-01-05T08:07:02+00:00</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="boolean">false</from-support>
    <id type="integer">240335</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>New notes view is redundant</summary>
    <updated-at type="datetime">2008-12-25T21:45:06+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2006-01-15T15:19:09+00:00</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="boolean">false</from-support>
    <id type="integer">240346</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <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">2009-01-08T10:16:52+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>bgfq4qA1Gr2QjIaaaHk9wZ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-01-27T22:05:29+00:00</created-on>
    <description>Any ideals on how we could facilitate the work needed to translate you're system.  Please write me at bernier.thomas@gmail.com.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240351</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">202</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>Would like to help translate Tracks to other languages</summary>
    <updated-at type="datetime">2009-01-16T18:04:44+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-02-13T10:47:27+00:00</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="boolean">false</from-support>
    <id type="integer">240355</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>Gentoo ebuild</summary>
    <updated-at type="datetime">2009-01-08T10:16:53+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-02-17T13:21:16+00:00</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="boolean">false</from-support>
    <id type="integer">240360</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>provide some information on GTD concepts?</summary>
    <updated-at type="datetime">2008-12-25T21:47:51+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-03-02T02:46:05+00:00</created-on>
    <description>Dragging and dropping between contexts would allow &quot;state changes&quot;.  I find this helpful when a next action can move from &quot;do something&quot; to &quot;waiting for something&quot; without additional editing.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240369</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">220</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Drag and drop between contexts</summary>
    <updated-at type="datetime">2009-01-16T18:04:44+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2006-03-20T13:56:06+00:00</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="boolean">false</from-support>
    <id type="integer">240386</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Req: Tracks as Hipster Composer</summary>
    <updated-at type="datetime">2009-01-08T10:16:53+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-03-25T15:06:23+00:00</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="boolean">false</from-support>
    <id type="integer">240391</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>email management</summary>
    <updated-at type="datetime">2009-01-08T10:16:54+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-05-03T22:23:08+00:00</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="boolean">false</from-support>
    <id type="integer">240429</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>add duration estimation for activity</summary>
    <updated-at type="datetime">2009-04-23T22:54:24+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-05-12T07:02:33+00:00</created-on>
    <description>As the summary says: multiple languages. Maybe a default set by the admin, and a user configurable setting in the preferences? That would be great..
</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240438</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">283</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Multiple languages</summary>
    <updated-at type="datetime">2009-01-08T10:16:55+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-05-18T23:11:14+00:00</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="boolean">false</from-support>
    <id type="integer">240449</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>re-arranging action items and reflecting it in feed order</summary>
    <updated-at type="datetime">2009-01-08T10:16:55+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>bgfq4qA1Gr2QjIaaaHk9wZ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-05-23T15:19:53+00:00</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="boolean">false</from-support>
    <id type="integer">240450</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Meta Refresh Prefrence on Main Page?</summary>
    <updated-at type="datetime">2009-01-16T18:04:45+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-05-27T05:58:39+00:00</created-on>
    <description>I ran into an odd error tonight. I was trying to add an action with the word &quot;ssh&quot; in it, and nothing seemed to be happening when I clicked the &quot;Add Action&quot; button. Using FireBug and reviewing logs, I determined that the request was being sent to apache but no further and was coming back to the browser as &quot;412 Precondition Failed&quot;. I believe this is some mod_security setting at my hosting provider, because I was able to add the action by inserting spaces (&quot;s s h&quot;). Tracks' javascript should handle this error condition and similar ones by notifying the user that the action was not added due to an error and provide whatever information is available.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240453</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">298</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>add new action ajax doesn't handle 412 Precondition Failed very well</summary>
    <updated-at type="datetime">2009-01-16T18:04:46+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>agEkPqn1Sr3On0eJe5aVNr</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-06-02T15:36:22+00:00</created-on>
    <description>Projects are an excellent way of defining lots of next actions into a group with a singular goal, but what do you do about NAs that depends on another NA to be completed?

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

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

h3. Proposal for todo FSM with added pending state
!http://www.assembla.com/spaces/tracks-tickets/documents/dD_W-EIQar3QxReJe5afGb/download/todo_fsm.png!</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240455</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">300</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>Next Action Dependencies</summary>
    <updated-at type="datetime">2009-08-16T20:12:37+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-06-12T04:09:24+00:00</created-on>
    <description>The ability to subscribe to a remote iCal in the project section.

</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240460</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Subscribe to a remote iCal To Do list</summary>
    <updated-at type="datetime">2009-01-08T10:16:56+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2006-06-24T05:59:26+00:00</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="boolean">false</from-support>
    <id type="integer">240464</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Display multiple contexts in a single list</summary>
    <updated-at type="datetime">2009-01-08T10:16:56+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-06-27T11:12:08+00:00</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="boolean">false</from-support>
    <id type="integer">240467</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Applescript for the creation of new projects?</summary>
    <updated-at type="datetime">2009-01-08T10:16:56+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-07-01T01:13:10+00:00</created-on>
    <description>I love the look of the new nav bar in trunk, but it has some significant usability issues.

1) When your window is scrolled down toward the bottom of a page and then you use the New Action accesskey to expand the form and focus the cursor in the description field, the page will scroll up high enough to show the form field, which puts it squarely behind the translucent bar.

2) When using firefox's Find feature to look for a particular action on the page, the browser will scroll the page enough to bring that action into the viewport, but it's very hard to see because it's behind the nav bar.

I don't have a good solution in mind. I'm cross-posting this to the mailing list to solicit ideas.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240470</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">315</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>nav bar usability issues</summary>
    <updated-at type="datetime">2008-12-25T21:57:35+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-07-05T18:35:33+00:00</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="boolean">false</from-support>
    <id type="integer">240472</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>&quot;relative&quot; due date entry?</summary>
    <updated-at type="datetime">2009-01-08T10:16:57+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-07-17T06:01:53+00:00</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="boolean">false</from-support>
    <id type="integer">240479</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>User can apply a variety of visual themes</summary>
    <updated-at type="datetime">2009-01-16T18:04:47+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-07-26T22:37:42+00:00</created-on>
    <description>In terms of user interface, I find it a little awkward that &quot;Preferences&quot; calls up a page that *reports* preferences, but then one still has to click &quot;Edit preferences&quot; to *change* them. It's very rare that I would seek out the preferences without the intention to make a change. And more than once I've clicked on the settings on that first page in a vain effort to change them as if they were text boxes and not just read-only reports.

Is there any reason why there couldn't simply be the one preferences page, from which one can either see or change the settings?</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240492</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">337</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>prefs page immediately editable?</summary>
    <updated-at type="datetime">2009-01-08T10:16:57+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-08-08T20:06:00+00:00</created-on>
    <description>My &quot;done&quot; page tells me &quot;You have completed 9 actions so far today,&quot; but really I've done 3 things today and 6 others yesterday afternoon. IMHO, if Tracks is going to have a &quot;so far today&quot; message (which I think is useful), it should really count by date of completion, not previous 24 hours. 

Tracks 1.041 on Camino 1.0.1</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240510</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">355</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>done today message is misleading</summary>
    <updated-at type="datetime">2008-12-25T22:01:01+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2006-08-11T22:25:32+00:00</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="boolean">false</from-support>
    <id type="integer">240512</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>wish - team (family) wide tasking</summary>
    <updated-at type="datetime">2009-01-08T10:16:57+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2006-08-11T22:36:46+00:00</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="boolean">false</from-support>
    <id type="integer">240513</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>sync offline laptop with online tracks</summary>
    <updated-at type="datetime">2009-01-08T10:16:58+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-08-14T17:15:59+00:00</created-on>
    <description>I would like to request the ability to control which next actions show on the home page on a per project basis.  GTD dogma suggests that you should review your projects and then add the single next action from that project to your context lists.  Others feel this is an inaccurate reading of GTD - you should be able to list multiple next actions.  See here:  http://www.davidco.com/forum/showthread.php?t=5541&amp;page=1&amp;pp=10

My work day involves a number of single next actions as well as a number of projects, some with many multiple next actions, some with fewer.  The projects with many next actions can clutter up my home page making it hard to use effectively.  However, I do sometimes need to list multiple next actions from a project on the home page.

Suggestion:

How about setting Tracks up so that the first next action of a project is automatically shown, but also allow additional items to be shown if necessary.  Maybe this can be tied into the deferred next actions schema (some sort if indefinitely deferred item, dependent upon the next action above it, or a check box which manually activates it).

Maybe a simpler way to do it is to require next actions that are associated with a project to be added manually by checking a check box.  This could be tied into the deferred action schema by making each action an indefinitely deferred action until a check box is checked,  when the check box is checked, then it is added to the context lists.

Or maybe this is a refinement of the hidden context schema - next actions associated with projects are hidden until unhidden using a check or some other kind of control.

Or maybe I should just do this manually myself, by associating each project's next actions with a hidden category until I want it unhidden.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240515</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">360</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Control of Multiple Next Actions in Projects</summary>
    <updated-at type="datetime">2009-01-08T10:16:58+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>bgfq4qA1Gr2QjIaaaHk9wZ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-10-19T18:19:14+00:00</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="boolean">false</from-support>
    <id type="integer">240549</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>resort on change of due date?</summary>
    <updated-at type="datetime">2009-01-16T18:04:47+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>bgfq4qA1Gr2QjIaaaHk9wZ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-11-21T18:15:59+00:00</created-on>
    <description>The context drop down is not functioning in the add next action form on the home page.  If I enter the first letter of the context, auto complete does work.  If I delete the text I type, leaving the text box empty, the drop down will function.
~
Changed type to enhancement -Luke</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240561</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">405</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>Context drop-down not working.</summary>
    <updated-at type="datetime">2009-01-16T18:04:48+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>bgfq4qA1Gr2QjIaaaHk9wZ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2007-02-04T17:51:51+00:00</created-on>
    <description>The Ajax spinner at the top doesn't work very well and is not very telling with regard to *what* is happening.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240589</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">433</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>Better Ajax UI cues</summary>
    <updated-at type="datetime">2009-01-16T18:04:48+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2007-02-23T10:47:07+00:00</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="boolean">false</from-support>
    <id type="integer">240608</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Enable synchronization with mobile devices/other systems</summary>
    <updated-at type="datetime">2009-01-08T10:16:59+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2007-03-25T16:57:39+00:00</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="boolean">false</from-support>
    <id type="integer">240635</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Enhancements to Notes section</summary>
    <updated-at type="datetime">2008-12-25T22:13:17+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2007-04-18T14:31:00+00:00</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="boolean">false</from-support>
    <id type="integer">240660</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Notes with history</summary>
    <updated-at type="datetime">2009-01-08T10:19:14+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2007-04-18T14:40:52+00:00</created-on>
    <description>I run a lot of projects on Tracks. It would be really good to be able to see the completed actions over the last week in each project. Instant activity report.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240661</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">504</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>Sort completed actions by project to create an activity or status report by project</summary>
    <updated-at type="datetime">2009-01-08T10:20:24+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2007-04-23T01:52:51+00:00</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="boolean">false</from-support>
    <id type="integer">240664</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>bookmarklet to create action including &quot;link:&quot;current url</summary>
    <updated-at type="datetime">2008-12-25T22:15:47+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2007-06-13T14:11:26+00:00</created-on>
    <description>I would like to see a limited number of NAs for a given project in my home and context view. I currently accomplish this by only ever having 1 NA on the project NA list and the others as a project note. Then as I finish one I move one off of the note and put it in the proper context.

A more elegant solution would be to allow you to list as many NAs on a project page as you wish but only ever queue up one per context.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240683</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">526</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>Queue Next Actions on Project page</summary>
    <updated-at type="datetime">2008-12-25T22:17:07+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2007-08-09T02:41:11+00:00</created-on>
    <description>I've noticed a couple of things with respect to the autocomplete functionality for contexts on the projects page
1) It would appear that the database is hit each time to generate the contexts list for the autocompleter for each project ( i could be reading the logs wrong...)
2) When creating a new project in a new context, that new context should be available in all autocompleters on that page w/o a refresh occurring

1 can be addressed completely server side by putting the contexts list in an instance var (if this is in fact a problem.

I've found that adding elements to the array the autocompleter was instantiated with do in fact appear in the list, so it is possible to put the contexts in a var like so:
var contexts= &lt;%= context_names_for_autocomplete %&gt;
defaultContextAutoCompleter = new Autocompleter.Local('project[default_context_name]', 'default_context_list', contexts, {choices:100,autoSelect:false});

then later, in the rjs for project add, if there's a new context created, do contexts.push(newContextName)

The page could share one contexts var for all the autocomplete instances - saves on page size a bit too.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240702</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">545</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>share context list and project lists across whole page - new projects/contexts should show up in autocomplete w/o refresh</summary>
    <updated-at type="datetime">2008-12-25T22:19:07+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2007-09-25T23:06:06+00:00</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="boolean">false</from-support>
    <id type="integer">240721</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Some requested features inspired by My Life Organized</summary>
    <updated-at type="datetime">2008-12-25T22:20:48+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2007-09-26T05:13:14+00:00</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="boolean">false</from-support>
    <id type="integer">240722</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <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">2008-12-25T22:20:50+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2007-09-26T22:43:45+00:00</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="boolean">false</from-support>
    <id type="integer">240725</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <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">2008-12-25T22:21:24+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2007-09-27T04:53:38+00:00</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="boolean">false</from-support>
    <id type="integer">240726</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <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">2008-12-25T22:21:26+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2007-09-27T05:42:41+00:00</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="boolean">false</from-support>
    <id type="integer">240728</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Add Tooltip to Tags textbox on Next Action form?</summary>
    <updated-at type="datetime">2008-12-25T22:21:33+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2007-09-27T05:48:07+00:00</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="boolean">false</from-support>
    <id type="integer">240729</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Add inpage anchor named links to projects/actions page?</summary>
    <updated-at type="datetime">2008-12-25T22:21:35+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-01-06T23:13:11+00:00</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="boolean">false</from-support>
    <id type="integer">240782</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Delete Project Notes directly on Project Page</summary>
    <updated-at type="datetime">2008-12-25T22:27:24+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-01-12T21:49:28+00:00</created-on>
    <description>Let's also emit JSON format for project/context/todo lists and individual items. </description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240786</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Enhance REST api with JSON support</summary>
    <updated-at type="datetime">2009-01-16T18:04:51+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>bgfq4qA1Gr2QjIaaaHk9wZ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-01-24T16:39:45+00:00</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="boolean">false</from-support>
    <id type="integer">240793</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>indication that an action has just 'come from' the tickler</summary>
    <updated-at type="datetime">2009-01-16T18:04:51+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-03-12T20:48:52+00:00</created-on>
    <description>When editing an existing task, it is difficult to move/add it to a hidden project because the auto-complete list does not contain the name. (Adding a new task to a hidden/complete project is easiest to do from the project's page.)

It is possible to type out the exact name of the old project, but making any spelling errors will cause a new project to be created. Of course, &quot;hiding&quot; these hidden/completed projects is the point of the feature, but I think there are some ways to still help the user here.

I propose that when matching what the user types to the project list, Tracks could fall back to the hidden project list and then the completed project list when it can't find any matches at each level.

For example, take the following projects (no spaces to show simplest case):
 * active: Proj1, Proj2
 * hidden: Project123
 * complete: someoldproject, someone

I select the text of the current project field (could be None) and start typing &quot;Proj&quot;, I would get Proj1 and Proj2. If I type &quot;Proje&quot;, it would fall through to search hidden and show me Project123. If I type &quot;some&quot;, it would fall through active and hidden and search the complete list and show me someoldproject and someone.

In this way, a user could type enough identifying information that Tracks could help find the right project and populate the field.

The only case where they would *never* see the auto-complete list containing their project's name would be if their project name only differed from an active project by the last letter. In that case, the existing matching project will at least help them type the majority of the string correctly (or they can select it and edit).
</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240818</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">661</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>it is difficult to move an existing task to a hidden or complete project</summary>
    <updated-at type="datetime">2008-12-25T22:31:23+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-03-13T20:47:08+00:00</created-on>
    <description>If i want to change the context of an action i have to always open the action. 

I suggest to add an icon in right to the star. If i click on it, the context contextmenu appears where i can select another context.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240824</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">667</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>quick change context in lists</summary>
    <updated-at type="datetime">2008-12-25T22:32:04+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-03-13T21:00:06+00:00</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="boolean">false</from-support>
    <id type="integer">240825</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <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">2008-12-25T22:32:06+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-03-31T09:20:57+00:00</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="boolean">false</from-support>
    <id type="integer">240839</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Encryption?</summary>
    <updated-at type="datetime">2008-12-25T22:33:12+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-04-01T07:25:37+00:00</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="boolean">false</from-support>
    <id type="integer">240844</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Add due dates for projects</summary>
    <updated-at type="datetime">2008-12-25T22:33:37+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2008-04-11T00:33:42+00:00</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="boolean">false</from-support>
    <id type="integer">240851</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Suggestions on implementation of sortable Next Actions</summary>
    <updated-at type="datetime">2008-12-25T22:34:07+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2008-05-23T06:58:09+00:00</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="boolean">false</from-support>
    <id type="integer">240874</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Dropdown textarea for Search</summary>
    <updated-at type="datetime">2008-12-25T22:36:28+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-06-05T12:05:10+00:00</created-on>
    <description>Safari has little nice handle to expand textareas but there is no such thing in Firefox/IE &amp; others. Sometimes I put longer notes/descriptions to projects/contexts and it would be convenient to have such feature (actually I've installed Safari only for that reason). It could be a dropdown where you can change number of visible lines like in trac wiki?</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240887</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">728</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>textareas should be expandable</summary>
    <updated-at type="datetime">2008-12-25T22:38:29+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-06-24T22:21:03+00:00</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="boolean">false</from-support>
    <id type="integer">240900</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Feature Request</summary>
    <updated-at type="datetime">2008-12-25T22:40:29+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>bgfq4qA1Gr2QjIaaaHk9wZ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-06-25T19:29:12+00:00</created-on>
    <description>this error could have been spotted in the rails upgrade if there was a test for it. Don't know if this is easy with rspec?</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240902</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">743</number>
    <priority type="integer">3</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>there should be a test for #742</summary>
    <updated-at type="datetime">2009-01-16T18:04:52+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-08-22T08:59:56+00:00</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="boolean">false</from-support>
    <id type="integer">240918</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Staleness options</summary>
    <updated-at type="datetime">2008-12-25T22:42:22+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-09-20T16:03:59+00:00</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="boolean">false</from-support>
    <id type="integer">240932</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Edit multiple tasks</summary>
    <updated-at type="datetime">2008-12-25T22:43:48+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-10-15T22:00:40+00:00</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="boolean">false</from-support>
    <id type="integer">240941</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>WYSIWYG Notes &amp; Action Editor</summary>
    <updated-at type="datetime">2008-12-25T22:44:51+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-10-15T22:07:23+00:00</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="boolean">false</from-support>
    <id type="integer">240942</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Notes &amp; Notebooks</summary>
    <updated-at type="datetime">2008-12-25T22:44:53+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-01-16T01:41:56+00:00</created-on>
    <description>it would be great if you could select multiple tags in order to filter more than with just one

Ex:
http://localhost:3000/todos/tag/something+other

would show actions with tag _something_ AND _other_</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">255825</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">827</number>
    <priority type="integer">3</priority>
    <reporter-id>bFW1SO424r3yAkab7jnrAJ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>multiple tag selecting</summary>
    <updated-at type="datetime">2009-01-16T08:20:52+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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">tags</CustomField>
      <CustomField type="List" name="Version" id="3084">git-devel</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-01-17T09:04:50+00:00</created-on>
    <description>Patch
http://github.com/vitaliel/tracks/tree/feb3a44191721acfc29c9bb3085b467f51aa49db

It will makes todo list to look prettier.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">256595</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>[Patch] Convert first letter to upper case for todos.description</summary>
    <updated-at type="datetime">2009-01-19T20:54:32+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-02-12T15:16:02+00:00</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="boolean">false</from-support>
    <id type="integer">279828</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <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">2009-02-18T08:40:33+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2009-02-18T15:37:31+00:00</created-on>
    <description>The transparent fixed topbar can really hammer Firefox performance because it finds transparency complicated - I was wondering if there could be a user preference to disable this behaviour. I know it's all stylesheet stuff but it would be good to be able to enable/disable something like that per-user. Not everyone is going to want to use the transparent topbar anyway - it's a matter of preference. </description>
    <from-support type="boolean">false</from-support>
    <id type="integer">284614</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">842</number>
    <priority type="integer">3</priority>
    <reporter-id>aNNyMc-fWr3AsQeJe5afGb</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Option to disable the fixed topbar</summary>
    <updated-at type="datetime">2009-02-18T18:55:53+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">enhancement</CustomField>
      <CustomField type="List" name="Severity" id="3081">minor</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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2009-03-06T09:45:29+00:00</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="boolean">false</from-support>
    <id type="integer">298542</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>viewing notes from project view</summary>
    <updated-at type="datetime">2009-03-10T13:38:29+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-03-10T21:39:31+00:00</created-on>
    <description>Is there any chanse of having an API for tickler ?

Many thanks!</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">301916</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">857</number>
    <priority type="integer">3</priority>
    <reporter-id>bRCet2dBOr3Rv3eJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>API for ticker</summary>
    <updated-at type="datetime">2009-03-10T21:59:01+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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">api</CustomField>
      <CustomField type="List" name="Version" id="3084"></CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-03-10T21:42:48+00:00</created-on>
    <description>Can you please also include the completed and defered tasks for a project API

Many thanks
Adi</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">301918</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">858</number>
    <priority type="integer">3</priority>
    <reporter-id>bRCet2dBOr3Rv3eJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Show completed/defered tasks in /projects/ID.xml API</summary>
    <updated-at type="datetime">2009-03-10T21:59:33+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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">API, project</CustomField>
      <CustomField type="List" name="Version" id="3084"></CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2009-03-15T11:41:00+00:00</created-on>
    <description>when autocompletion dropdown appears and I try to navigate on it by using up/down arrow keys unexpectedly whole page moves up/down by the height of whole page so that selected entry is on the very top/bottom edge of the page </description>
    <from-support type="boolean">false</from-support>
    <id type="integer">305691</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">861</number>
    <priority type="integer">3</priority>
    <reporter-id>dcBQMyccir3ORbeJe5aVNr</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>using arrows on autocomplete ajax list moves whole page up/down  </summary>
    <updated-at type="datetime">2009-03-21T07:39:33+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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.7</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2009-03-28T14:55:22+00:00</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="boolean">false</from-support>
    <id type="integer">319287</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <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">2009-03-30T13:50:57+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-04-19T13:10:26+00:00</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="boolean">false</from-support>
    <id type="integer">340660</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>creating new action on any page?</summary>
    <updated-at type="datetime">2009-04-20T07:39:30+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2009-04-29T18:01:37+00:00</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="boolean">false</from-support>
    <id type="integer">352813</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Integration of SIMILE: Timeline</summary>
    <updated-at type="datetime">2009-05-12T19:04:04+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">enhancement</CustomField>
      <CustomField type="Text" name="Keywords" id="3083">timeline</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-06-16T21:05:09+00:00</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="boolean">false</from-support>
    <id type="integer">407060</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <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">2009-06-18T08:50:58+00:00</updated-at>
    <working-hours type="float">1.0</working-hours>
    <working-hour type="float">1.0</working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2009-06-17T19:41:56+00:00</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="boolean">false</from-support>
    <id type="integer">408384</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Feature Request: Expose timestamp values in todos table</summary>
    <updated-at type="datetime">2009-06-18T08:46:20+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-06-18T18:58:29+00:00</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="boolean">false</from-support>
    <id type="integer">409689</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Add read/write iCal support</summary>
    <updated-at type="datetime">2009-06-18T19:20:09+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">enhancement</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-06-24T01:11:12+00:00</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="boolean">false</from-support>
    <id type="integer">415046</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <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">2009-08-05T17:15:18+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer" nil="true"></component-id>
    <created-on type="datetime">2009-06-24T01:18:02+00:00</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="boolean">false</from-support>
    <id type="integer">415049</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Drop-down buttons on project and context</summary>
    <updated-at type="datetime">2009-06-26T14:00:08+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">enhancement</CustomField>
      <CustomField type="List" name="Severity" id="3081">normal</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2009-07-15T01:43:52+00:00</created-on>
    <description>It would be nice to have a Star option in the create and edit task screen rather than having to enter the 'starred' tag.  I have sometimes misspelled 'starred' and subsequently missed an important task.  The Star option would also be consistent with the stars shown in the task lists.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">437869</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">928</number>
    <priority type="integer">3</priority>
    <reporter-id>cEbgCiCeGr3Q76eJe5afGb</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Have a Star option on task entry screens</summary>
    <updated-at type="datetime">2009-07-15T01:43:52+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <CustomField type="List" name="Type" id="3080">enhancement</CustomField>
      <CustomField type="List" name="Severity" id="3081">normal</CustomField>
    </CustomFields>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer" nil="true"></component-id>
    <created-on type="datetime">2009-09-12T20:58:02+00:00</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="boolean">false</from-support>
    <id type="integer">514990</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <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">2009-12-17T15:34:36+00:00</updated-at>
    <working-hours type="float">1.0</working-hours>
    <working-hour type="float">1.0</working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-09-12T21:09:22+00:00</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="boolean">false</from-support>
    <id type="integer">514993</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>task sort within context should use project order as secondary key</summary>
    <updated-at type="datetime">2009-12-17T15:35:00+00:00</updated-at>
    <working-hours type="float">0.5</working-hours>
    <working-hour type="float">0.5</working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2009-09-12T21:26:13+00:00</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="boolean">false</from-support>
    <id type="integer">514997</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>context, project and tag view/edit inconsistency</summary>
    <updated-at type="datetime">2009-09-12T21:26:13+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-09-12T21:28:05+00:00</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="boolean">false</from-support>
    <id type="integer">514999</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>should be able to drag contexts between visible/hidden</summary>
    <updated-at type="datetime">2010-01-17T19:08:55+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-09-12T21:30:24+00:00</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="boolean">false</from-support>
    <id type="integer">515001</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>projects need default due date, default 'show from'</summary>
    <updated-at type="datetime">2009-09-12T21:30:24+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2009-09-12T21:35:55+00:00</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="boolean">false</from-support>
    <id type="integer">515004</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>context sort order by session or IP or ?</summary>
    <updated-at type="datetime">2009-09-12T21:35:55+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2009-09-13T21:17:14+00:00</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="boolean">false</from-support>
    <id type="integer">515522</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>context collapse animates after page reload</summary>
    <updated-at type="datetime">2009-09-13T21:17:14+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2009-09-16T18:19:35+00:00</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="boolean">false</from-support>
    <id type="integer">520298</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <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">2009-09-16T18:19:35+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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 nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2010-01-03T09:56:44+00:00</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="boolean">false</from-support>
    <id type="integer">795317</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>RTL support</summary>
    <updated-at type="datetime">2010-01-03T09:56:44+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2005-04-02T06:15:21+00:00</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="boolean">false</from-support>
    <id type="integer">240151</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">17</number>
    <priority type="integer">4</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>integration of a wiki into Tracks</summary>
    <updated-at type="datetime">2009-01-08T10:16:48+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2005-06-25T02:33:47+00:00</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="boolean">false</from-support>
    <id type="integer">240211</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <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">2009-01-08T10:16:48+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2005-07-13T13:55:08+00:00</created-on>
    <description>If you do add recurring events to a future version, could I also request an advanced visibility period for items?  This would help prevent the summary being cluttered with low-priority items that aren't due for a long time.

e.g. For birthday items I'd generally only want them to be visible a few days head of their due date, for posting cards.  For car servicing, I'd like to see them a few weeks ahead instead to allow for booking delays.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240219</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">82</number>
    <priority type="integer">4</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>Request: configurable advanced visibility</summary>
    <updated-at type="datetime">2009-01-08T10:16:48+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2005-07-29T12:58:52+00:00</created-on>
    <description>I regularly carry out the same set of actions as part of a process. Would it be possible to allow me to create a 'template project' containing actions for each step in the process, and then create instances of that template as required?</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240229</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">92</number>
    <priority type="integer">4</priority>
    <reporter-id>czFbRE0eSr3zoYab7jnrAJ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>Project Templates</summary>
    <updated-at type="datetime">2009-01-08T10:16:49+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2005-09-29T14:35:53+00:00</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="boolean">false</from-support>
    <id type="integer">240263</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>&quot;Covey Quadrant&quot; - some brainstorming</summary>
    <updated-at type="datetime">2009-01-08T10:16:50+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2005-10-18T23:10:43+00:00</created-on>
    <description>Possibly add additional checkbox that when clicked closes action and offers a new next action with project or context preseleted.  Or you could make it a Shift or Command or Ctrl click function to close and offer the next action entry box.  </description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240284</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">143</number>
    <priority type="integer">4</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Offer next action on completion.</summary>
    <updated-at type="datetime">2008-12-25T21:39:55+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-03-28T03:06:35+00:00</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="boolean">false</from-support>
    <id type="integer">240394</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <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">2008-12-25T21:50:55+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2006-04-23T10:33:47+00:00</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="boolean">false</from-support>
    <id type="integer">240418</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Change layout for Edit Action box</summary>
    <updated-at type="datetime">2009-01-08T10:16:54+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-05-17T09:07:27+00:00</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="boolean">false</from-support>
    <id type="integer">240446</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Change context state based on IP address of client</summary>
    <updated-at type="datetime">2008-12-25T21:54:43+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-06-25T23:43:13+00:00</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="boolean">false</from-support>
    <id type="integer">240465</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Feature Request: Add category tags and views to Projects</summary>
    <updated-at type="datetime">2010-01-17T19:13:02+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
    <CustomFields>
      <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" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-09-23T09:03:17+00:00</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="boolean">false</from-support>
    <id type="integer">240538</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>completing or adding actions should update sidebar counts</summary>
    <updated-at type="datetime">2008-12-25T22:03:13+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id nil="true"></assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2006-11-08T20:43:17+00:00</created-on>
    <description>Observed some layout/display issues with both Internet Explorer 6 and 7 (release version).

Screen shot:  http://www.solo-technology.com/images/IE_Tracks.png

Might be related to some of the validation issues around the &lt;ul&gt;'s?</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240553</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">397</number>
    <priority type="integer">4</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>IE Layout issues - IE6 and IE7</summary>
    <updated-at type="datetime">2009-01-16T18:04:48+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2007-02-03T03:16:56+00:00</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="boolean">false</from-support>
    <id type="integer">240587</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Sidebar: todo and notes fields too narrow. Optional width?</summary>
    <updated-at type="datetime">2009-01-08T10:16:58+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2007-02-08T08:48:20+00:00</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="boolean">false</from-support>
    <id type="integer">240593</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Adding Notes</summary>
    <updated-at type="datetime">2008-12-25T22:08:53+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2007-02-15T09:33:28+00:00</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="boolean">false</from-support>
    <id type="integer">240596</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>'Project' field in action's edit mode should be highlighted</summary>
    <updated-at type="datetime">2009-01-08T10:16:59+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2007-03-21T10:50:20+00:00</created-on>
    <description>Actions in a project often have to be taken in some ordered fashion. Attaching dependencies would make it easy to only show the actions which are &quot;actionable&quot; at the moment and not overload lists with all the single steps which are to be taken in the future.

An action should be able to depend on another action or a project (requiring that the project be completed before). Dependencies on multiple actions/projects should be possible.</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240632</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">475</number>
    <priority type="integer">4</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>Actions should be able to depend on other actions/projects</summary>
    <updated-at type="datetime">2009-01-08T10:17:00+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2007-03-29T07:40:35+00:00</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="boolean">false</from-support>
    <id type="integer">240640</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>(context based) help</summary>
    <updated-at type="datetime">2008-12-25T22:13:39+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>bgfq4qA1Gr2QjIaaaHk9wZ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2005-08-04T16:44:36+00:00</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="boolean">false</from-support>
    <id type="integer">240231</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>TXT as YAML</summary>
    <updated-at type="datetime">2009-01-16T18:04:41+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2005-08-10T22:03:43+00:00</created-on>
    <description>If there is interest, at some stage we should consider adding &quot;Multilingual&quot;:http://www.tuxsoft.se/oss/rails/multilingual support. </description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240242</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">104</number>
    <priority type="integer">5</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">1</status>
    <story-importance type="integer">0</story-importance>
    <summary>Multilingual Tracks</summary>
    <updated-at type="datetime">2009-02-15T21:23:19+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2005-10-01T11:16:55+00:00</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="boolean">false</from-support>
    <id type="integer">240267</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>&quot;Project Notes&quot; appearance - suggestion</summary>
    <updated-at type="datetime">2008-12-25T21:38:23+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-04-17T13:01:30+00:00</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="boolean">false</from-support>
    <id type="integer">240408</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <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">2009-01-08T10:16:54+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2006-04-19T13:41:34+00:00</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="boolean">false</from-support>
    <id type="integer">240410</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Transfer next actions between users</summary>
    <updated-at type="datetime">2009-01-08T10:16:54+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2007-03-02T02:03:58+00:00</created-on>
    <description>Would be useful to see some type of indicator (text color, character, icon/image) that helps a project in the right hand column project list to stand out better if there is a project without a next action assigned to it.
</description>
    <from-support type="boolean">false</from-support>
    <id type="integer">240621</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></notification-list>
    <number type="integer">464</number>
    <priority type="integer">5</priority>
    <reporter-id>bgfq4qA1Gr2QjIaaaHk9wZ</reporter-id>
    <space-id>alWI9M0eWr3zoYab7jnrAJ</space-id>
    <status type="integer">0</status>
    <story-importance type="integer">0</story-importance>
    <summary>indicator on right hand project list of home page if project is without next action.</summary>
    <updated-at type="datetime">2009-01-08T10:17:00+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2007-06-13T16:18:34+00:00</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="boolean">false</from-support>
    <id type="integer">240684</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>Delegate actions to other users</summary>
    <updated-at type="datetime">2008-12-25T22:17:10+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">3</component-id>
    <created-on type="datetime">2008-01-05T07:10:43+00:00</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="boolean">false</from-support>
    <id type="integer">240778</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <story-importance type="integer">0</story-importance>
    <summary>too dark?</summary>
    <updated-at type="datetime">2009-02-16T11:21:45+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
  <ticket>
    <assigned-to-id>czFbRE0eSr3zoYab7jnrAJ</assigned-to-id>
    <completed-date type="datetime" nil="true"></completed-date>
    <component-id type="integer">2</component-id>
    <created-on type="datetime">2008-02-12T18:22:07+00:00</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="boolean">false</from-support>
    <id type="integer">240800</id>
    <importance type="integer">0</importance>
    <is-story type="boolean">false</is-story>
    <milestone-id type="integer">54242</milestone-id>
    <notification-list nil="true"></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>
    <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">2008-12-25T22:29:29+00:00</updated-at>
    <working-hours type="float" nil="true"></working-hours>
    <working-hour nil="true"></working-hour>
  </ticket>
</tickets>
