Our Kanban board is already pretty powerful.  Recently, we have added prioritization to the board and a number of Mashups that provide a basic implementation for Classes of Service and even visualization of Due Dates.  Now, we would like to introduce you to another Mashup for the Kanban board: the column grouper.

This Mashup allows you to group together various swimlanes on your board, and even have group WIP limits that apply to the grouped columns in aggregate.  For example, you can now have a WIP group called “Development” that contains all the swimlanes related to development, another for Testing, and another for your Release process.  Each of these swimlanes can have their own individual limits, and each of the swimlane groups can have an aggregate limit.

The Mashup is 100% customizable in terms of your group names, columns, and limits.  Check out the Mashup in our Mashups Library on GitHub for download links and more information.

TargetProcess v.2.22.10 is available to all the On-Demand customers and Free edition users. On-Site customers will be able to upgrade by the end of the week.

The New Bugzilla Integration Plugin: Faster and Easier

Our new Bugzilla plugin is the best on the market for sure. It can’t be any easier to setup and use a plugin. Auto-mapping makes setup a breeze, while the new mashups come handy for an even closer integration. Read more about Bugzilla plugin.

NOTE: The new plugin is fully functional, but it’s not possible to convert the old profiles so far. You can set up new test profiles on a dummy project.

Bugzilla - TargetProcess integration: map priorities

REST API Improvements

  • REST: update inactive project
  • REST: incorrect update if inner entity does not exist
  • REST: get/update custom fields for the Project entity
  • REST: Reset Iteration value when reset Release
  • REST: Filter by acid in Context
  • REST: exception adding a new User if the Developer role renamed

Other Fixes

It really is:

TargetProcess Support Case

TargetProcess v.2.22.9 is available to all On-Demand customers and On-Site Free users. Public release for On-Site customers is due in several days.

This release is quite significant as it includes a number of major improvements.

Beta Views: inner lists with inline edit and prioritization

Order bugs and tasks inside a User Story. Inline edit on the fly. Read more about improvements in lists.

Ordering and Inline Edit in lists

Beta Views: Implementation History for Features, User Stories, Bugs, Tasks and Requests

This visualized timeline shows full progress including all the state changes, time spent, responsible persons, impediments, added and closed bugs, and tasks. More on how the Visual Flow can help you.

Visual Flow

Mashup Manager: basic release

On-Demand users can create their own mashups in minutes or re-use out-of-the-box mashups. Note: you need Admin rights to create and manage mashups.

Mashups manager

Multi-select custom fields (not available in Beta Views so far)

It’s finally there. If you need a custom field with multiple choices, you can now use it.

Multiple Selection

Burn Down calculation when Time Tracking is not used

Now you can have accurate burn downs even if you don’t use time tracking at all. Just update the remaining effort in Task Board and check the progress on Sprint Burndown chart.

 

Tasks added to Prioritize screen

Order Tasks, Stories and Bugs by their priority for your developers

 

REST API fixes and improvements

  • REST: Test Plan Run collection for Test Plans added
  • REST: HTTP 500 error for requests if user logged with Windows Authentication
  • REST: exception on resetting custom field value to NULL
  • Plugins: Logs and Data Folder not deleted when TP is updated

Other Fixes

Our real Kanban Board snapshot. Note that it is enhanced by two mashups: Team Load (by @alexsane) and Classes of Services (by EugeneKha).

Live Kanban Board Jan 13

Here’s what we received from our hosting provider:

Our data center which is owned by Verizon Canada is having a global outage and they are in complete dark right now. None of their backup power flipped over. We have a backup generator and UPS that should all automatically pick up.

They will be releasing a statement apologizing for the issue once all is said and done that you can extend to your clients. We can also talk about compensation at that time.

For the time being we are anxiously waiting on power to be restored, we will update you as soon as we have more from Verizon.

We will update you about the status.

UPDATE: 6 AM EST

Power is restored, our datacenter is having trouble with the network but the problems should be resolved shortly.

They have 24 hours of UPS and 24 hours of diesel fuel onhand. The issue was the flip did not work properly and did not flip over to an alternate power source. Power has been restored for quite sometime but they are having troubles getting their networking equipment going.

We use the top datacenter in Toronto, most of the banks use the same one as us.

We have had constant communication with them every 10 minutes, this issue is effecting multiple other large clients of Verizon as well. They won’t issue an ETA but say it could be any minute.

All of the servers are on, we are just waiting for them to fix connectivity. I will make sure you have something to give to your clients that explains the issue in detail.

UPDATE: 8:12 EST

Some of Verizons(datacenter) routers were damaged in the power surge. They are reloading the configuration on those devices. They won’t issue an ETA but are working on it with all hands on deck.

We have numerous staff at the datacenter and keep phoning for updates frequently.

I don’t have a firm ETA but I would think by the amount of man power working on this for the past few hours, it should be fixed any time.

UPDATE: 9:20 EST

We received an ETA from the datacenter of 1 hour. We were in the process of moving the equipment to our 2nd datacenter but given the new ETA. We will give it the hour before moving.

UPDATE: 10:47 AM EST

Servers are back! Please let us know if you have any problems.

UPDATE: 1:15 PM EST We received update from our hosting provider with some explanations:

At 11:30PM on Monday, January 9th the Verizon datacenter lost complete power. Normally this would not be a problem as they should failover to Verizon’s UPS or generator. For reasons that have not yet

been explained to us, none of the alternate power sources picked up. This caused the entire datacenter to lose all power and lights. We had someone onsite by 12AM on Tuesday, January 10th to investigate the issue.

At this time numerous other large customers of Verizon also arrived, demanding answers about the situation. We knew very little until the power was restored at roughly 2AM. We were then able to power all servers and equipment and ensure everything was in a healthy condition. Verizon announced at this time they were having “internal network problems” that they were trying to resolve and did not have an ETA as to when it would be fixed.

We escalated the case along with the other companies using the facility. Verizon was unable to provide any ETA or information on what was wrong until roughly 10AM EST. The issue was found to be 4 cards in a Cisco gateway were damaged as a result of a short circuit within Verizon. We were told 4 cards were being rushed to the facility and we would be back online in roughly 1 hour. All systems came back online at 10:45AM EST.

It was very difficult for us to provide much information to our clients during the outage because the issue was not with our equipment or infrastructure directly.

Verizon will be making an announcement and providing more detail in the coming days.

UPDATE: Jan 13

We’ve received official email from Verizon

Dear Verizon Canada customer:

On Monday, January 09 at 11:02 PM EST Verizon’s network connections in
the Toronto data center experienced a service interruption. This
incident was triggered by numerous utility voltage fluctuations followed
by a total loss of utility power. Verizon backup power systems came
online as designed but a failure occurred during the transfer to
generator power.

At approximately 11:20 PM EST the power in the Verizon colocation
facility failed. By this time Verizon field engineers were on site to
investigate the power incidents. Utility power was restored at
approximately 11:31 PM EST which also restored colocation power.

Residual problems with the UPS systems were observed. Verizon field
engineers engaged vendor and third party assistance to restore full
functionality. At approximately 12:00 AM EST the UPS came back on line
and the power systems were fully restored throughout the facility.

At about 12:30AM commercial power returned and site was transferred
back.

Verizon observed problems within the network infrastructure and began
troubleshooting. At approximately 03:00 AM EST it was determined that
there were multiple hardware failures in the switching infrastructure.

At 06:49 AM EST network field technicians were dispatched to replace
hardware.
By 08:49 AM EST the incidents were escalated to level 3 engineers.
At 09:37 AM EST it was determined that additional hardware was required
from another Verizon site within Toronto.
At 10:32 AM EST all faulty hardware was replaced.

Network services were fully restored at 10:41 AM EST.

********

Corrective actions were planned and an emergency maintenance was
performed on January 12th 2012, at 12:00 AM EST to bypass the power
equipment which failed during the transfer to generator power. Verizon
procedures have been adjusted to improve the speed of escalation for
network infrastructure devices at this facility.

Current development status @ TargetProcess. Important things are highlighted:

TargetProcess Kanban Board

New Views with full inline edit are on the way. In TargetProcess v.2.23 (to be released in January) the Inner Lists will be really powerful. It will be possible to inline edit content in lists, use drag and drop to prioritize entities, and run any actions in lists.

As we collect feedback, we’re also working to fine-tune the Views. For example,  the related entities part has been improved a lot (navigation, re-ordering and changing states).

States reordering in Workflow

You’ve customized your workflow for Tasks, and there are several states on your Task Board now, such as Open, Reviewing, In Progress and Done. Now you want to reorder these states (you need Admin rights for that).

Go to Settings > Process > Edit Process > Workflow. Select Task. Drag and drop the states as you wish.

Reorder states

If you drag a state and put it on top, this state will always be the Initial one.
You cannot drag the last (final) state. It is final, so it always comes last. You can rename it though. Similarly, you can reorder states for User Stories, Bugs, Features.

Which areas are affected?

  1. Order of states in the change state drop downs
  2. Order of columns on the Task Board
  3. Order of states in the History tab
  4. Default order of columns on the Kanban Board and Teams Board

Subversion to TargetProcess: auto-mapping users

One-click-mapping between Subversion users and TargetProcess users is available now. It compares users logins, emails and names to fill the mapping.

Tags: import and export

You can import tags with User Stories, Bugs, Features and other entities. Just create a Tags column and put required tags like: tag1, tag with long name, tag2

REST API

Ordering: You can order items using various fields like http://tp/api/v1/UserStories?orderBy=Iteration.StartDate

Other Fixes:

  • TestCasesRun collection, TestCasesRun-count, TestPlan, Build references added to TestPlanRun
  • Deserialization error when setting null value to custom fields
  • Forbid to change EntityType of Priority

Fixed Bugs

© 2012 TargetProcess Product Blog Suffusion theme by Sayontan Sinha