Targetprocess v.3.11.3: User Stories will now follow their parent Feature

User stories will now follow their parent Feature

Previously, if you moved a Feature to another Project, its User Stories did not follow the Feature to the new Project. This was fairly counter-intuitive. Starting with this release, if you move a Feature to a different Project, all of its User Stories will follow (as long as they were originally in the same Project as their parent Feature).

If you move a Feature to a Project with a different process, you will get a warning that this change might cause you to lose some custom fields.

Private Impediments have been removed

As described in this blogpost, we're removing this barely-used feature to improve performance and reduce complexity. Feel free to message our support team if you have any questions.

Fixed Bugs

• Corrected the @user mention format for email notifications
• Fixed the creation of a Test Plan with multiple Test Cases via REST API POST
• The order of mandatory custom fields in Quick Add forms will now correspond to their order in entity views
• Fixed a case where it was not possible unlink a Bug from a Test Case Run if its Test Plan Run is the child of another Test Plan Run
• Improved the performance of Relations lookup
• Fixed an incorrect term: When completing Team Iterations, the system would incorrectly describe them as Iterations.