Mark's dashboard

Mark replied on October 10, 2008 18:25 to the problem "I cant accept some stories" in Pivotal Labs:

What stories in particular? Parker only mentioned one story in his email.

Mark

Mark replied on October 09, 2008 02:48 to the question "Moving multiple stories to "top of backlog" moves the stories to top of Current in FF3.03" in Pivotal Labs:

Hi Heidi,

The problem should now be fixed. When stories are moved from the icebox to the top of the backlog they are moved after the last story in the current iteration. In some cases if the story is bug or chore (assuming you are not estimating bugs and chores) or if the current iteration has room the story(s) will end up at the bottom of the current panel.

Mark replied on October 09, 2008 02:24 to the question "How can I use curl/ruby to retrieve exported csv file?" in Pivotal Labs:

Our current plan is to use a token based authentication approach. Each user will be able to generate a token that will be passed along as the basic auth user during api requests. More to come on this in the future.

A comment on the question "How can I use curl/ruby to retrieve exported csv file?" in Pivotal Labs:

Perfect.

I will assume that you have an equally good solution for authenticating my request. That was the one thing that prevented me from using the CSV export you already have. – Ward Cunningham, on October 08, 2008 16:49

Mark replied on October 08, 2008 15:39 to the question "How can I use curl/ruby to retrieve exported csv file?" in Pivotal Labs:

The name is the story title that is displayed as part of the unexpanded view of a story. The description is the text placed in the "Description" section of an expanded story.

The example story I used just happened to not have any notes. Notes will show up under the story element like this:
<story>
....
<notes>
<note>
<text>a note</text>
<author>Mark Test</author>
<date>Oct 28, 2008</date>
</note>
</notes>
</story>

Mark

Mark replied on October 08, 2008 15:29 to the question "Moving multiple stories to "top of backlog" moves the stories to top of Current in FF3.03" in Pivotal Labs:

I think we can recreate it ourselves, I added bug that we should have fixed soon.

Thanks for reporting the issue,
Mark

Mark marked one of Heidi's replies in Pivotal Labs as useful. Heidi replied to the question "Moving multiple stories to "top of backlog" moves the stories to top of Current in FF3.03".

A comment on the question "How can I use curl/ruby to retrieve exported csv file?" in Pivotal Labs:

Mark -- This is very close to what my ruby code produces from the existing csv. Some questions: What is name? Why is description empty? What happened to the notes? – Ward Cunningham, on October 08, 2008 06:11

Heidi replied on October 07, 2008 22:15 to the question "Moving multiple stories to "top of backlog" moves the stories to top of Current in FF3.03" in Pivotal Labs:

Hi Mark- current is filled up with stories matching our velocity. If you want to contact me via email I can show you via screensharing.

Mark replied on October 07, 2008 22:07 to the question "Moving multiple stories to "top of backlog" moves the stories to top of Current in FF3.03" in Pivotal Labs:

Were there any stories in current before moving the stories? A story(s) moved to the top of backlog should be moved to the bottom of current if the current iteration has room for them.

Mark

Mark replied on October 07, 2008 15:09 to the question "How can I use curl/ruby to retrieve exported csv file?" in Pivotal Labs:

Once we are ready, we can definitely give early access to our staging environment. Below is an example or our current XML format for story retrieval

<response>
<stories>
<story>
<id type="integer">2914</id>
<story_type>feature</story_type>
<url>http://demo.pivotaltracker.com/story/...</url>
<estimate type="integer">2</estimate>
<current_state>accepted</current_state>
<description></description>
<name>Any user can initiate a Search by product name, color, product type, size, size variant, and style ID </name>
<requested_by>Michael Test</requested_by>
<owned_by>Steve Test</owned_by>
<created_at>Oct 17, 2006</created_at>
<accepted_at>Oct 2, 2006</accepted_at>
</story>
</stories>
</response>

Mark replied on October 06, 2008 18:21 to the question "Tracker down?" in Pivotal Labs:

Tracker is back up now, let us know if you have any issues.

Peter Brown replied on October 06, 2008 18:18 to the question "Tracker down?" in Pivotal Labs:

It's like I've lost part of my mind

Mark replied on October 06, 2008 18:13 to the question "Tracker down?" in Pivotal Labs:

Yes Tracker is down it was a Database issue on Engine Yard and we're working with them to resolve the issue.

A comment on the question "How can I use curl/ruby to retrieve exported csv file?" in Pivotal Labs:

Well, xml is ok so long as I can read it without heroics. I'm programming in Quartz Composer (good for visualizations) and its XML support is modest. If you can give me early access, I will give my tools a test and even share the visualization that results.

Details: Composer abstracts XML into a black box that takes a url in and answers a structure out. A composer structure is like a ruby hash of hashes. The problem is that this built-in translation is lossy. If you use every XML capability I will probably have to write an XML simplifier as a separate process, complicating the install beyond my energy for other than my own use.

I'm using a separate process to translate CSV to XML now. Here is the ruby that does the translation:

require 'csv'


reader = CSV.open('tracker.csv', 'r')

keys = reader.shift.collect {|key| key.gsub(/ /, '_').downcase}


puts '<file>'

reader.each do |row|

  i = 0

  puts '  <row>'

  row.each do |value|

    key = keys[i]

    i += 1

    puts "    <#{key}>#{value}</#{key}>" if value && value != ''

  end

  puts '  </row>'

end

puts '</file>'

– Ward Cunningham, on October 06, 2008 16:08

Mark replied on October 06, 2008 14:23 to the question "How can I use curl/ruby to retrieve exported csv file?" in Pivotal Labs:

We currently do not have a way to programatically retrieve data from Tracker. We are working on XML/JSON Tracker API that will enable users to programatically interact/retrieve data from Tracker. The new API should be deployed in the next few weeks.

Would want the new API to include a csv export option as well?

Mark

A comment on the idea "Clearer visual distinction of your tasks in Current view" in Pivotal Labs:

I believe Mark meant to say the initials next to a story that you own. – Joseph, on October 03, 2008 21:01

A comment on the idea "Clearer visual distinction of your tasks in Current view" in Pivotal Labs:

Thanks for your response, Mark. The thing about the My Work view, aside from being kind of redundant, is that it still shows items waiting for someone else's approval, and, more than anything, that it shows up way over on the right-hand side of the screen on the opposite side of the backlog (between Done and Current would make more sense to me -- or, ideally, being able to drag them around freely).

I'm not clear on what you mean by #2 above, though, so maybe I'm missing something. Clicking on a story doesn't seem to do anything for me. – chrisw, on October 03, 2008 20:23

Mark replied on October 03, 2008 15:55 to the idea "Clearer visual distinction of your tasks in Current view" in Pivotal Labs:

We'll look into what we can do. There are currently several ways to view your work.
1. Open my work view as you mentioned
2. Click on one of the stories that you one which will perform a mywork search
3. Type in mywork:<initials> in the new search field on the top right side of the browser.

Mark</initials>

danp replied on October 02, 2008 23:34 to the idea "Consider making the new design slightly narrower" in Pivotal Labs:

Thanks, we're working on fixing this.