If you work on product that include several components or application that are being developed in a multiple teams in parallel, synchronize their releases in time and ship under one new version, you might be interested in a single Release for planning and tracking.
Starting from 3.5.4 you can create a shared Release that will allow you to plan work from different projects under the one Release and track the progress within one Burn Down Chart! Read more in a detailed feature guide
Outgoing Web Hooks Plugin
Outgoing web hook plugin allows you to listen to triggers in Targetprocess entities, which will then send relevant data to external URL in real-time. With this plugin you can integrate Targetprocess with third-party services:
For example, we did it with Slack communication platform. Read the instructions here
#82925 Assigned feature resets when converting Bug to Story and vice versa
#96105 Inability to unassign Team from Project – “Too many parameters were provided in this RPC request”
#91797 Error “UserFirstName UserLastName is already allocated to the Scrum project”
#95068 Fail to update Initial Estimate for Features and Epics and Velocity for Iterations
#95168 Restore the “Show Weekends” option state in burn down charts
#95342 Custom field value is not saved when new entity is added via SOAP API
#84433 I can’t move a user to “No Team” cell while he’s assigned to any other team
#82217 Inadequate pull-down filters length in the entity lookup
Custom Business Rules
Starting from this release you can extend the default business rules and Targetprocess will automatically do some additional actions that you’ll choose. For example, now if you assign any Bug to User Story, the defect might be auto-assigned to a User Story’s Feature. You can find all the new rules list in the ‘Settings > Custom Rules (NEW!)’ below the ‘Settings > Processes’ item, available for admin users.
Read more about Custom Rules in the new blog post!
QA Area: New On Hold run result and a possibility to skip test cases naturally
A new On Hold run result is introduced for test case runs. The skip action can still be performed by clicking the Next Test Case button, which is active always now and can be clicked any moment of time even with no run result selected.
QA Area: Show a Tester in the Test Runs list on a Test Plan Run view
When a test case is started being executed, i.e. if a test step in it is marked as passed/failed or a test case run result is specified, we can see now who is executing a test case run. This allows to avoid many people working on the same test case run simultaneously.
#93839 QA Area: ‘Run date’ unit in the Test Runs list
#93654 QA Area: fixed long Test Case Run names display
#92146 QA Area: Test Plan Run counts are not updated when inner Test Plan Runs are deleted
#94282 QA Area: fixed “You can’t do that” error when move Test Plan card from clipboard to test plan lane
#67318 Fixed error message in board view by User if a new entity is added and its project is not selected.
#69089 Project, Team views: unable to correct and add a new team (or a project) if a duplicate team name has been added before
#93435 Fixed all “You can’t do that” error messages
#94466 Fixed shortened list of Projects in the entity lookup filter in the Relations tab
#94554 Fixed limitation of teams list in a Project view
#92780 Fixed annoying message on reconnect
Test Case Runs and Bugs Relations
The newly introduced test case run and bug relation feature adds the ability to create bugs related to a test case that is currently being executed. As a result, you can track how many issues have been found during the execution of the whole test plan run.
To add a bug related to a test case run, simply click the Create Bug button on a test case run view, give the bug a name and click the Add or Add & Open button.
A new bug will be created and linked to the current test case run automatically.
All the bugs related to a test case run are shown on the bugs tab of a test case run view.
Here you can see and update bugs details such as business value, severity and also assign bugs to people so they can be fixed.
If you’ve found a bug which already exists in the system, you can simply link it to the current test case run using the lookup window. This way bugs are not duplicated and we can specify how many test case runs a bug has affected.
The ability to link existing bugs provides a great way to track how many rounds of testing a bug was not fixed, as you can simply link the same bugs to different executions of the same test case or a test plan.
In case a bug has been created by mistake or it should not be linked to a test case run, it can be unlinked. Right click to open the context menu and unlink it from the test case run.
With the Open/Total Bugs unit added to the test plan/case list it’s quite easy to get an idea on how many bugs have been found and how many still need to be fixed during the current test plan run execution.
The same unit can be added to test plan run cards on a board, list and timeline view modes.
QA Area: Unlink a Test Plan from a parent Test Plans
To see how many test plans the current test plan is included to, we’ve recently introduced the Test Plans tab on a test plan view. It’s useful to look at this tab when you plan to update the current test plan to know how many test plans will be affected by your changes.
In this release we’ve added the possibility to quickly unlink the current test plan from its parent test plans. Simply right click on a parent test plan and select unlink.
List: Counters showing the number of entities at the very last inner lever
The counters in lists now show the number of entities at the last inner level instead of showing the number of entities on the next level. As an example, this allows you to see how many bugs and user stories are in every state, even if they are grouped by project or any other property.
#93913 QA Area: Fixed Test Plan Run card customization mode
#86816 QA Area: Fixed an error ” Oops… Something’s wrong” thrown in Test Step editor
#93094 QA Area: Fixed “Data layer exception occurred” when deleting Test Case in TP2
Filter User Stories and Bugs by Feature
When you have a board that shows User Stories and Bugs at the same time, you can filter them by Feature now. So you can create a board that shows everything related to a specific Feature.
QA Area: Test Plans tab on a Test Case and a Test Plan views
As you know a test case or a test plan can be linked to many different test plans. On a Test Plans tab you can find what exactly test plans the current test case/plan is linked to. It can be very useful when you decide to update a test case/plan and need to know what test plans would be affected by this change.You can also unlink a test case/plan from the test plans it’s linked to straight from this tab.
QA Area: The Skipped test case run result has been renamed to On Hold
The Skipped test case run result has been renamed to On Hold. Now you can mark a test case run, which can’t be executed right now, as On Hold and return to it later. You can also skip a test case run. To do that just open the next test case run.
#92980 Mylyn connector to work with Targetprocess later than v.3.4.3
#93457 Support <table> in comments
#92046 Batch move requests get stuck when test cases move between test plans with test plan runs
#92274 “You are using the in-browser JSX transformer” warning in Firefox v.33
#92911 Search doesn’t work after changing assignments
#93283 Mention is not emailed, if there is a deleted user with the same email address
This release summarises some changes in recent minor builds and includes hierarchical Test Plans functionality, which makes QA area in Targetprocess much more powerful.
Hierarchical Test Plans
Now you can organize test cases in a test plan into groups (lower level test plans) based on many different parameters, such as – only to name a few – different types of testing (smoke and regression tests, for example), test case priority to specify which groups need to be executed first and which last, or by user story (thus creating a user story test plan) to see which user story every single test belongs to during execution. Read more about better QA area.
Start Date/End Date could be before Creation Date now
There are cases when you have to set Start Date before entity Creation Date. For example, you exported some features from CSV and Create Date was set as Today. However, some features have been already started, so you can’t set correct Start Date. However, Lead Time can’t be calculated correctly in this case, so there is an icon that indicates that:
“No Project” option removed
Previously it was possible to assign work to No Project. It complicated some internal implementation and we decided to remove this possibility. We are working on Team Workflow functionality and No project option doesn’t fit it. All work that was not assigned to any project has been moved to new artificial project called ‘No Project’.
Easier Workflow Setup
New Workflow solves several usability problems, provides clear and visual Workflow manipulation functionality and saves your time. Read more about this new functionality.
- #92772 Fail to reconnect after connection lost
- #89595 Selected Test Cases vanished when drag-n-drop them to Test Plans board from the clipboard.
- #77724 Exception “Field ‘Color’ is not available” when user assigns team to any project while the team is assigned to any inactive projects.
- #85658 Saved context for board should be updated if only ‘Set’ button is pressed.
Easier and faster Workflow Setup
We’ve redesigned Workflow setup. It solves several usability problems, provides clear and visual Workflow manipulation functionality and saves your time.
Read more about the feature, play with it and share your feedback.
#91319 Fixed: ‘?Iteration.IsNext is True’ (‘ .IsNow is True’ and ‘ .IsPrevious is True’)
#91486 Fixed: assignments reset when new state is added to workflow (for default process only)
#90950 Fixed: Eclipse/Mylyn connector fails if there’s an Epic in ToDo list
#91758 Fixed: Mention doesn’t work when using popup in new lists.
Now you can find a test case ID shown next to a test case run ID on a test plan run view, so that you can quickly move to the related test case if required when executing a test case run.
90633 Fixed: Import test cases to different project
91210 Fixed: Incorrect counters if Test Plan Run is completed from Targetprocess v.2
QA Area: Show Test Case attachments on a Test Case Run view
Test Case attachments are now visible when you execute Test Plan Runs. You can easily open files and screenshots you have attached earlier. It is also possible to attach more files while executing a Test Case Run. The files will be automatically linked to the related Test Case.
Now following is available for Epics, too. You can receive email notifications if new comments and attachments appear, if new Features are assigned or removed from the Epic, etc.
#88177 Effort units in Test Plans (pt or h)
#79932 ‘Show more’ is hidden on hover if its cell is collapsed
#87751 Link underlining in Chrome is corrected
#87941 Missing icon in ‘Open/Total User Stories’ unit
#89300 List mode: JS error while adding user stories to the new Feature view
#89629 Can’t open Burn Down from the list view
#89961 ‘Diff’ view pop-up was incorrectly placed
#90309 Top filter on the board shrinks for screens with horizontal resolution < 800px
This release includes two major additions.
Epic is an entity above Feature. Quite often you want to have one more level of hierarchy for requirements, and Epic can be handy. For example, you have large module and several features inside this module. Or you have large feature and break it down to smaller, like Minimal Viable Feature and Minimal Marketable Feature.
Follow entities and receive email notifications about changes. For example, you may follow a Feature and receive notifications about its effort changes, new comments, new attachments, added/removed User Stories or their states changes, etc.
Read more about these two features and share your feedback!
WYSIWYG editor in Test Steps
WYSIWYG editor is introduced in Test Steps. Now you can apply different text styles like bold and italic, change text colour, use bulleted and numbered lists, add links and images with ease in test steps descriptions and expected results.
Minor fixes and improvements
#87668 Test Case: wrong Last Run Date sets if server runs with a specific date formats (DD.MM.YYYY instead of MM.DD.YYYY)
#81700 Email Notification: include internal images in comments to outgoing emails
This release includes two more features: Epics and Follow Entity. They are in beta mode and can be enabled for some servers.