Targetprocess Product Blog

Agile development on a real project (we do Kanban)

changelog

Targetprocess 3.7.4: Private Projects, Epic Conversion

Private Projects

Starting from v.3.7.4 you can mark a Project as private. A private Project will only be visible to users who are members of the Project Team, if the user is the Project Owner or if the user is part of a Team assigned to the Project.  These projects will be hidden from everyone else, even administrators and observers.

private projects

Epics Improvements

‘Convert’ action for Epics

Now you can convert an Epic to a Feature, User Story or Request. You can also convert a Feature, User Story or Request to an Epic.

convert epic

In addition to converting, we’ve also added the possibility to assign Epics to Releases and display the History of an Epic.

EpIc history and Release

 

Minor changes and features

  • Graphical Reports: Iteration/Release/Team Iteration/Build sort order is now by ‘Start Date’
  • Graphical Reports: Facet charts with categorical axis should exclude empty categories
  • Search Results now display in a full size view

Fixed Bugs

  • Fixed: Time Sheet does not show entities with time records for a user that is assigned only via a Team
  • Fixed: Newly added Team from Projects/Teams menu could not be added to current context w/o reload
  • Fixed: Calculation of Effort ToDo for a person’s capacity when the Iteration has already started
  • Fixed: User Story quick add on a view with Sprint / Epic lanes
  • Fixed: Card details that appear on hover were hidden by the Left menu
  • Fixed: Completed cards by Team State didn’t appear on a view (Responsible Team was not set yet)

 

Targetprocess 3.7.3: Epic unit for Bug/Story cards, new DateTime functions in Webhook plugin

Webhook plugin supports new DateTime functions

AddDays(DateTime date, int days) – Returns a new date with the number of days added. The number of days can be positive or negative.
Example: {{CreateDate | AddDays: 7}}

Now() - Returns the server’s current date and time.
Example: {{Now}}

LastSunday(DateTime date) – Returns the closest start of the week (last Sunday) for a given date.
Example: {{StartDate | LastSunday}}

Epic unit added to Story and Bug cards

We’ve added a new ‘Epic’ unit on User Stories and Bugs. Since a Bug or User Story cannot be related directly to an Epic, this unit will show the Epic for the Feature that a Story or Bug is related to. This also means that the Epic unit for Stories and Bugs is read-only when in the list mode.

epic unit

Fixed Bugs

Fixed: Verification of the project/team abbreviation length from an entity view
Fixed: Text in brackets ‘<>’ is not processed correctly
Fixed: `TypeError: e is null` on a View change
Fixed: REST API cannot get a specific custom field for Time
Fixed: “Object reference not set” exception on a Timeline if Visual Encoding by a custom field was applied
Fixed: “Responsible Team” is missing when in List mode
Fixed: Timeline exception when an invalid date range is selected and the Milestones feature is “On”
Fixed: Description is not auto saved correctly with a long description and poor internet connection
Fixed: Board “Owners” from left menu disappears if an owner was deleted from Targetprocess
Fixed: Date units in filters should be case-insensitive
Fixed: Broken “?TeamIteration is current” filter
Fixed: Warning message about slow mashups is not displayed in no mashups mode, delay to display increased from 10 to 20 seconds
Fixed: Unable to edit entity description if the Entity Template mashup is installed
Fixed: Authentication of SVN plugin to Visual SVN Server 3.3.1 errors processing

Targetprocess 3.7.2: Project Statuses, Sorting by Custom Field, Find Bug Duplicate

Project States, Lead and Cycle Time

Many times projects need go through different phases.  Starting with this release you can track and visualize the status of a project using Project States and Project Lead/Cycle Time reports.

Project states can be added by admin user from Process Setup > Workflows.

Project States

Having project states allows us to calculate the lead and cycle time, which will appear on the project view.

project cycle time

Duplicate Bugs in v.3

For those of you who have used v.2, you know there was a Duplicate Bugs feature.  We’ve taken this feature and reworked it, to bring this functionality into v.3.

You can add a bug duplicate from the ‘Actions’ menu of the Bug view.  This can also be done from the Bug Duplicates section, which is right below the bug state.

bug duplicate tp3

 

The mechanism differs a little bit from Targetprocess v.2 as it based on Relations. We’ve introduced a new type of Relation called ‘Duplicate’.  When on a bug view and you select any other bug to be added as a duplicate, it will appear in the Outbound Relations section.

We decided to use Relations as it will help for creating boards/lists of duplicated entities and merge these items into one ticket. Merging duplicates (bugs and request) is in development now and will go live in v.3.7.4.

Sort cards by custom fields

The long awaited functionality of being able to sort cards by custom fields is now supported.

Starting from v.3.7.2 can order lists or cards on a board by a custom field!

cf sorting

Fixed Bugs

#101153 Fixed: incorrect and failures for graphical reports when a division by zero occurred

#103039 Fixed: extra line breaks when hyperlinks are added via Markdown editor

#102567 Fixed: exception in case a rule ‘?Owner is Me’ used for Visual Encoding

#103347 Fixed: exception on Timeline when Visual Encoding rule is applied and a horizontal lane is selected

#103491 Fixed: Saved filter with double quotes are restored incorrectly

#101627 Timeline: show entity name on the smallest zoom level

Targetprocess 3.7.0: Milestones and Entity Test Plans

Milestones

Since the world is so dynamic, we have to be on time with our projects to be successful. Starting from the v.3.7.0 you can now visualize important milestones on a timeline view. Simply add a new milestone and specify what projects it relates to. Now you can track whether your progress is effective enough to complete work on time.

Milestones

To see all milestones in one place, you can use the ‘Milestones’ widget on a Dashboard.

Milestones Widget

You can find more details about Milestones in the Targetprocess Guide.

Entity Test Plan

Imagine you have a bug, which you need to test. With the new Entity Test Plan functionality you can create a bug test plan and easily add new test cases or link existing ones to it with just a few clicks. When it’s time to test a user story, which this bug relates to,  you can create a user story test plan and automatically link any related bugs’ and tasks’ test plans to it. Link several more existing test cases or plans, which have to be executed during any user story testing, and you are ready to go. Now you can execute this user story test plan as many times as you need and keep all the run results.

Milestones

Later when it’s time to test the whole release, you just create a release test plan and include all the user stories test plans into it with just one click.

Milestones Widget

It is possible create a test plan for any of the following entities and operate with them in a similar way as you currently do with an independent test plan:

  • Epic
  • Feature
  • User Story
  • Task
  • Bug
  • Request
  • Build
  • Release
  • Iteration
  • Team Iteration

As a result, your test cases and test plans can be beautifully structured according to your entities hierarchy and easily managed.

Structure

More details are available in the Targetprocess Guide.

Copy Test Case Run Details to a Bug Description

When you create a bug from a test case run, now test case run details are automatically copied to the description of the bug, so you can easily see what are the steps to reproduce and where exactly the bug has been found:

Milestones

Responsible Team axis

Before this release you could create a view with a Team axis that showed all the cards that are assigned to different teams. If you’ve started using the team workflow feature and have different team workflows created, this didn’t really help to see what cards the team is currently responsible for.

From v.3.7.0 you can now create a view that will show all the items assigned to the team that they are responsible for, based on their team workflow. For example, if a story is assigned to a team and it is in a project state that is mapped to a team state for this team, then it will be shown in the team’s lane.  When it gets to a state in the project workflow that is not mapped to a team state it will no longer be shown in this teams lane, as they are no longer responsible for it. Instead, it will appear under the heading No Responsible Team, since there is a team assigned but no related team state.

For now views using the Responsible Team axis are read-only.  This means you will not be able to move cards between responsible teams or use quick add on this view.

‘Share link’

The URL is now automatically copied to the system clipboard.
share link copy

Markdown editor

Markdown is now available for the whole account in comments and descriptions. It also supports Emoji.

mardown

Code highlights is supported, so you can format code examples much better now.

Finally, you can save changes using Ctrl+Enter shortcut.

We value your feedback and consider your suggestions when come back to our new features to improve on them.

Minor Features

  • Visual Encoding now supports multiple and custom colors

Targetprocess 3.6.6: Calculated Custom Fields (beta)

Calculated Custom Fields

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:

Effort*(IIF(Complexity==”Low”,10, IIF(Complexity==”Average”, 11, 15))),

where IIF is an Inline IF function which takes 3 parameters (evaluated expression, value for true, value for false)

See some examples of how you can use them!

 

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.

cross process

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.

money cf

Fixed Bugs

  • 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

Targetprocess 3.6.5: Unsaved Comments Recovering, Create a Project from a Request

Prevent the loss of unsaved comments

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.

create project from request

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.

markdown in Descr

Minor Features

  • Relations: Project added to the entity lookup
  • Sync interval for the Git Plugin is changeable now

 Fixed Bugs

  • 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

Targetprocess 3.6.3: Views in a Group have the same access permissions

Left Menu Improvements

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.

change group access

Fixed Bugs

  • 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

Targeprocess 3.6.2: Add Relation to Epic, Left Menu and List Improvements

Left Menu Improvements

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.

group owner

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.

share view

Lists Improvements

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.

team wf delete state

Add relations to Epic

Finally the new entity type appears in Add Relation lookup similar to other entities.

Epic in relations

Fixed Bugs

  • 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
  • Assignable.Team should be editable in REST API

Targetprocess 3.6.1: Visual Encoding

Meet the new beta feature which allows you to color cards by your own rules — Visual Encoding!

Now you can specify the color saturation and highlight cards by some property importance or highlight even intervals of certain properties like Effort or Time Spent.

VisualEncodingSample1

Read the detailed feature announcement.

Lists Improvements

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

lookup-list

Minor improvements

#84602 Customize Cards: Add unit ‘Open/total bugs’ for Feature
#98190 Left Menu Improvements: Add tooltips for long view and group names

Fixed Bugs

#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

Targetprocess 3.6.0: Dashboards, Graphical Reports and Test Plan Run Results Freezing

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.

Graphical Report: Teams / Month vs Cycle Time and Effort

Reports are really flexible, check documentation to create your own report:

Intro
Reports Setup
What you should know
Advanced topics
Use Cases

Dashboards

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.

There are three sources of dashboard widgets:

  1. Predefined widgets in a library
  2. Any List. You can create a List and drag and drop from left menu to a Dashboard.
  3. Any Graphical Report. Create a report and drag and drop it from left menu to Dashboard.

dashboard_

Read the guides about Dashboards:

Intro
Widgets
Use Cases

Test Plan Runs results freezing

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.

Test Plan New View

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.

TPRNew

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:

Remove group with views action

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.

lists_inline_edit_custom_fields

Requester entity in Views and Lists

Now you can create lists and boards that display Requesters entities.

Requesters List

Minor improvements

  • Search by Test Steps fragments.
  • TFS plugin: added a custom synch interval option.
  • TFS plugin: support the on-demand TFS service visualstudio.com.
  • Customize cards: added ‘Initial estimate’ unit for Features.

Fixed bugs

#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

Targetprocess Help

All you want to know about Targetprocess

Recent posts