Targetprocess 3.7.1: Better Relations and Usability

This release contains several usability and functionality improvements.

Relations as cards on a view

In previous releases it was very difficult to create Views with relations, and many times it was impossible to see all the relations at once because it's not possible to choose cards of different types, like Features and Projects, at the same time.

Now you can use inbound or outbound relations as cards on a view. In the example below, we've selected Features as lanes and inbound relations for cards.  We can easily see all the inbound relations for our Features, regardless of the type of the related card:

Planned Start/End dates for Projects

Previously a Project could only have actual start and end dates, it was not possible to compare a planned start date with the real start date. We've unified this and now you can set the Planned Start Date and the Planned End Date for any Project.

Collections in Calculated Custom Fields

Calculated custom fields were introduced last month, but it was not possible to use collections in calculations. For example, you have a User Story with several Bugs and you want to see how much effort is required for the related Bugs. Now you can create "Total Bugs Effort" custom field for User Story and use formula:

Bugs.Sum(Effort)

Or you can calculate effort of all related entities. Let's say, you have a feature in some project and you link other features from other projects to this feature.

InboundAssignables.Sum(Effort)

With this release all available resource collections are now supported. To learn more about collections, check the resource description.

Allow to copy text by double-clicking on description

For years you were able to edit an entity description by clicking on it. However, it complicated selecting text and copying it. So, we decided to add an Edit button. You might have to re-learn some old usage patterns, but it seems this solution is better:

Ability to assign Requests to a team via the POP plugin

You can now assign Requests to teams by using rule similar to:

then assign to team 1234

or

then create private request in project projectID and attach request to team teamID

Save images in WYSIWYG as Attachments

When you insert an image into the WYSIWYG editor it is now added as an attachment. This solves a security issue with static files and unifies how images are stored in Targetprocess.

Fixes

• It should be difficult to accidentally delete test case
• WYSIWYG Editor: when pasting image it is always added to the top of a description or comment
• Dashboards: Unable to change the name of widgets in Safari
• Security: XSS vulnerability in the filter bar
• Lists: Allow to move User Stories between Features in Epic/Feature configuration
• Time zone issue for Milestones
• Unable to attach a Revision to an Assignable when it is created via the REST API
• Custom Reports based on history show entities from other process
• Attachments have the name "undefined" when an image is pasted from the clipboard