Get your own customer support community

About me

Location
San Francisco

Recent activity

Subscribe to this feed

  • Jonathan started following the question "it would be nice if we could put in due dates and track by date" in Pivotal Labs.

  • idea

    Jonathan replied on February 12, 2009 16:23 to the idea "A "pause" button" in Pivotal Labs:

    Jonathan
    I find that if I stop working on a story for a day or two, I un-start it. If I have done some work or gained some context that would be beneficial to whomever re-starts it, I add that information as a comment and possibly an attached diff.

    If you really wanted to track stories that have had some work done on them but were un-started for whatever reason (re-prioritization etc.), you could make a 'paused' tag and add it to those stories thus making them easier to find later.
    Do you think this is one of the best points? Mark it as a good point
  • problem

    Jonathan reported a problem in New Relic on December 17, 2008 00:31:

    Jonathan
    2.7.4 causes Error calling Dispatcher.dispatch
    We get the following stacktrace when trying to upgrade to 2.7.4. This is when trying to hit a page on the site. We did not experience this problem in 2.3.5. We are using Desert (http://rubyforge.org/projects/desert/), but it hasn't caused a problem in the past.

    Tue Dec 16 16:21:01 -0800 2008: Error calling Dispatcher.dispatch #<nameerror: />
    /Library/Ruby/Gems/1.8/gems/desert-0.3.2/lib/desert/rails/dependencies.rb:56:in `look_for_constant_in_parent_module'
    /Library/Ruby/Gems/1.8/gems/desert-0.3.2/lib/desert/rails/dependencies.rb:13:in `load_missing_constant'
    /Library/Ruby/Gems/1.8/gems/activesupport-2.1.2/lib/active_support/dependencies.rb:468:in `const_missing'
    PATH_TO_PROJECT/vendor/plugins/newrelic_rpm/lib/new_relic/agent/instrumentation/dispatcher_instrumentation.rb:41:in `dispatcher_finish'
    PATH_TO_PROJECT/vendor/plugins/newrelic_rpm/lib/new_relic/agent/instrumentation/dispatcher_instrumentation.rb:49:in `dispatch'
    /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/rails.rb:76:in `process'
    /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/rails.rb:74:in `synchronize'
    /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/rails.rb:74:in `process'
    /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:159:in `process_client'
    /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:158:in `each'
    /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:158:in `process_client'
    /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:285:in `run'
    /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:285:in `initialize'
    /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:285:in `new'
    /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:285:in `run'
    /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:268:in `initialize'
    /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:268:in `new'
    /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:268:in `run'
    /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/configurator.rb:282:in `run'
    /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/configurator.rb:281:in `each'
    /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/configurator.rb:281:in `run'
    /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:128:in `run'
    /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/command.rb:212:in `run'
    /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:281
    /usr/bin/mongrel_rails:19:in `load'
    /usr/bin/mongrel_rails:19
  • idea

    Jonathan replied on January 23, 2008 00:35 to the idea "I would like current and backlog columns merged into one" in Pivotal Labs:

    Jonathan
    I also see people trying to move a story in the backlog into the end of the current iteration but the story doesn't show up there it shows up at the top of the backlog, they then try to re-drag it and re-drag it and then end thinking it is a bug in tracker. When I tell them to consider them one column and that nothing else can fit into the iteration they are moving the story into so it gets pushed out, then everything clicks for them.
    Do you think this is one of the best points? Mark it as a good point
  • question

    Jonathan replied on January 18, 2008 17:34 to the question "How can I refine a search for stories?" in Pivotal Labs:

    Jonathan
    All this advance search help/reference material should be readily available in the search pane. Preferably in a manner that it could be seen while using search. Currently it is 2-3 clicks away and not very useful
    Do you think this answers the question? Mark it as answered
  • idea

    Jonathan shared an idea in Pivotal Labs on January 18, 2008 17:30:

    Jonathan
    I would like current and backlog columns merged into one
    there is hardly any value it considering them different things and tends to confuse clients early in the adoption phase