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.
Having project states allows us to calculate the lead and cycle time, which will appear on the project view.
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.
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!
#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 v.2 was released in 2006. 10 years is a huge timeframe in SaaS world, so we are going to completely remove Targetprocess v.2 soon.
Most of you already work with v.3 user interface and you'll hardly notice any difference. This post answers some questions that may trouble you. Please, don't hesitate to ask more in comments.
Why do you want to remove v.2?
Basically, it affects our development speed. We have to run all old tests, try to not break old things and fix if they break. Less and less people use v.2, so we think we reached a safe moment to cut it completely.
There are some features I use in v.2, since there are no good replacements in v.3
We are going to match almost all features. At least it will be possible to do almost all the things in v.3 as well, like Split, Merge, etc. This is a prerequisite to remove v.2 for us. You can mention any particular case in comments and we will take it into consideration.
I love v.2 and we have On-Site installation
It means you will not be able to upgrade to newer version from Jan 2016. Most likely nothing changes for you, since we didn't improve v.2 last two years.
I love v.2 and we have On-Demand account
In this case we will move your account to a separate server and will not upgrade this account anymore.
If you have more questions, please feel free to ask them.
Targetprocess gives you a great power when it comes down to searching the information. We have the powerful DSL filters, which let you compose fairly sophisticated queries against your data.
However, the power and flexibility are not free, and sometimes our users tell us that it's too hard to manually write the filter queries, especially for the non-techies.
To make this process more transparent and to help our users learn the filtering techniques we decided to create a new "visual filters" feature. The main idea is to show a graphical form to help you quickly compose the filter queries. We want to make sure that you always know how to start building a query, so the filter builder dialog is displayed as soon as you put the cursor in the filter text input.
The dialog immediately displays a list of possible filters for your data. These filters are based on the entity fields available for the currently selected entities, you get all the fields you'd normally get from the auto-suggestion when manually typing '?' into the input.
Let's say you want to see all the cards from the current release. Click the greyed "Any" area, and you should see a list of possible release filters. Choose one, and it will be immediately added to the list of filters.
Of course you can also start typing the desired release name, the suggestion list will be automatically narrowed down according to the text you type.
You can add several filters for a single field by clicking "+ Add" area on the right side of the field row, and you can add new fields by choosing them from "+ Add rule" dropdown at the lower left corner of the dialog.
As you choose several filters, you may notice that the original filter input field text is changed according to your selection. We analyzed the most frequently used filters, and decided to start with a simple rule for filter combination. Filter values in the same row are combined with "OR" operator, and the field rows are combined with "AND".
When you're done with building the query, just click the "Apply filter" button to filter the cards.
We understand that this visual component does not fit all scenarios, and we're not deprecating our existing manual filters, but we try to integrate with them instead. We don't want to stand in the way of our advanced users, so as soon as you start manually typing the filter query, the visual dialog will be automatically hidden. You can either click or clear the input to display the dialog once again.
Nice, so how can I get it?
TL:DR; Once upgraded to 3.7.1, go to Settings -> Mashups and install "Visual Filters Preview" mashup to enable the preview
We try to release the new features as early as possible to get the valuable feedback and adjust the development (you can read more about our process here), and with this feature we go even further with releasing a preview version with 3.7.1. It's already functional for certain usecases, but it's not the final production version, so you may expect some bugs and quirks here and there.
What's more important is that visual filter dialog lets you compose only a subset of all possible DSL filters, and it's not meant to be a 100% replacement for the manually composed queries. And because it's in the early preview stage, we decided to not automatically enable it for everyone, and make it optional with a separate mashup.
We’d love you to try this new feature and let us know what you think about it! If you're feeling adventurous, just open the mashup manager for your account and install "Visual Filters Preview" mashup.
What's in the preview
Here's the list of things which already work:
- Display all fields for the currently selected entities
- Display a list of suggestions for non-primitive field types (releases, projects, states, etc.)
- Support primitive values like text (Name) , numbers (Effort, Times), flags (IsNow, IsPast)
- Support dates
- Exact: StartDate is '23-Apr-2009'
- Range: StartDate >= '23-Apr-2009' and StartDate <= '30-Apr-2015'
- Relative: StartDate is Today - 7(days)
- Oh, and we've also added "months" and "quarters" units for relative dates!
- Support simple collection filtering, like AssignedUser.Where(It is Me or It is 'Admin')
- (Almost) normal conjunctive form for the filters, i.e. we only support filtering queries which are ANDs of ORs of simple field filters.
- For now, if you open the filter dialog for the input with the filter query which doesn't match this template, we will render the empty filter set with default fields.
What's not implemented yet, but is planned for the next releases:
- More helpful date editors—calendars, date pickers, this kind of stuff
- Parametrized identifiers, like Release is Past(2)
- More powerful numeric field filters, with equality, comparisons, and ranges
- Improved state filters—is final, is initial, etc.
- General improvements for integration with existing filters
- Anything else you think important? Let us know in the comments
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:
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.
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
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.
- 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