Pivotal Tracker for iOS 1.6.1 fixes Romaji and other text input issues: 失礼しました｡

Wednesday, March 6, 2013

We’ve just released version 1.6.1 of the Pivotal Tracker iOS app, which includes fixes for a number of text input problems.

Most importantly, it fixes Romaji input for Japanese users. While we don’t officially support non-English localizations, we try our best to allow Tracker to be used in any language. This release also fixes a similar bug that prevented auto-completion, spell-checking, and text shortcuts from working in text fields.

Dragging stories is also snappier in this release, because we’ve reduced the delay before beginning a drag. To recap, stories can be dragged to a new location by touching and holding a story for a short time with one finger. We include a momentary delay, otherwise stories would get moved while scrolling through story panels. Touching a story with two fingers will immediately begin dragging a story, which I find really convenient and useful on an iPad.

The new version can be downloaded from the App Store, and we welcome your feedback in the Pivotal Tracker community forum.

Greatly Refined Story Editing in Pivotal Tracker for iOS 1.6

Christian Niles

Wednesday, February 27, 2013

Today we’ve released Pivotal Tracker for iOS 1.6 to the App Store. With this release we’ve thoroughly refined the app to make updating stories easier and more enjoyable. While there are all kinds of refinements, we think you’ll be most excited about the following:

All text can now be edited inline

A story’s name, description, tasks, and comments are all editable inline, without transitioning to a new screen and losing context. While editing, text now wraps gracefully across multiple lines as you type.

For example, previous versions of the app provided a separate screen for creating a comment. In version 1.6 this now happens inline, right where the comment will be added. This allows you to continue to scan other comments or details about the story as you write.

Managing labels is easier

Finding and adding labels to a story is much improved, especially for larger projects. The label list now filters as you type, which helps avoid duplicate or mistyped labels. Adding a new label is also much more obvious and easy.

Moving Tasks doesn’t require a separate mode anymore

All tasks can now be moved using the standard move controls, without the need to go into “move” mode. This gets rid of a needless extra taps. To remove a task, simply swipe it and tap the “Delete” button.

Moving or Deleting a story are both more accessible

We’ve gotten rid of the separate “Action” screen, and replaced it with a pair of buttons to move or delete a story. You’ll find these at the very bottom of the story editor, rather than the old icon in the title bar.

We hope you love this release! Please don’t be shy about letting us know in our community about how we can continue to make the app better.

New in Pivotal Tracker for iOS: Search, My Work, New iPhone Interface

Dan Podsedly

Tuesday, November 15, 2011

Version 1.1 of the Pivotal Tracker for iOS app is now available in the iTunes App Store. This update adds the Search and My Work panels, a redesigned iPhone interface, and many overall usability improvements. All the details after the jump, below.

Search and My Work

You can now find and filter stories quickly with the new Search panel, which supports all of the Tracker search syntax that you’re used to. The new My Work panel shows you all of the stories that you’re currently working on, that are assigned to you, or that are waiting for your acceptance.

Add Stories Anywhere

Adding stories is easier now, just tap the new story button at the top right corner, regardless of where you are in the app (on the iPad or the iPhone).

Faster Access to Story Panels

Switching between panels on the iPhone is now much faster with the new tab bar at the bottom. It even works while dragging a story – tap the desired target panel with the other finger.

Similarly, the iPad version now has a row of panel buttons at the top right, tap them to reveal a given panel quickly or just swipe the panels side to side as before.

Story States on iPhone

Story states are now displayed for in-progress stories on the iPhone, and easily changed by swiping a story to the left.

Other Improvements

Drag and drop and scrolling has been significantly improved, particularly on older iPhone and iPod Touch models. We’ve also updated the app for iOS 5, and added many detailed interface tweaks to make stories easier to find and work with.

Feedback

We’re committed to bringing the best of Pivotal Tracker to the your iPhone and iPad, while taking full advantage of all the user experience and portability features of the iOS platform. Many more improvements are on the way, but we’d love to know what you think so far! Give us a shout at tracker@pivotallabs.com.

By the way, we’re thrilled to see all the positive reviews in iTunes. Thanks everyone, and keep them coming!

Standup 4/28/2010: Webrat threading errors & new RubyMine version

David Stevenson

Wednesday, April 28, 2010

Ask for Help

“We keep getting webrat thread exceptions running our integration specs with the rails integration runner: Thread tried to join itself. The error message varies with different versions of ruby 1.8.6 vs 1.8.7.”

Anyone had this problem or know why?

“How do I skin an iphone mobile site to be the correct width so it’s not 980px wide?”

<meta name="viewport" content="width = device width" />

*”We’re trying to deploy some nginx configuration changes to EngineYard Cloud, what’s the right way to do that?”

We’ve tried building custom chef recipes to solve this problem, but they run after nginx has already restarted, so are a poor solution to this problem. The better solution might be to check in configuration files into the application and symlink them into the nginx configuration directory using a before_symlink.rb hook in the /deploy directory.

*”We’ve got a has_many association where some of the child records are originally saved in an invalid state. When we later load the parent and ask it if it’s valid, it returns true even with validates_associated. How can we get the desired validation behavior?”

Turns out that unloaded associations are not validated. Solution: load the association before calling .valid? on the parent. In general, you should also not create invalid objects, instead using a state variable to put them into a “draft” or “incomplete” state where they are still valid but not complete. Then remove that state and you’ll see the errors required to finish that object.

Interesting Things

When RubyMine 2.0.1 won’t run your focused specs, try attaching rspec 1.2.9 to it rather than 1.3.x. It fixed this issue for one of our teams.
Rubymine 2.0.2 came out today: can finally run focused contexts?! Also including bundler support! What’s new
We tried our Unicorn on EngineYard cloud: so far so good. It’s still “experimental” but seems to work.

Standup 08/24/2009: How do you redefine css classes in javascript?

David Stevenson

Monday, August 24, 2009

Ask for Help

“How do I redefine a CSS class in javascript”

You can create a new <style> element and append it to the head. This should probably be avoided if you can help it.

If you simply want to toggle between 2 states, consider putting both sets of rules in the CSS and toggling a class on the body or other container.

*”Should I use BOSH for XMPP on the iPhone?”

Probably not. If you have a long-running low latency XMPP connection, you’ll probably want to use a socket from the CFNetwork package. That’s the most we know about iPhone development right now.

Interesting Things

New tracker updates with better burndown charting!

iPhone Interface for Pivotal Tracker

David Stevenson

Thursday, March 19, 2009

I’ve been wanting to use Pivotal Tracker on my iPhone, so I wrote a little proof of concept using the Tracker API. I thought that a native application would be much more difficult than a skinned web application using ActiveResource.

I tried out Dashcode, Apple’s recommended iPhone-compatible front-end web development tool, but was disappointed. I basically found myself developing the entire application in javascript, actually using XMLHttpRequest to talk directly to the API. This would have been pretty neat if I could have pulled it off, but I’d rather develop a data-heavy application in rails than javascript.

I ended up using simple CSS to skin the application called UiUI. It’s the best looking iphone UI I’ve seen, with tons of elements to choose from. It’s missing effects, of course, being only CSS. I also used Heroku, a free and scalable rails deployment environment to host my application. With it, I was up and running with a functional tracker application in under 3 hours. Since then, I’ve added the ability to create and update stories.

Check it out, let me know what you think:
http://itracker.heroku.com

If you’re not on an iPhone, be sure to use Safari. It doesn’t look great in Firefox or IE.

Standup 11/14/2008: XXL Mongrels and Non-Model Reports

Pivotal Labs

Saturday, November 15, 2008

Interesting Things

The iPhone SDK version 2.2 was released.
An interesting Selenium Object Pattern was discussed.

Ask for Help

“How big should a typical mongrel be? Ours is starting out at over 200 megs but is not leaking from that point.”

Everyone agreed that 50MB to 70MB is standard and anything over 100MB is considered pretty big. People suggested RubyProf for inspecting object counts and possibly tracking down the memory hogging code.

“What pattern does everyone use for non-model Reports with ActiveRecord? We are trying to create a report that counts a single model and groups by two associated models”

There was consensus around modeling a distinct report object and calling the referenced models. For example, FooReport and FooReportController fit nicely in a RESTful Rails world.

iPhone-Optimized Webapp

Alex Chaffee

Thursday, December 13, 2007

iPhone on Rails – Creating an iPhone optimised version of your Rails site using iUI and Rails 22