Search by tag

changelog

3 weeks ago

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

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')   

10

 

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).”

new

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
4 weeks ago

Targetprocess v.3.8.4: Requests as lanes, minor bug fixing

Requests as lanes on view

Here at Targetprocess, we manage our requests via relations, and we bind defects or user stories to customer requests as Outbound Relations. In v.3.8.4, we've introduced the ability to select Request entity type as a lane on a Relations Board. For example, you can now set up a list of open requests whose dependencies are completed by using Request as a lane, filtering by lane using '?OutboundRelations.Where(Outbound.EntityState.IsFinal is True) and EntityState.IsFinal is False' and selecting Outbound Relations as the view's cards.
request

From this list, it's easy to understand which requests have been fixed. You can also notify requesters directly about the release version which contains the fix.

 

 Fixed Bugs:

  • Fixed failure to search for project IDs on lists of projects
  • Fixed problem with the possibility to share views/folders with members of any projects/teams (even if user doesn't have access to them)
  • Fixed incorrect selection of the first item in the list of relation popup after selecting any item
  • Fixed issue with an inability to select all projects/teams in the access popup by checking All projects/teams checkbox
  • Fixed problems with styles in a finish iteration view when it is opened in a separate tab
  • Fixed issue with the possibility to allocate an inactive user to a project
  • Fixed the incorrect display of some currencies in follow notifications
  • Fixed extremely high CPU usage when try to open Burn Down for a release with a large number of entities
1 month ago

Targetprocess v.3.8.3: Sorting Order for Comments, Term for Request, New Languages, Workflow Management for Functional Teams

The Order of Comments on Cards

You can now specify the order in which you would like to see comments on cards. From the card description, choose to display either the oldest or newest comments on top. It's a per-user setting, so everyone will be able to set up their own preferred order for following comments.

3.8.3 pic1

Custom Term for Request

From now on, it is possible to rename 'Request' with our Terms editor in the same way as other entities. For example, you can rename 'Request' to 'Requirement' and collect requirements that come from your clients throughout the project.

3.8.3 pic4

New Languages added to Targetprocess: French, Spanish, Portuguese (the Brazilian variety)

Targetprocess can now be used in 6 different languages: English, German, French, Spanish, Portuguese (the Brazilian variety) and Russian. Translations in all these languages have been completed. English still remains the main language of the system, and the administrator's user interface is not supposed to be translated for now. Every user can switch to one of the new languages via My profile - Account Settings. Read more

3.8.3 pic3

Workflow Management for Functional Teams publicly available

We have finished the Beta testing of our new feature and are proud to announce that Workflow Management for Functional Teams is now publicly available. The new functionality will be useful for companies who have teams working sequentially. Accounting, Marketing, Designers and Development are examples of such teams; they are often called functional teams. From now on, several teams can work on the same item – e.g. a feature or a user story – one after another. So, the final state of an item in the workflow of one team is its first state in the workflow for another team. Read more

Functional-Teams

 

Minor Features:

  • Filtering by entity-specific fields when several card types are selected at the same time

 Fixed Bugs:

  • Fixed export failure when last commented user name is not specified
  • Fixed saved context override by global context
  • Fixed failure with renaming tags if they have a long name
  • Fixed issues with import for Bugzilla plugin
  • Fixed problem with allowing prioritization in lists with the configuration when prioritization should not be allowed
  • Fixed sorting in lists for some units when more than one card type is selected on setup
  • Fixed problem with filtering projects by anticipated end date
  • Fixed problem with the possibility to create allocations beyond the project end date
  • Fixed incorrect handling of unsupported expressions in visual filters
  • Fixed filtering users by custom fields using api/v1
1 month ago

Targetprocess v.3.8.2: Custom Fields for Programs, Allocations in a Project View

Minor Improvements

 Custom Fields for Programs

You can now organize your project portfolio by categories. You might have your working Projects grouped into Programs. Now, by means of custom fields for Programs, you can categorize them by type, value driver or prioritization criteria. For example, we have several programs with multiple projects and our Programs are categorized by business direction: Finance, R&D, Finance, etc.

portfolio program CFs

Allocations improved

  • Allocations tab added to a Project view

projects allocations

  • Anticipated Date info displays on mouse hover over the Name along with the all allocation line
  • Anticipated/Forecasted End Dates added on a Project view

Custom Business Rule: when a User Story is assigned to a Team all its tasks and bugs are assigned as well

custom rule assign tasks and bugs

 

Fixed bugs

  • Web Hooks can  access custom fields by name
  • Fixed: sorting axes by custom fields in a List view
  • Fixed: color coding for bugs and tasks on a Flow Tab
  • Fixed: copy default values of custom fields if Process is cloned, calculated custom fields cloning fixed.
  • Fixed: 'show more' in a Backlog column, filtering by 'Backlog', i.e. ?TeamIteration is ‘Backlog’
  • Disable ability to change Project field for Tasks
  • Fixed: display of a 'Money' custom field in Follow email notifications.
  • Fixed: redirect to a v.3 if logging is performed from the Targetprocess website targetprocess.com/login
  • Fixed: Null Reference exception if required NumericPriority field is not set
  • Fixed: alignment of programs and project names in a Project/Team selector
  • Fixed: "UserStory should be specified" error on a try to add a Task to a User Story - Effort cell
  • Fixed: lookup filters layout for the case when no entities are available
  • Fixed: sorting order for Roles to work by name not by ID in all selectors
  • Fixed: 'Invalid slice definition' exception when a board with deleted project context is open
  • Fixed: ability to change a Project for a Bug that is created during Test Plan Run execution
  • Fixed: 4-digit numbers display in a 'Time Spent' custom unit
  • Fixed: performance of a List view with calculated custom fields
  • Fixed: export of Test Step with a multiline description
  • Fixed: performance of a quick add [+] from an entity view
Get started for free

Sync up your teams with a visual project management tool that adapts to your organization and gives you transparency across different projects and departments. Visualize every step of the way.

Get started