Targetprocess v.3.8.5: custom rules for Request closing, Planned Start/End date lanes, Customized card units update | Targetprocess - Visual management software

3 years ago

Targetprocess v.3.8.5: custom rules for Request closing, Planned Start/End date lanes, Customized card units update

Brief summary of this article:

Minor Features

A custom rule for Request closing

We've created custom rules that will close a request once all of its related items (outbound and/or inbound) have been closed. These rules will help to save time and effort, and will minimize the chance that a request unnecessarily remains open after all related work has been completed.  

3.8.5 pic7

Planned Start/End date lanes

We've also introduced the ability to set up views that group user stories, defects and other entities by planned start and planned end dates.  For example, let’s say you want to see which user stories are planned to end next week so you can increase their priority.  To do this, create a view that displays User Stories as cards. Select 'planned end date' as a lane and filter it using your desired date range: ?(It >= '11-Apr-2016' and It <='18-Apr-2016')   

Planned Start/End date lanes

 

Customize cards with 'Entity Type' and 'Planned/Forecast duration' units

Sometimes, it can be difficult to recognize what kind of item a card is through color coding alone.  To remedy this, we have added a new “Entity Type” unit for cards to help you immediately recognize if an item is a User Story, Task, Bug, Request, etc.   

3.8.5 pic5

We've also added units of time for planned and forecasted duration. So, you can now see how long an item is planned or forecasted to take. For example, an entity with a planned start date of April 8th, 2016 and planned end date of August 20th, 2017 will display a planned duration of “1 year, 4 months.” In tooltip, you can see more a more detailed representation of the duration -- e.g., “1 year, 4 months, 3 weeks and 2 days (500 days).”

Customize cards with Entity Type and Planned/Forecast duration units

Relations are shown independently from the specified context now

Previously, Relations were displayed based on the selected projects and teams in the top bar’s context/filter selector. A user had to select "All projects" and "All teams" to see all specified Relations. From now on, you'll be able to see all the available Relations no matter what context is selected. This change affects the Relations tab on entity view and Inbound/Outbound Relation cards.

The ability to map Team workflow to a final Project state only

You might be in a situation where you need a team to start work on an entity only at the final stage of its workflow. For example, when new functionality is ready, the Copywriter Team is assigned to write the relevant User Guide pages. You can now plan this out in Targetprocess by creating a team workflow that's mapped only to the final project state.

3.8.5 pic6

Math functions syntax simplified to work with nullable values

We've simplified the syntax of functions that are used in Reports to work with null data (data with no value assigned to it).
For example, in early versions of Reports, you would have to write the following formula to see requests' lead time in minutes:

IIF(StartDate != null, Math.Round((Today-StartDate.Value).TotalMinutes), -1)

This complex formula would have to be used for those instances when a request is not yet started and its StartDate is null. Now the formula can be written simply:

Math.Round((Today-StartDate).TotalMinutes)

Fixed Bugs

  • Fixed currency display for money fields
  • Fixed quick add form submit by enter key
  • Fixed some layout problems for custom card units
  • Fixed an issue with CKeditor: links did not open in a new window
  • Fixed a problem with creating attachments for Requests from messages sent from a third party tool like ServiceNow
  • Fixed broken search in IE11 after changing entity assignments

You can subscribe to our monthly newsletter here:

Thank you!

Сheck out latest blog posts: