Urban Turtle's blog

Once again, Team Urban Turtle is quite proud to announce the release of Urban Turtle 3.14. Featuring updated visuals and the ability to fill a backlog or decompose a product backlog item in seconds, we’re pretty sure you’ll be as excited as we are about this new version.

New Design
While strictly an aesthetic update, the new planning and task board design in Urban Turtle 3.14 was also aimed at improving the visibility of the boards when displayed using a projector. The original design, albeit attractive on paper, turned the Turtle into a Christmas tree (actual user comments!) when used in the real world. Even though it has always been a concern for us, we chose to concentrate on developing new features since the 3.0 release. This update was long overdue, and this is why we tasked our web guy, Guillaume, to come up with a new look for the application. We’re very happy with the results and we hope you will be too! We can’t wait to hear what you think about it. It may be disconcerting at first, as with any major change, but given time, we’re convinced you’ll find the new look to be quite easier on the eyes. Can’t go wrong with less eye bleeding, right?

Quick Add
We know for a fact that our users tend to avoid round-trips to the Work Item Editor window in Team Web Access like the plague. And with good reasons! It is painfully slow to render and it forces a planning or task board refresh when closed. This is why we try to come up with features that avoid having to go through this window.

Urban Turtle 3.14 introduces the Quick Add section which aims to make the user story/product backlog item decomposition part of your Sprint Planning meetings an actual joy to do. It allows you to add tasks to a PBI in a matter of seconds, without ever going through the Work Item Editor. Simply type in the work item title, press enter and a new work item appears immediately. What’s really cool about this is that you don’t need to wait for the work item to actually be created in TFS. The creation part is all done asynchronously, so you can just continue to type in work item titles and press enter. Combined with the in-place editing capabilities, creating tasks and setting the work remaining is no longer the chore it used to be.

Quick Add Section

After breaking tradition and our monthly release cycle, Team Urban Turtle is proud to present to you version 3.13 featuring the most requested idea ever!

New Features

• Our planning board has always been agile, but we had it learn some new tricks to make it more flexible than ever. With most process templates, it is now possible to simply drag a work item and drop it anywhere you want. Urban Turtle will take care of figuring the updates required such as removing the current work item link between the item and its parent, creating a new one and prioritizing the work item within its new siblings.
• The iteration panel can now be collapsed, leaving more space for the work items. This was accomplished by inserting the iteration panel inside of the default Team Web Access side-panel. As this is where Team Web Access displays its search bar, users also gain access to search capabilities at the same time.
• With Urban Turtle 3.9, we introduced independent iteration and area settings for the planning and task boards. This change didn’t please everyone, so we decided to turn this itself into a setting. On the iteration and area panel, a pushpin icon has been added. When the pushpin is colored, it is active, forcing iteration and area settings to be retained across both boards. Otherwise, settings are independent.

Improvements

• A few usability improvements have been made to the planning board. Now that the iteration panel can now be hidden, it was obvious we needed to expand work item titles to fill the space. This automatic expanding and truncating of the work time titles is also done when resizing the window. This means that the larger screen resolution that you use, the more you will be able to see of the work item titles.
• A little known feature that has always been present on the planning board is the ability to select multiple work items to drag and drop them on an iteration, an area or the recycle bin. We’ve decided to improve this and highlight this functionality by adding checkboxes on work items. This makes it a lot more obvious that this feature exists. Please note that multi-selection does not apply when reordering work items.We’ve also ported the ability to collapse parent work items from the task board to the planning board.

Fixed Issues

• Users of the french version of the MSF Agile 5.0 process template will be glad to know that we have resolved the issue that prevented adding some child work items. The problem was due to accents in the work item types (such as Tâche).
• We have also fixed an issue preventing moving a work item after the last visible work item on the planning board.

We know that it’s been a long time coming (the ability to change work item links using drag and drop has been requested over a year ago!) and we invite you to download the latest version. Your feedback has always been invaluable to us and we’re very excited to hear what you have to say about this new release. While we already have ideas in mind for the next release, your feedback may still steer our decisions. Don’t hesitate, and voice your opinion on our community support site!

Team Urban Turtle is proud to announce the release of Urban Turtle 3.12. During the last month, we’ve focused on further improving support for the Scrum for Team System v3 process template, as well as adding a few template-agnostic goodies for everyone.

Scrum for Team System v3
Implementing support Scrum for Team System (hereafter SfTS for brevity) proves to be an interesting challenge for us. As we strive to protect our template independence, there are many particularities with this template that force us to jump through hoops in order to provide a compelling solution for SfTS users. We’ve introduced the Direct Links query mode in Urban Turtle xx, to support the various link types found in SfTS. We have also added the ability to configure a Sprint work item type per iteration level, to support the Release, Sprint and Team Sprint work item types. Now, we are adding the ability to automatically link these work item types together via the Implemented-By link type, as prescribed by the SfTS guidance.

The default configuration file for SfTS specifies the relationship between the different link types. In Urban Turtle, when you add a Sprint work item to an iteration, it automatically looks up the chain of iterations to find the Sprint work item it should link to. This is all done automatically, behind the scenes, but it requires you to create the Sprint work items in the expected order. This means that you should first create a Release, then a Sprint, and finally, a Team Sprint. Doing so will automatically link the Sprint to the Release, and the Team Sprint to the Sprint, enabling all the cool roll-up features and calculated fields found in Scrum for Team System. To make things a bit easier, iterations without a Sprint work item can now be quickly spotted just by looking at the iteration panel.

We’ve also added the last missing piece in the SfTS feature tracking work item model: the Acceptance Test. This work item type links Bugs to Product Backlog Items but it was missing from the default SfTS configuration file that ships with Urban Turtle. This means that you can now have Product Backlog Items tested by Acceptance Tests failed by Bugs as suggested in the process guidance.

We believe this extended linking support will be more than welcome by current users of the Scrum for Team System process template as they make Urban Turtle a compelling alternative solution to the TFS Workbench from EMC Consulting.

And the goodies!
Most of our current customers rely on the common process templates from Microsoft: MSF Agile 5.0 and Visual Studio Scrum 1.0. If you’re using one of these templates, you can still benefit from the features added specifically for Scrum for Team System, as every new functionality is implemented in a template-independent way. For instance, you can switch to the Direct Links query mode to add support for custom link types. You can configure the relationship between the different work item types to prevent users from adding User Stories to Tasks. Any feature that is unavailable with the default configuration file can be added by modifying your process template and creating your own custom configuration mapping file. But Urban Turtle 3.12 also introduces a few features that work with any process template and do not require any tinkering with the configuration files.

• Ordering of new child items
  With prior versions of Urban Turtle, new child items always appeared on top, with a seemingly higher priority. This doesn’t make much sense for a lot of users as most people tend to create tasks in the order they believe they should be completed. Urban Turtle 3.12 now sets a default backlog priority or stack rank for new child work items at a value higher than the last visible item.
• Improved Pagination
  Experienced Urban Turtle users know that the options in the Cards per Stack menu on the planning board refer to the number of parent or root work items and not to the number of visible work items. This means that you could choose to display 25 Cards per Stack but actually see a lot more work items because all the descendants of each of the visible parent work items would also be displayed. This could severely impact loading times when accessing either board. Furthermore, there was no Cards per Stack option for the task board, as it doesn’t use the stack metaphor.

  In Urban Turtle 3.12, we have decided to change the pagination logic by applying the Cards per Stack selection to visible work items. One caveat to be aware of is that you will always see all descendants of a parent work item no matter how many there are. However, as soon as we hit the chosen Cards per Stack limit, the next parent is pushed to the next stack. This means that it will still be possible to view more than the selected number of work items, but the count should never get unreasonably high.

  We have also ported the same pagination logic to the task board, including the Cards per Stack menu (renamed Cards per Page on the task board). This should also help improve load times as the pagination applies to all displayed work items unlike previous versions which had separate logics for the parent and the Other Work Items sections.

As usual, we recommend that everyone upgrades to the latest version. We are looking forward to your feedback! Please visit our community support-site to ask questions, propose ideas or report issues. It is monitored very closely by the team and you will get timely replies to any inquiry.

Over a year ago, we released Urban Turtle 3.0, the premier Scrum tool for Team Foundation Server 2010. To be honest, it was a bold move. Four months before the release, what we had was a product that almost nobody knew about, compatible only with TFS 2008. We threw half of the code away, went through a complete UI overhaul and developed against beta releases of TFS 2010, aiming to be ready for the big Visual Studio 2010 launch in April. Strong believers in Agile software development practices, we fully embraced the release early, release often pattern and sim-shipped Urban Turtle 3.0 alongside TFS2010. Over the year that followed, we managed to release 12 updates, one each month. Today marks the day of our 12th release: Urban Turtle 3.11. As always, it includes a few new features, several tweaks and improvements as well as a few bug fixes. Read on to find out what’s new!

Print support
Many people have been requesting for some time now that we add printing support to Urban Turtle. As per the Manifesto for Agile Software Development, people highly value individuals and interactions over processes and tools. They wanted to be able to print work items in an index card format for use on an actual task board instead of a virtual one. This is exactly what we are introducing in Urban Turtle 3.11. You now have the option to export work items to a PDF file. We’re starting with basic support, but we do hope you will give us feedback to help us improve this feature over the next releases. Click here for a sample of the PDF output.

Filters on the task board
We have decided to port the planning board filtering options over to the task board following a customer request. You now have the ability to hide work items from child iterations, to hide items that are done and to filter work items according to their work item type. These settings are independent from the planning board, meaning that you can hide done items on the planning board but have them show up on the task board.

Business value on the planning board
Until now, the planning board view was restricted to two customizable fields. Since one of the fields represented the work item title, there was effectively only one field to customize unless you knew your work item Ids inside-out. Customers have requested the ability to view both the Effort and Business Value fields at the same time, for obvious reasons. We therefore managed to squeeze in a third configurable field and the default Scrum 1.0 mapping file has been updated to display the Business Value for Product Backlog Items.

Single Column Headers
Another highly requested feature or improvement regarded the duplicate column headers on the task board. We used to display the headers for every root (or parent) work item, usually the Product Backlog Items. This took up a lot of space and was considered a waste by just about everyone using the product. This has been replaced by fixed column headers which are always visible but displayed only once, saving up precious screen real estate.

Configurable Blocked State
The Task work item type definition in the Scrum 1.0 process template specifies a Blocked field which we added support for the previous release. We used to consider any value as meaning that the item was blocked, but it has come to our attention that this can prove problematic with other process templates. While this option is still available, you can now also configure a value to represent the Blocked state. We have updated the Scrum 1.0 mapping file to consider tasks as blocked when the value for the Blocked field is yes. As with many things in Urban Turtle, this is fully configurable and can be adapted to your own custom process template by editing your project’s mapping file.

There are several other improvements and bug fixes included in this release. I invite you to review the release notes for more information. This release has been driven by your feedback, and we would like to thank you for taking the time to propose ideas, ask questions, report issues and praise us on our community support site. Your help has become an invaluable asset to our development team! As always, we recommend that you download and upgrade to the latest version. We are pretty sure that it has something to like for everyone!

Almost a whole year has gone by since the release of Team Foundation Server 2010 and our add-in for its Team Web Access application tier, Urban Turtle 3. Since then, we have managed to release a new version each month, for a total of eleven. Some say it’s too much, others say it’s impressive, but the team thinks nothing of it. We’re just working hard, trying to improve our product release after release. Frequent releases is merely a side effect!

Scrum for Team System
This month, we bring you two outstanding features along with the ubiquitous bug fixes. First on the list is further improved support for Scrum for Team System v3 (refered to SfTS from now on). We’ve been shipping beta support for this template for a few months now through a compatible mapping file but users have found it to be lacking. The problem lies with the custom types used by SfTS. Both the MSF Agile 5.0 and Scrum 1.0 process templates use the standard Parent-Child relationship to link most work item types. With SfTS most links are named according to the type of the relationship. For instance, a task implements a product backlog item and is not merely a child of it, as with the other templates. The Parent-Child relationship was the only one supported by Urban Turtle until today. This meant that work items created with Urban Turtle would not appear as expected when looked at from the SfTS tooling and reports, and vice versa.

With Urban Turtle 3.10, we are introducing support for the Direct Links query mode which allows Urban Turtle to display all link types between work items. This means that a task that implements a product backlog item and another task that is a child of the same product backlog item will both be displayed as children on the planning board.

Another cool feature is that you can now explicitly define the link types in the mapping file. By default, when adding a child item using the plus sign on a card, the Parent-Child link type is used. You can override this by specifying the link type to use and Urban Turtle will automatically create the appropriate relationship when adding a child item. This is obviously required for the SfTS template, and the mapping file has been updated accordingly. You can also use this feature to restrict the work item types that are allowed to be created as children as only the link types specified are displayed on the Add child dialog. Define a single link type and you can even avoid the dialog altogether!

Teams!
The second major feature of this release is Team Configuration and Management. It is now possible to specify teams on a per-project basis, allowing further filtering options and better control over the Assign tasks to drop-down list on the task board.

A team is composed of a name, a root iteration, a root area and a TFS Security Group. Both the root iteration and area affect which iterations and areas are visible from Urban Turtle when the team is selected. By default, Urban Turtle uses the project node as the root for both the iteration and area paths. This new feature allows you to override this default behavior and automatically hide some classification paths. We expect people already using areas to divide team work to really appreciate this new feature.

We use the TFS Security Group to determine which teams are displayed on the new Team menu by verifying the current user’s membership. When a team is selected, the Assign tasks to drop-down list displays the security group members, this overrides the default behavior of listing individual users who have access to the project.

Configuration is done through the global.settings file, which was only used before to control access to Urban Turtle. Documentation for this file can be found here.

Other improvements
We’ve made several other improvements throughout the application. On the task board, we’ve tweaked the pagination system and turned the collapsing/expanding of a parent work item into an instant action. We’ve also fixed an issue with the Burndown where the planning board settings would be used even when launching it from the task board. More improvements and bug fixes are listed in our release notes on the download page.

Available now!
As usual, we recommend that everyone upgrade to the latest version. If you’re still pondering whether or not the Turtle is worth a try, rest assured that we’ve gone to great lengths to make the first experience as painless as possible. The setup is a simple three-click, next-next-next affair and the integration with Team Web Access is seamless. You’ll find two new tabs, Planning board and Task board, and with the common MSF Agile 5.0, Scrum 1.0 and now Scrum for Team System v3 templates, you’ll be up and running right after the installation. So don’t hesitate, download it and give it a try. Don’t forget about our community support site. All questions, comments, suggestions or bug reports are more than welcome. You’ll get answers straight from the team in a timely fashion, so post away!

It is really cold up here in Montreal, but this Turtle is not the hibernating kind. Once again, relentlessly, the team has worked hard to bring you its tenth release in ten consecutive months. While we’re happy with our track record, we’re definitely a lot happier with the contents of each of these releases and the latest one is no exception. It’s packed with new features, improvements and bug fixes of all kinds, so read on to find out what’s new!

Taskboard Improvements
Several new features have been added to the task board.

• Warning Zone


Ever since we’ve added support for the Visual Studio Scrum 1.0 process template, people have come to us asking why some work items were not visible on the task board. Most of the time, the simple reason was that they were in a state that was not configured to appear under one of the columns. While this made sense to us, it was still pretty confusing. We wanted to find a solution that would not force us to map states to columns in a way that did not make sense. What we’ve come up with is something that will hopefully remove some of the confusion while helping people realize that some work items should probably not be in the team’s sprint backlog.

Work items in a state not mapped to one of the task board columns will now appear under a new section dubbed ‘The Warning Zone’. The cards in this section appear a little bit different than the cards in columns. The state of the work item appears as a link that will allow you to quickly change to a state mapped to a column. In theory, the warning zone should never be visible. If you see it, it means you’re probably doing something against the rules.



• Recycle bin

The task board is all about simplifying work item state transitions. In this regard, we’ve implemented an equivalent to the Recycle Bin feature of the planning board. Put simply, if a ‘Deleted’ state is configured in your mapping file, as it is by default with the Scrum template, a recycle bin icon will be visible on the card if the transition to this state is possible. This is a great way to quickly remove tasks involving work that is now unnecessary!

• Blocked tasks

Scrum 1.0 users have asked us why there was no visual cue when they flagged a task as blocked. This was a very good question for which we simply had no good answer and so we went straight ahead and implemented the suggestion. Indeed, it is very useful to know at a glance that a task is blocked and requires attention from your Scrummaster. As always, this feature is configurable, meaning that you can add your own Blocked field to your work item type definition and gain this feature by rolling out your own mapping file.

• Independant iterations and areas

Another interesting change is that the task board now has iteration and area settings that are independant from the planning board. This allows you to view the current sprint on the task board while grooming your backlog on the planning board without having to switch back and forth between iterations.

Steer clear of the editor!
The work item editor is arguably the slowest window to use in Team Web Access. While it is sometimes a necessary evil, we’ve added some features to reduce round-trips to it.

• Detailed tooltips

We’ve replaced the default tooltips in some areas of the application by ones that display more information. For instance, the tooltip for a card in either board now displays the full title of the work item and the contents of a configurable description field. By default, when using the stock Scrum 1.0 and MSF Agile mapping files, we’ve configured the description field for each of the work item types to display the content of left-side text area from the work item editor.

This also works for the iteration information icon on the left-hand side of the planning board. With the Scrum 1.0 template, the tooltip will display the start and end dates of the sprint along with the team’s goal.

The information icon has also been added to the task board, to the right of the iteration drop-down list. You’ll have no good reason to forget your sprint goal now!


• Improved in-place editing

Urban Turtle 3.7 introduced in-place editing for work remaining on the task board as a way to avoid using the work item editor just to update a task. We had promised that this was only the beginning of a new trend in Urban Turtle, and with this new release, we’ve improved and extended this feature.

The major complaint with this feature in previous versions was that the clickable zone was just too small. Some people weren’t even aware of the existence of such a functionality in Urban Turtle. We’ve therefore expanded the zone and changed the visual style of the editable fields to improve usability.

Up until now, this feature only applied to the work remaining field, and only on the task board. This is no longer true as you will now be able to quickly edit both the work remaining and effort (story points) fields in either board. Decimal values are also now supported, making it possible to use your full planning poker deck, including the 0.5 card!

Support for Chrome and Safari
We are quite happy to announce that we’ve removed the biggest hurdle preventing Chrome and Safari support: drag and drop on the planning board. This bug finally moved up the priority ladder and the team happily squashed it! We expect feedback from the community regarding this initial support. There’s even a special place on our community support-site to notify us of any issue found while using Chrome or Safari. Please help us improve!

Other improvements and bug fixes
We’ve also managed to squeeze in many smaller improvements and bug fixes in this release:

• The Hour Burndown popup is now centered (and can now be shown more than once in Internet Explorer)
• New child items are never assigned to the current user
• Rank or priority is now always initialized to 0 when creating a work item
• The task board colum headers are now gray instead of orange to reduce eye bleeding
• It is now possible to enable Urban Turtle on a per-collection basis
• Several bug fixes listed in the release notes

We’ve put a lot of work into this release, coming in to work during snowstorms and arctic cold. It’s one of our most jam-packed releases and we hope you will enjoy everything it brings to the table. If you do, or if you don’t, we want to hear from you! The community site is more popular than ever and it’s a great way to gather votes for your ideas. So experience the latest version and voice your opinion. We’re listening!

Nine in nine!
As our customers are well aware of, each and every month we release a new Turtle. For each of these releases, we try to focus on soothing users pains while respecting our vision of a simple, dedicated Scrum management tool for Team Foundation Server. It’s actually a fun and challenging balance to try and maintain and the team loves challenges!

Out with the old…
Our main focus for Urban Turtle 3.8 was improving support for dealing with multiple states in the task board columns. We used to have a feature where, upon dropping a work item onto a column where multiple states were mapped, a dialog would pop up to let the user pick the new state. This was fine when moving between columns but it was quite impractical if you wanted to transition to another state that was mapped to the same column. Put simply, we made it hard for fans of the popular To Do -> In Progress -> Ready to test -> Done workflow to use our task board.

…in with the new!
With this new version, you can now pick the next state for your work item as you drop it on the column. But what makes it really interesting is that you can now drop a work item in the column it is already in while choosing a new state. It is very straight-forward and quick to pick up. Taking the previous example, you could now map both the In Progress and Ready to test states to the In Progress column and easily transition between these states.

To help you distinguish between the multiple states in each of the column, we have added the ability to configure a color for each of the states. This color is then used to add a visual cue on the card and on the drop zones when dragging work items. This configuration is a new section in the mapping file. If you use a customized mapping file, you will need to add the section and pick colors for the different states in your project.

And a few bonuses
Other features include keyboard shortcuts to quickly switch between active users on the task board. We expect this to be quite popular in your daily scrums.

We have also added two new colors, Orange and Brown, for your work items.

As usual, we invite everyone to download and install the latest version. We can’t wait to hear from you about these new features, particularly regarding the task board improvements. So don’t wait, and get it while it’s hot! And don’t forget to visit our community site to share comments, ask questions and report issues!

8 months, 8 releases
The team is back at it again. Another month sees another release out in the wild. We’re once again quite proud to have been able to stick to our monthly release cycle, but we’re even more proud of what you will actually find in this new version. ‘Tis the season and Santa has something for every member of your Scrum team!

A more agile task board
Our previous release included various performance improvements but most of them simply went unnoticed because of the tremendous gains asynchronous ranking brought forth. While this really helped during planning and backlog grooming sessions, some team members might have felt left out. We’ve therefore decided to take everything we’ve learnt developing this feature and apply it to the task board. No longer will you wait for the dreaded spinner to disappear when moving work items through the task board columns. Everything gets updated asynchronously and state transitions are now swift and smooth.

But this is not the only improvement the task board has received. Users loved the automatic assignment feature, which assigns tasks moved to the In Progress column to the currently logged-in user. While this was quite useful for team members during the day, it proved somewhat annoying during stand-up meetings. We decided to implement an idea from a member of our community which described a way to select an active user on the task board. Instead of assigning tasks to the logged-in user, we now assign them to the selected user. We’ve further enhanced this feature by adding the option of highlighting the selected user’s tasks.

One more feature that we expect will be very appreciated by developers on your team is the ability to specify work remaining on the work item card itself. No longer do you have to open the work item editor, edit the work remaining field, save and close and wait for a full task board refresh. In-place editing turns a chore into pure joy! Sure, you will start hoping right away for the ability to edit other fields in the same way, but rest assured, this is only a glimpse of a bright and exciting future!

Hopefully, these improvements to the task board will make the turtle a little more daily-friendly!

Improved Planning
We’ve turned a long requested feature into reality with this new version. Actually, this idea was originally mentioned by a previous member of our team, before the initial 3.0 release. It has taken some time but the iteration/area and work items sections on the planning board have been split into two and no longer share a single scrollbar. This means that you can now take the last work item on your backlog and move it to the top-level area without feeling any pain in your hand!

Goodbye, session timeouts!
It is quite common for developers to leave the task board open in the background and come back to it after having completed a task. What would then happen is that they’d try to move their task to the Done column only to see the task board being refreshed, and their task still sitting under In Progress. A frustrating sigh later, the card would be moved a second time to the Done column, hopefully sticking to it this time. The cause of this was a simple session timeout. Fortunately, a combination of many changes made throughout the different releases enabled us to actually complete the intended action even when the session is expired. This is only one example of a frustrating moment caused by session timeouts, but other actions will also successfully complete, such as moving a work item to an iteration.

Miscellaneous Improvements
Several other changes can be found in this release. For instance, the number of cards per stack can now be changed through a new menu option. Switching between viewing the iteration or the area on a card on the planning board is now instantaneous. Data for the next day (tomorrow) is no longer displayed on the burndown chart.

We’re also including a beta version of our configuration mapping file for the Scrum for Team System v3 process template. We know this is a popular template and we hope users will try it and send us feedback so that we can further improve our support for it.

Courtesy of the Turtle Hospital

Once again, we recommend to everyone to upgrade to the latest version. We will eagerly be waiting for your comments. As usual, make sure your voice gets heard on our community-powered support site. The weather outside might be frightful, but the turtle is delightful. This season, present your team with the gift of the turtle and witness joy, daily!

The turtle ride continues, 6 releases in 6 months!
Team Urban Turtle is once again proud to announce the release of a new version of Urban Turtle. We’ve received a lot of feedback from our customers and partners and we’ve worked hard to show our appreciation to all the turtle aficionados out there!

Burndown filtered according to selected area
John, this one’s for you! …and for many other people who have told us it would be great if the real-time burndown in Urban Turtle would take into account the currently selected area, like it does the selected iteration.

Support for Readers
Not everyone who needs access to Urban Turtle should have the appropriate rights to actually edit work items. Urban Turtle did not always play nice with people having limited access rights, such as people in the default TFS Readers group. You can now safely allow anyone to take a look at your team’s progress. Urban Turtle automatically activates drag and drop and editing capabilities according to the user’s access rights.

Per-project activation
Want to test drive Urban Turtle with a pilot project without impacting the other projects on your server? No problem! Urban Turtle can now be set to appear only for projects specified in a configuration file. This one’s strictly for administrative purposes. Contact us for more information about how to use this feature. Urban Turtle is still a next-next-next experience, meaning click through the installation wizard and the turtle is ready to go! All projects have access to Urban Turtle by default.

Improvements and fixed issues
We’re not perfect. We make mistakes. And we embrace opportunities to improve our development process and our product!

Urban Turtle now automatically selects the first valid configuration mapping file for your project. We’ve improved the session management and the favorite iterations/areas feature. The footer now displays important information about your license. And everyone can uninstall the product (when you need to upgrade to the latest version, of course!). We also fixed this, this, this and several other issues. And for a lot these improvements, we have you to thank for your feedback. You guys are awesome!

There is simply no reason not to try Urban Turtle! So give it a shot and download Urban Turtle 3.5 today! And, as always, we strongly encourage you to take the time and send us questions and comments either directly or through our community support site. Any kind of comments, good and bad. We just want to improve and create a better product, release after release, and we just cannot do it without you!