<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' version='2.0'><channel><atom:id>tag:blogger.com,1999:blog-30774001</atom:id><lastBuildDate>Wed, 29 Apr 2009 10:08:53 +0000</lastBuildDate><title>TargetProcess Day by Day | Agile Development On Real Project</title><description>Agile development of TargetProcess application, C#, ajax, ASP.NET 2.0, code, examples, usability, ideas, design</description><link>http://www.targetprocess.com/agileproductblog/</link><managingEditor>noreply@blogger.com (Michael Dubakov)</managingEditor><generator>Blogger</generator><openSearch:totalResults>122</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-7252324074378218502</guid><pubDate>Sun, 05 Apr 2009 21:28:00 +0000</pubDate><atom:updated>2009-04-05T23:32:36.727+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>ruby</category><category domain='http://www.blogger.com/atom/ns#'>API</category><category domain='http://www.blogger.com/atom/ns#'>soap</category><category domain='http://www.blogger.com/atom/ns#'>web services</category><title>Using TargetProcess SOAP API in Ruby Application</title><atom:summary type='text'>It is quite easy to access TargetProcess SOAP API via Ruby.
Install soap4r
First thing you need to install soap4r. SOAP4R is a Ruby library for accessing Web Services via SOAP.
gem install soap4r --include-dependencies
Generate Classes From WSDL
For example, you want to use ProjectService API. You have to generate some classes using wsdl2ruby.
[path_to_wdsl2ruby]wsdl2ruby.rb --wsdl [</atom:summary><link>http://www.targetprocess.com/agileproductblog/2009/04/using-targetprocess-soap-api-in-ruby.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-1664406976121874784</guid><pubDate>Wed, 01 Apr 2009 10:12:00 +0000</pubDate><atom:updated>2009-04-01T15:40:41.879+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>waterfall</category><category domain='http://www.blogger.com/atom/ns#'>agile</category><category domain='http://www.blogger.com/atom/ns#'>release</category><title>TargetProcess Announced v.2.14 Release With Full Waterfall Support</title><atom:summary type='text'>We are extremely happy to announce the full Waterfall support in TargetProcess. No wonder it has the reputation of being the most flexible agile project management software on the market! New v.2.14 (special edition) will include features like:


Gantt Charts On All Levels
You will at least see nice and accurate Gantt charts in project, release and even iteration scope. Now you may define and </atom:summary><link>http://www.targetprocess.com/agileproductblog/2009/04/targetprocess-announced-v214-release.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>25</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-1432071255745787297</guid><pubDate>Thu, 26 Mar 2009 10:30:00 +0000</pubDate><atom:updated>2009-03-26T12:56:56.051+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>JavaScript</category><category domain='http://www.blogger.com/atom/ns#'>asp.net</category><category domain='http://www.blogger.com/atom/ns#'>ajax</category><title>ASP.NET 2.0 AJAX, Safari and Scroll Offset Tricks</title><atom:summary type='text'>Couple days ago, I faced odd bug with DragDropManager at Microsoft.Web.Preview.dll. It doesn’t work correctly if the page is scrolled down in Chrome and Safari browsers. Google did not help. Debugging did not help as well (DragDropManager file is really huge). The last way was to use reflector tool to dig into sources.

The first odd thing was classes hierarchy. Two classes were the most </atom:summary><link>http://www.targetprocess.com/agileproductblog/2009/03/aspnet-20-ajax-safari-and-scroll-offset.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>1</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-3428176735423637401</guid><pubDate>Tue, 24 Feb 2009 19:15:00 +0000</pubDate><atom:updated>2009-02-24T21:37:37.327+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>help desk</category><category domain='http://www.blogger.com/atom/ns#'>support</category><category domain='http://www.blogger.com/atom/ns#'>release</category><category domain='http://www.blogger.com/atom/ns#'>email integration</category><category domain='http://www.blogger.com/atom/ns#'>issues</category><title>TargetProcess v.2.13 released: Help Desk improvements</title><atom:summary type='text'>Yesterday we've released TargetProcess v.2.13. The release is fully dedicated to Help Desk improvements. 

In short, we've improved Help Desk user experience and made some actions easier. Some usage patterns:





ActionOld wayNew way


Check for unprocessed requestsNavigate to requests list, sort by date. Then sort by last comment date. Filter out ideas to see just issues and questions.Navigate </atom:summary><link>http://www.targetprocess.com/agileproductblog/2009/02/targetprocess-v213-released-help-desk.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>3</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-1575436090863165447</guid><pubDate>Sun, 15 Feb 2009 23:25:00 +0000</pubDate><atom:updated>2009-02-16T01:43:15.528+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>usability</category><category domain='http://www.blogger.com/atom/ns#'>design</category><category domain='http://www.blogger.com/atom/ns#'>developing</category><category domain='http://www.blogger.com/atom/ns#'>UI</category><category domain='http://www.blogger.com/atom/ns#'>navigation</category><title>Developing TargetProcess v.3.0: Navigation (Tabs or Tree?)</title><atom:summary type='text'>First thing we are going to change in v.3.0 is navigation. First discussion was quite general and first solution most likely is not ideal. We rightly identified two major different areas: inside and outside of a project. Initially we wanted to separate navigation outside of a project and inside of a project, thus having two completely different menus. But what if we can unite these areas?

Indeed</atom:summary><link>http://www.targetprocess.com/agileproductblog/2009/02/developing-targetprocess-v30-navigation.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>19</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-2544017184753249616</guid><pubDate>Tue, 10 Feb 2009 22:00:00 +0000</pubDate><atom:updated>2009-02-10T23:24:12.267+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>helpdesk</category><category domain='http://www.blogger.com/atom/ns#'>help desk</category><category domain='http://www.blogger.com/atom/ns#'>usability</category><category domain='http://www.blogger.com/atom/ns#'>design</category><category domain='http://www.blogger.com/atom/ns#'>developing</category><category domain='http://www.blogger.com/atom/ns#'>UI</category><title>New Help Desk Portal. Issues.</title><atom:summary type='text'>Let's finalize new Help Desk Portal concept. We are starting development next week, so you have a little time to provide valuable feedback :)

Issues List
Contains all issues with filtering option. State of the each issue is highly visible. It shows whether bug created from the issue and when it will be fixed. Also if someone knows solution, he may attach solution to the issue right away.


Post </atom:summary><link>http://www.targetprocess.com/agileproductblog/2009/02/new-help-desk-portal-issues.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>7</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-2316949294699198890</guid><pubDate>Tue, 10 Feb 2009 00:10:00 +0000</pubDate><atom:updated>2009-02-10T02:28:46.899+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>helpdesk</category><category domain='http://www.blogger.com/atom/ns#'>help desk</category><category domain='http://www.blogger.com/atom/ns#'>usability</category><category domain='http://www.blogger.com/atom/ns#'>design</category><category domain='http://www.blogger.com/atom/ns#'>developing</category><category domain='http://www.blogger.com/atom/ns#'>UI</category><title>New Help Desk Portal. My Requests</title><atom:summary type='text'>Continue posting mock-ups of the upcoming Help Desk Portal. Definitely there should be a place where people may see all posted ideas, issues and questions. In this list user should focus on what is going on and get quick answers to the questions like: 

"Should I reply to something to help with problem resolution?"
"When will the bug for the request XXX be fixed?"
"Are there any interesting </atom:summary><link>http://www.targetprocess.com/agileproductblog/2009/02/new-help-desk-portal-my-requests.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-529786010734186562</guid><pubDate>Mon, 09 Feb 2009 15:20:00 +0000</pubDate><atom:updated>2009-02-09T17:44:02.837+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>helpdesk</category><category domain='http://www.blogger.com/atom/ns#'>help desk</category><category domain='http://www.blogger.com/atom/ns#'>ideas</category><category domain='http://www.blogger.com/atom/ns#'>design</category><category domain='http://www.blogger.com/atom/ns#'>developing</category><category domain='http://www.blogger.com/atom/ns#'>UI</category><category domain='http://www.blogger.com/atom/ns#'>issues</category><title>New Help Desk Portal. Ideas and Issues.</title><atom:summary type='text'>We are thinking about Issues and Ideas separation. They are quite different and needs separate lists, views, etc. based on our analysis. People have different goals when working with ideas and issues, and this should be reflected in the dHelp Desk Portal design.

What is important for person who looks at idea? And what is important for person who looks at issue? 



Idea
Issue


Discuss idea
Add </atom:summary><link>http://www.targetprocess.com/agileproductblog/2009/02/new-help-desk-portal-ideas-and-issues.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-3811549488620614696</guid><pubDate>Thu, 05 Feb 2009 22:14:00 +0000</pubDate><atom:updated>2009-02-06T01:43:07.202+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>help desk</category><category domain='http://www.blogger.com/atom/ns#'>usability</category><category domain='http://www.blogger.com/atom/ns#'>design</category><category domain='http://www.blogger.com/atom/ns#'>developing</category><title>New Help Desk Portal. Moving Forward.</title><atom:summary type='text'>Finally, I may share ideas/stories/requests that will be implemented in the new release of Help Desk Portal.

We have selected about 20 customers' requests and improvements (all are reasonable and most of them improve usability). Here is the list that includes the most interesting requests.


Search by ID
View Help Desk Request Number (#) in Requests Lists
Add a "Vote" mechanism to the request </atom:summary><link>http://www.targetprocess.com/agileproductblog/2009/02/new-help-desk-portal-moving-forward.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>3</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-6759217377319029855</guid><pubDate>Mon, 02 Feb 2009 21:01:00 +0000</pubDate><atom:updated>2009-02-02T23:14:38.091+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>v.3.0</category><category domain='http://www.blogger.com/atom/ns#'>help desk</category><category domain='http://www.blogger.com/atom/ns#'>usability</category><category domain='http://www.blogger.com/atom/ns#'>design</category><category domain='http://www.blogger.com/atom/ns#'>developing</category><category domain='http://www.blogger.com/atom/ns#'>UI</category><title>Developing TargetProcess v.3.0: New Help Desk Portal</title><atom:summary type='text'>Help Desk Portal is quite important application. It allows our customers to interact with us. Also it allows customers of our customers to interact with our customers (weird assertion, but it's true :). We've collected quite many requests for Help Desk Portal improvements and finally decided to push it forward. 

Here is the first mockup of the home page. It is still a work in progress, so </atom:summary><link>http://www.targetprocess.com/agileproductblog/2009/02/developing-targetprocess-v30-new-help.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>8</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-2357125993845252150</guid><pubDate>Wed, 28 Jan 2009 11:15:00 +0000</pubDate><atom:updated>2009-01-28T14:19:46.936+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>v.3.0</category><category domain='http://www.blogger.com/atom/ns#'>usability</category><category domain='http://www.blogger.com/atom/ns#'>design</category><category domain='http://www.blogger.com/atom/ns#'>developing</category><title>Developing TargetProcess v.3.0: Redesigning Comments List</title><atom:summary type='text'>We are redesigning comments to make them more usable. Redesign includes clear formatting and some functional improvements. Current comments list has several problems as you see:



Here is the list of ideas:

Currently to add a comment user should click add link and the form appears on the bottom of the list. The add link will be removed and comment form will be always visible.

Currently when </atom:summary><link>http://www.targetprocess.com/agileproductblog/2009/01/developing-targetprocess-v30.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>4</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-1421334433950381000</guid><pubDate>Tue, 27 Jan 2009 11:35:00 +0000</pubDate><atom:updated>2009-01-27T13:49:29.702+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>report engine</category><category domain='http://www.blogger.com/atom/ns#'>howto</category><category domain='http://www.blogger.com/atom/ns#'>report</category><title>Using Custom Reports: Time Spent on Releases</title><atom:summary type='text'>How much time we spent on a particular release? Quite interesting question that can be answered using Custom Reports functionality. For example, last release of TargetProcess v.2.12 took about 5,500 hours. That is MUCH more than any of the previous releases. OK, let's try to create the report.
Step 1
Navigate to Custom Reports and click Create New report button. Select Release entity.
Step 2
Add </atom:summary><link>http://www.targetprocess.com/agileproductblog/2009/01/using-custom-reports-time-spent-on.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-732303906552217085</guid><pubDate>Tue, 20 Jan 2009 18:17:00 +0000</pubDate><atom:updated>2009-01-20T23:40:26.837+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>v.3.0</category><category domain='http://www.blogger.com/atom/ns#'>usability</category><category domain='http://www.blogger.com/atom/ns#'>ideas</category><category domain='http://www.blogger.com/atom/ns#'>developing</category><category domain='http://www.blogger.com/atom/ns#'>UI</category><title>Developing TargetProcess v.3.0: Lists</title><atom:summary type='text'>Lists in v.3.0 was a hot topic during today's meeting. It seems we will replace all lists in v.3.0 (such as User Stories, Bugs, Requests, etc) with lists based on the Custom Reports functionality. It will be possible to create custom lists (same way as a custom report) and to include these lists into the Main menu. For example, you may create Current Iteration Stories list or Open Stories list </atom:summary><link>http://www.targetprocess.com/agileproductblog/2009/01/developing-targetprocess-v30-lists.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>6</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-6103934773517314232</guid><pubDate>Mon, 19 Jan 2009 19:36:00 +0000</pubDate><atom:updated>2009-01-19T22:52:43.997+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>v.3.0</category><category domain='http://www.blogger.com/atom/ns#'>usability</category><category domain='http://www.blogger.com/atom/ns#'>developing</category><category domain='http://www.blogger.com/atom/ns#'>navigation</category><title>Developing TargetProcess v.3.0: Navigation</title><atom:summary type='text'>Today we've discussed navigation problems in TargetProcess and all agreed that we have four major issues:

Similar labels in menu (for example, Reports inside a project area and Custom Reports in top menu).
Too many links in the header (for example, in Project -&gt; Planning area there are 31 links to click).
Menu structure and how to get into required place (why Tags Board is in the Dashboard </atom:summary><link>http://www.targetprocess.com/agileproductblog/2009/01/developing-targetprocess-v30-navigation.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>5</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-2204216874231835975</guid><pubDate>Fri, 16 Jan 2009 02:18:00 +0000</pubDate><atom:updated>2009-01-16T19:09:54.372+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>report engine</category><category domain='http://www.blogger.com/atom/ns#'>howto</category><title>Using Custom Reports: Creating Stories Quality Report</title><atom:summary type='text'>Report Engine in TargetProcess is quite interesting beast. It allows you to extract data in different ways. For example, you may to create stories quality report that shows number of total bugs, open bugs, failed and passed test cases for each user story. Let's try to create the report in TargetProcess v.2.12.

First click to Custom Reports link on the top and then push New Report button. You </atom:summary><link>http://www.targetprocess.com/agileproductblog/2009/01/using-custom-reports-creating-stories.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-2929311215437273692</guid><pubDate>Mon, 12 Jan 2009 18:16:00 +0000</pubDate><atom:updated>2009-01-13T14:02:22.277+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>howto</category><title>First Thing To Do With Your Copy of TargetProcess</title><atom:summary type='text'>We get emails from people who are just starting out with TargetProcess, and they go: where do we begin? What is an Iteration? What is a User Story? How do I plan Release? How to I create a Requirements Backlog? How can I learn fast? Our universal answer to these questions is a cute Getting Started page (Home - Getting Started). You could use it as a quick visual introduction to TargetProcess and </atom:summary><link>http://www.targetprocess.com/agileproductblog/2009/01/first-thing-to-do-with-your-copy-of.html</link><author>noreply@blogger.com (Olga Kouzina)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>3</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-4543967237021865765</guid><pubDate>Fri, 12 Dec 2008 09:53:00 +0000</pubDate><atom:updated>2008-12-12T12:26:27.116+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>typo</category><category domain='http://www.blogger.com/atom/ns#'>fun</category><category domain='http://www.blogger.com/atom/ns#'>humor</category><title>Funny Typo in TargetProcess User Guide</title><atom:summary type='text'>Yesterday we've got an email from one of our leads with a typo in TargetProcess user guide. He has really great sense of humor!

"Hehe…found this today and thought you may want to fix it….Unless there’s some new interface you are working on I’m not aware of."

</atom:summary><link>http://www.targetprocess.com/agileproductblog/2008/12/funny-typo-in-targetprocess-user-guide.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-4530251190094016578</guid><pubDate>Thu, 11 Dec 2008 11:31:00 +0000</pubDate><atom:updated>2008-12-11T13:37:43.511+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>tags</category><category domain='http://www.blogger.com/atom/ns#'>tag</category><category domain='http://www.blogger.com/atom/ns#'>categorization</category><title>Product Owner Usage Pattern: Categorize Requirements with Tags</title><atom:summary type='text'>As a Product Owner you deal with many functional requirements. You need a way to keep them categorized and find requirements for specific category quickly. In TargetProcess you may store requirements as Requests, Features and User Stories.The best way to categorize information in a free form is Tags. TargetProcess provides full support of tags categorization. As a Product Owner you have the </atom:summary><link>http://www.targetprocess.com/agileproductblog/2008/12/product-owner-usage-pattern-categorize.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-5654684698230931303</guid><pubDate>Tue, 02 Dec 2008 13:36:00 +0000</pubDate><atom:updated>2008-12-02T15:47:04.301+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>survey</category><title>What Features Should be Improved/Updated in Next Releases?</title><atom:summary type='text'>Continue to post survey results. Here is the list of what should be improved in TargetProcess.


 FeatureRelevant customization 79% integration 74%agile planning and tracking 96%QA 83%reports and dashboards 81% people allocations 75% collaboration 77% help desk 55% email integration 52%time tracking 68%

Interestingly, agile project planning and tracking is on the top. The main goal of the tool </atom:summary><link>http://www.targetprocess.com/agileproductblog/2008/12/what-features-should-be-improvedupdated.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-6564181298742124899</guid><pubDate>Wed, 05 Nov 2008 23:02:00 +0000</pubDate><atom:updated>2008-11-06T01:32:05.400+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>integration</category><category domain='http://www.blogger.com/atom/ns#'>survey</category><title>Usage of Integration Features in TargetProcess</title><atom:summary type='text'>I continue posting customers' survey result. One of the question was about integration abilities usage of TargetProcess. Here are the results.


 Very Important Never used CSV Import/Export40%  37% VS 2008 47% 42% JIRA 11% 78% Bugzilla 15%72%  TestTrack Pro 2%85%  Selenium20% 70%  NUnit 38%44%  Subversion 57% 39%  Perforce 4% 87% Source Safe 9% 80%

As you see, TestTrack Pro, Perforce and </atom:summary><link>http://www.targetprocess.com/agileproductblog/2008/11/usage-of-integration-features-in.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>2</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-3614546810733297325</guid><pubDate>Wed, 29 Oct 2008 10:35:00 +0000</pubDate><atom:updated>2008-10-29T12:42:51.109+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>targetprocess</category><category domain='http://www.blogger.com/atom/ns#'>survey</category><title>TargetProcess Customers' Feedback</title><atom:summary type='text'>We've conducted TargetProcess survey among our customers. The goal of the survey was to check people happiness, determine most important problems and future product development directions. Overall we've got responses from 65 companies. There will be some posts about results in this blog. 

One question was "Your personal feedback as a TP user". See below all the answers (without any shortcuts or </atom:summary><link>http://www.targetprocess.com/agileproductblog/2008/10/targetprocess-customers-feedback.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-4069954657928201323</guid><pubDate>Thu, 09 Oct 2008 13:59:00 +0000</pubDate><atom:updated>2008-10-13T15:34:33.219+02:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>help desk</category><category domain='http://www.blogger.com/atom/ns#'>future</category><title>Help Desk Portal Future</title><atom:summary type='text'>TargetProcess has Help Desk on board. I think it is important to have close relation with customers, to collect their feedback and react on issues and ideas. We've designed Help Desk Portal for that purpose. It is a separate simple application integrated with TargetProcess via API. Customers may post ideas, requests and questions via Help Desk Portal, vote for requests, post comments.

Over the </atom:summary><link>http://www.targetprocess.com/agileproductblog/2008/10/help-desk-portal-future.html</link><author>noreply@blogger.com (Michael Dubakov)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>1</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-9184577692126713440</guid><pubDate>Thu, 09 Oct 2008 07:09:00 +0000</pubDate><atom:updated>2008-10-09T09:30:54.674+02:00</atom:updated><title>TargetProcess Development Tricks: Clear NHiberante cache using ASP.NET handler (.ashx)</title><atom:summary type='text'>
Sometimes we need to clear cache of NHibernate. For example when the database was changed without using NHibernate. We have created the corresponding handler in web application ClearCache.ashx with the following code:

&lt;%@ WebHandler Language="C#" Class="ClearCache" %&gt;
using System;
using System.Collections;
using System.Web;
using NHibernate;

public class ClearCache : IHttpHandler
{
  public </atom:summary><link>http://www.targetprocess.com/agileproductblog/2008/10/targetprocess-development-tricks-clear.html</link><author>noreply@blogger.com (Oleg Seriaga)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-6818705149404766100</guid><pubDate>Thu, 02 Oct 2008 06:17:00 +0000</pubDate><atom:updated>2008-10-02T08:27:22.351+02:00</atom:updated><title>TargetProcess Development Tricks: Force ExtJS GridPanel skip events processing raised from nested grid panels</title><atom:summary type='text'>
We got a problem with implementing inner grids based on ExtJS. ExtJS GridPanel reacts on every event from inner GridPanel by default. For example sorting in nested grid causes the sorting in parent. That is not good. Find below the code which will allow to deny the event processing in GridPanel if it is fired in its child grid panel:



Ext.override(Ext.grid.GridPanel, {
    processEvent: </atom:summary><link>http://www.targetprocess.com/agileproductblog/2008/10/targetprocess-development-tricks-force.html</link><author>noreply@blogger.com (Oleg Seriaga)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-30774001.post-3316095210101961825</guid><pubDate>Wed, 01 Oct 2008 10:02:00 +0000</pubDate><atom:updated>2008-10-01T12:13:32.860+02:00</atom:updated><title>TargetProcess Development Tricks: Setting the custom context to MS SQL Connection</title><atom:summary type='text'>
We are developing the new audit history mechanism. SQL triggers were added. They do the shadow copy of added/deleted/updated data in important tables such as user story, project. The problem is that we need the custom context in these triggers implementation such as logged user and client date. In other words we need to set some custom info into the connection session before any change.


The </atom:summary><link>http://www.targetprocess.com/agileproductblog/2008/10/targetprocess-development-tricks.html</link><author>noreply@blogger.com (Oleg Seriaga)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>1</thr:total></item></channel></rss>
