You have Budget, Expenses fields for Project and want to calculate your projects Profit? Want to compare the actual effort spent to the initial estimates? Have to compute the costs of a feature or story development?
In v.3.6.6 we introduce an elementary calculations of custom fields. Now you can create your own formula-based calculated custom fields. Use the built in properties for an item or even other custom fields that are a number, text, date or check box type.
For example, you have a custom field “Complexity” of a drop-down type with values “Low”/”Average”/”High”. Basing on a feature complexity you may calculate the costs of its implementation. Then you should add a calculated custom field “Cost” where the formula would be:
Apart from Calculated Custom fields, two more enhancements have been added
Cross-process Custom Fields for Projects
In the past when you wanted to change a custom field for all projects, you had to update the custom field in each Process separately. Now you can create a cross-process custom field for the Project entity. When you add a custom field for the Project entity, you can now choose the related processes. In this case, all the projects which run selected processes will use the same custom field, and you can edit it for all the projects in one place.
Money Custom Field
Also a new type for custom field has been added, Money, which handles a currency type. You might want using it for storing monetary values.
Fixed Test Plan/Case prioritization from the Test Plan view
Fixed card duplication on One-by-One view mode if board is configured with a many-to-many axis
Fixed quick add for the Team State axis if team states were reordered (for non-admin users)
Fixed a broken loader from the Create Run button on a Test Plan view
Before this release when you would type a comment and then accidentally close the view, the comment was lost. From v.3.6.5 if you write a comment, then switch to another view without saving it, the comment will be restored when you go back to it.
Export to .csv from a board now takes into account filters, paging and focus
With this release we’ve enhanced the export to a .csv from a board. Now if you have your board filtered or focused on a particular set of rows and columns and then export it, you will see the same set of cards in the csv file as the board shows. Another improvement is if you have a really large board spanning several pages, then all the cards across all the pages will be exported. By default, the number of exported entities is limited to 1000, but this can be changed in Web.config file. You will need to modify this line: <add key=”CsvSlice.TakeLimit” value=”1000″ />
‘Convert to Project’ and ‘Create Related Project’ actions added for Requests
Now you can create a new project directly from a request instead of just a feature, user story or bug, because it is what it is, a project. Alternatively request could be converted to a project.
Markdown as an option for the Description editor (per account only)
Starting from v.3.6.5 Markdown lovers and early adopters can switch the Description editor to work with Markdown for the whole account. Administrators can switch the default editor for new entities from the Settings Gear > Settings > General Settings > Editor Settings.
When this is enabled for any new descriptions, except for requests, you’ll write in plain text that will be converted to HTML. The Description of all old entities and requests will still use CK editor.
Currently we support basic Markdown and drag-and-drop images to the Description. Please, refer to the GitHub Markdown Guide for examples to see how easy-to-use this plain text editor.
We are working on enhancements to this and adding Markdown for Comments which will be released later.
Relations: Project added to the entity lookup
Sync interval for the Git Plugin is changeable now
Fixed the Time scale scroll for a Build Date
An Observer cannot access the History tab of an entity view
Restrict users from setting a Test Case Run status if they do not have Test Plan Run edit permissions
Fixed Test Cases/ Plans prioritization in a List mode view after dropping them from another hierarchy level
Reset an entity state to initial after ‘Copy’ action
Forbid to assign several teams to Assignable
Fixed Requesters count that increases while moving Request card through Requester axis
Fixed view sharing when the limit of public views is exceeded according to license
Fixed saving a filter for the ‘Created Date’ axis
When a Feature is copied to a Project the Epic field isn’t copied
Optimize context related requests for an entity view when opened from a Board
Starting from v.3.6.3 all Views in a Group will always have the same access permissions.
If you change the permissions of a Group it will automatically be applied to any Boards, Lists, Timelines, Reports and Dashboards that are part of this Group. With this update you no longer have to modify the permissions for each View in a Group individually. As a result, when a View is part of a Group you cannot change the access permissions of a specific view, this will always be inherited from the Group.
Improved performance of Request view and Relations
Fixed Visual Studio plugin memory leak
Team State doesn’t show in State selector if there are no subsequent Team States available
View access setup: Disable “Send notification” button after sending an access change notification
Start Date isn’t set when progress is started by moving an entity to a Team State
Cannot add Test Plan Run if Test Cases practice is not enabled in the default process
Fixed Test Run Import plugins to work with new test run statuses
We keep moving towards a possibility to do single-step changes of all the Views inside a Group.
Group owner becomes an owner of all Views inside
Starting from this version, all Group owners are added to their Views owners list as well. Now if you see any person as a Group owner, you definitely know that he could change any View in this Group. Therefore from now all the private Views departed their public and custom shared Groups.
View access changes when moves to the Group
In v.3.6.2 when you move an existing View to a Group with a different access you are warned that View will change its access permissions in order to match its Group settings.
Drag and drop in the List View is more useful — you can start moving item to a collapsed node, the necessary one will expand on the spot
Team workflow improvement
It wasn’t possible to edit team states in a team workflow as soon as they are created. From now you don’t need to re-create the whole team workflow when you need to modify it. You can easily change a state name or simply remove a state from a team workflow.
Add relations to Epic
Finally the new entity type appears in Add Relation lookup similar to other entities.
Fixed layout of a board with collapsed rows if Test Plan selected as horizontal lane
Fixed Burn Down Chart that displayed info in points for processes in hours
Fixed error “Sequence contains more than one matching element” when new Team Workflow added
Fixed exceptions when Tasks transfer to next states and their stories are in Planned state and “Developer” role doesn’t exist
Card doesn’t show immediately in its new cell if prioritize with <Shift>
Custom report fails to load if filter by date applied and application culture is not the en-US
Fixed search by test cases failure if there is a match in test steps
Fixed Dashboard charts that showed only one Date bar
Fixed “Something weird happened” when assign User Story or Bug to Epic from a Board view
Fixed history for Team Iterations
Fixed improper order if the same card is prioritized several times in a row
Fixed left menu to hide/show Views properly when their access level changed from public to custom
Drag and drop items between levels
You can move items between different levels in hierarchical lists: User Story to Feature, Feature to Release, etc.
Lookup for linking entities added to inner lists.
Often you want to attach existing Bug to User Story you’re working at the moment. So now you can find it quickly and assign Bugs to User Stories, or Features to Epics right from the view via entity lookup
#84602 Customize Cards: Add unit ‘Open/total bugs’ for Feature
#98190 Left Menu Improvements: Add tooltips for long view and group names
#77526 Run Estimate Field Calculations on a Test Plan View
#98369 Plugins: Update Mylyn connector to work with DB of v.3.5.5
#95375 Show local time in comments
#62763 Removed messages duplication in a Quick Add
#97674 Cannot set value in a long drop-down custom field if screen resolution is 1920×1200
#95793 Fixed comet failures while processing notifications on comment update
#97690 All test steps changes will be reverted if user doesn’t have permissions on Test Case/Test Plan Run edit #97712 Improved performance of a Quick Add in Relations tab of the view
#97878 Fixed Team names duplication in ‘Used by’ form when one team use the same workflow in different projects
#98222 Team permissions are not applied to list of tests on Test Plan view
#98371 Fixed test steps / test step runs layout when description or expected results contain long links
#98409 Fixed resource comet: states were not updated
#98451 Add spent/remaining time from the list should be disable for Epics and Features
#98471 Fixed: non-admin user cannot modify new Custom Report description
#98658 Fixed failing first login page for admin
This major release focuses on better information visualization and insights. With Dashboards and Custom Graphical Reports you have a powerful tools to see deeper and understand more about projects, team, work and plans.
Please, give us feedback about these features. We are going to improve them in the next couple of months based on your real needs.
Custom Graphical Reports
Reports should be used to see aggregated data and progress over time. So far you can create line charts, bar charts and scatterplots. Facets are supported as well, so you can group information by various categories and compare projects, teams, features, see trends in cycle time, quality and many other areas.
For example, the report below shows user stories (circles) for every team and for the last four months. Each small chart shows Effort vs. Cycle Time correlation. You see what teams create larger user stories, what team completes stories faster, what team has less consistent estimates.
Reports are really flexible, check documentation to create your own report:
Dashboards help to aggregate information from various sources and show it in a single place. In Targetprocess you can create as many dashboards as you want: for a single team, for QA, for development tracking, etc. Explore some use cases.
The freezing possibility allows to keep test run results unchanged forever. Now you can easily re-use existing test cases and test plans for testing a newer version of your software, even if it requires some modifications, and not to worry about loosing the historical information. Read more about test runs results freezing.
QA Area enhancements
We’ve made a lot of small improvements on test plan and test plan run views. We believe they will make it easier to work with test cases and test plans, execute them and see run results.
Now on a test plan view you can see a new list of test plan runs, from where you can quickly start a test plan run execution. There is a new section on the right, where you can create a new test plan run with just a single click and see how many open test plan runs there are right now.
On a test plan run view you can see a similar section on the right and quickly start or continue a test plan run execution. There is also a number of open and total bugs in this test plan run and current run results. A new Start/End Date unit has been added for test case runs and test plan runs, so now you can see when an execution was started and whether it’s already completed.
Audit history is now available for a test case run, so it’s easy now to see who made changes in it.
Left menu changes
We’ve accumulated feedback about left menu problems and are fixing them now. Some improvements included into this release.
Only owner/admin can change groups/views order
Previously anyone could change order of Groups and Views in the left menu. It lead to confusion since many users had different ordering and it was impossible to create a solid structure of company wide Groups. Now only Admin can freely change order of public Groups and Views. Non-admin users can still re-order their private Groups and Views.
NOTE: Order of Groups in your left menu will change with this update as a side effect of this change.
Action: Delete Group with all its Views
Sometime you want to delete a Group with all Views inside this Group. Now you have an action that does exactly that. Use with care:
List improvements: Inline edit for Team, Project and Custom Fields
In this release you can edit more fields in Lists. Team, Project and some types of Custom Fields (Date, Drop Down, Text and Number) are editable now.
Requester entity in Views and Lists
Now you can create lists and boards that display Requesters entities.
Customize cards: added ‘Initial estimate’ unit for Features.
#97114 Fixed posting decimal time records for cultures other than en-EN
#96236 Prohibit from creating custom fields which names start from a number
#93675 Test Cases / Test Case Runs View layout is broken when there’s not enough space
#93533 Unexpected View opens after another one removed
#96546 Duplicated processes appear in custom reports if non-admin is both a Project member and a Team member
#97518 Improved performance of the view related to proper processes and custom fields selection
#97925 ‘Time spent/remaining’ unit fixed to fit the M-size cards
#97271 Fixed the link to the entity if it was added from the List view
#84510 Fixed Team/Project selector in the quick add form on Relations tab of the entity view
Team workflows may become very useful when there are multiple teams working on the same projects (or projects which use the same process) and teams prefer their own way to work on items. Starting from now teams can run entities, like user stories, bugs and others, through the states that may differ from the states in a common project workflow. This allows teams to follow their real life workflows, and help project managers easily track the progress across all the teams not without being confused about each team’s specific workflow. Read more about Team Workflow feature.
QA area improvements
We’ve added a related Bugs list to a Test Plan Run view. Now you can see what bugs are related to all the test case runs in this test plan run in one place.
When look at a Bug view, you can similarly see what test case runs this bug has affected:
We’ve also replaced a list of test case runs on a test case view. Now you can clearly see which test plan runs a test case has been executed in, what were the run results and when it has been done.
Allow users to choose TP3 or TP2 to be loaded on entry
A new option added especially for our long standing customers, who have a mixed v.2/v.3 licenses. Now you can go to Personal Settings and choose the version, which you want to see by default after logging in.
Now if I have this checkbox in my settings on and follow the link https://mytargetprocess.com/ then I’ll get to Targetprocess v.3. If the box is unchecked, I’ll see Targetprocess v.2 as before
Show date and time of attachments
Mashups that affect the application performance will be listed in the diagnostics report
Requester as a view lane: now it’s possible to create a board or a list view of Requests grouped by Requester
Bugzilla comment is truncated if it contains a special sequence of symbols
Follow email: smart new line
‘Entity Not Found’ screen overlaps the other pop-ups from the top menu
Improved performance of a bug Duplicates
Unable to delete workflow state
Fixed: fail to rename Process State in Safari on a MAC
Replaced TP to TR in the Open/Total Test Plan Run unit
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
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
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