Targetprocess 3.5.5: Team Workflow

Team Workflow

Team workflows may become very useful when there are multiple teams working on the same projects (or projects which use the same process) and teams prefer their own way to work on items. Starting from now teams can run entities, like user stories, bugs and others, through the states that may differ from the states in a common project workflow. This allows teams to follow their real life workflows, and help project managers easily track the progress across all the teams not without being confused about each team’s specific workflow. Read more about Team Workflow feature.

QA area improvements

We've added a related Bugs list to a Test Plan Run view. Now you can see what bugs are related to all the test case runs in this test plan run in one place.

When look at a Bug view, you can similarly see what test case runs this bug has affected:

Allow users to choose TP3 or TP2 to be loaded on entry

A new option added especially for our long standing customers, who have a mixed v.2/v.3 licenses. Now you can go to Personal Settings and choose the version, which you want to see by default after logging in.

Now if I have this checkbox in my settings on and follow the link https://mytargetprocess.com/ then I'll get to Targetprocess v.3. If the box is unchecked, I'll see Targetprocess v.2 as before

Minor Features

• Show date and time of attachments
• Mashups that affect the application performance will be listed in the diagnostics report
• Requester as a view lane: now it's possible to create a board or a list view of Requests grouped by Requester

Fixed Bugs

• Bugzilla comment is truncated if it contains a special sequence of symbols
• Follow email: smart new line
• 'Entity Not Found' screen overlaps the other pop-ups from the top menu
• Improved performance of a bug Duplicates
• Unable to delete workflow state
• Fixed: fail to rename Process State in Safari on a MAC
• Replaced TP to TR in the Open/Total Test Plan Run unit