The Order of Comments on Cards
You can now specify the order in which you would like to see comments on cards. From the card description, choose to display either the oldest or newest comments on top. It's a per-user setting, so everyone will be able to set up their own preferred order for following comments.
Custom Term for Request
From now on, it is possible to rename 'Request' with our Terms editor in the same way as other entities. For example, you can rename 'Request' to 'Requirement' and collect requirements that come from your clients throughout the project.
New Languages added to Targetprocess: French, Spanish, Portuguese (the Brazilian variety)
Targetprocess can now be used in 6 different languages: English, German, French, Spanish, Portuguese (the Brazilian variety) and Russian. Translations in all these languages have been completed. English still remains the main language of the system, and the administrator's user interface is not supposed to be translated for now. Every user can switch to one of the new languages via My profile - Account Settings. Read more
Workflow Management for Functional Teams publicly available
We have finished the Beta testing of our new feature and are proud to announce that Workflow Management for Functional Teams is now publicly available. The new functionality will be useful for companies who have teams working sequentially. Accounting, Marketing, Designers and Development are examples of such teams; they are often called functional teams. From now on, several teams can work on the same item – e.g. a feature or a user story – one after another. So, the final state of an item in the workflow of one team is its first state in the workflow for another team. Read more
Minor Features:
- Filtering by entity-specific fields when several card types are selected at the same time
Fixed Bugs:
- Fixed export failure when last commented user name is not specified
- Fixed saved context override by global context
- Fixed failure with renaming tags if they have a long name
- Fixed issues with import for Bugzilla plugin
- Fixed problem with allowing prioritization in lists with the configuration when prioritization should not be allowed
- Fixed sorting in lists for some units when more than one card type is selected on setup
- Fixed problem with filtering projects by anticipated end date
- Fixed problem with the possibility to create allocations beyond the project end date
- Fixed incorrect handling of unsupported expressions in visual filters
- Fixed filtering users by custom fields using api/v1
We’d like to inform you that preparations are being made to disable the use of SSLv3 and TLS 1.0/1.1 encryption protocols.
On March 14th, Targetprocess will disable SSLv3 and TLS 1.0/1.1 to enforce TLS 1.2 with strong ciphersuites on all Targetprocess On-Demand servers and other Targetprocess sites. This change will prevent the use of SSLv3 and TLS 1.0/1.1 for accessing Targetprocess services with all connections, in favor of more secure encryption.
TLS 1.2 ensures that a connection to a remote endpoint is routed to the intended destination through encryption and endpoint identity verification. Targetprocess enabled TLS 1.2 for all servers a long time ago, so you’re already protected by TLS 1.2 if you’re using a modern browser, as compromised protocols have been disabled there. However, most servers do not yet enforce TLS 1.2 for compatibility reasons.
Why is this happening?
At Targetprocess, we understand that our customers share their most precious assets with us -- such as project details and roadmaps -- so we take the protection of your data very seriously. In the wake of vulnerabilities in protocols and ciphersuites (such as Poodle, FREAK, Logjam, KCI and Drown), we want to maintain the highest security standards possible to promote the safety of your data, as well as align with industry-wide best practices.
What are the access types where action may be needed?
There are two different channels that require encryption to access Targetprocess:
- Internet browser
- API integrations
An overview of each and their corresponding recommendation for TLS 1.2 compatibility can be found below in Internet Browsers. Your users will experience issues accessing Targetprocess via your browser if non-supported browsers are in use or if you have disabled the supported encryption protocols in the browser.
Testing your browser compatibility
You can find out if your browser is currently vulnerable to common attacks and if it is compatible with TLS 1.2 on the following Qualis page: https://www.ssllabs.com/ssltest/viewMyClient.html If you have TLS 1.2 listed as available, then your browser should not be impacted by this change, and no action is required.
Action Required for Browser Compatibility
If your browser is not compatible with TLS 1.2 after we make this change, you and other users in your company will NOT be able to access Targetprocess. We recommend that you update your browsers to support TLS 1.2 as soon as possible. Please refer to the compatibility guidelines below.
API Integrations
API Integrations are interfaces or applications–including mobile apps and desktop clients–that are separate from Targetprocess, but use Targetprocess data. If you have any API Integrations, please ensure that the TLS 1.2 encryption protocols are enabled in those integrations.
Action Required for API Integrations Compatibility
If your integrations that use inbound connections to Targetprocess do not have TLS 1.2 enabled after we make this change, your integrations may experience disruption. We recommend that you begin planning to support 1.2 as soon as possible. Please refer to the compatibility guidelines below.
Browser Compatibility Notes
Microsoft Internet Explorer (IE)
Review the Enabling TLS 1.1 and TLS 1.2 in Internet Explorer knowledge article for more details.
- Desktop and mobile IE version 11 - compatible with TLS 1.2 by default
- Desktop IE versions 8, 9, and 10 - Compatible only when running Windows 7 or newer, but not by default. Review the Enabling TLS 1.1 and TLS 1.2 in Internet Explorer article to enable TLS 1.2 or higher encryption.
- Windows Vista, XP and earlier are incompatible and cannot be configured to support TLS 1.2.
- Mobile IE versions 10 and below - Not compatible with TLS 1.1 or higher encryption.
- Microsoft Edge - Compatible with TLS 1.2 by default.
Mozilla Firefox
Compatible with the most version, regardless of operating system.
- Firefox 27 and higher - Compatible with TLS 1.2 by default.
- Firefox 23 to 26 -Compatible, but not by default.Use about:config to enable TLS 1.2 by updating the security.tls.version.max config value to 3.
- Firefox 22 and below - Not compatible with TLS 1.2
Google Chrome
Compatible with the most recent version, regardless of operating system.
- Google Chrome 38 and higher - Compatible with TLS 1.2 by default.
- Google Chrome 30 to 37 - Compatible when running on Windows XP SP3, Vista, or newer (desktop), OS X 10.6 (Snow Leopard) or newer (desktop), or Android 2.3 (Gingerbread) or newer (mobile).
- Google Chrome 29 and below - Not compatible with TLS 1.2
Google Android OS Browser
- Android 5.0 (Lollipop) and higher - Compatible with TLS 1.2 by default.
- Android 4.4 (KitKat) to 4.4.4 - May be compatible with TLS 1.2. Some devices with Android 4.4.x may not support TLS 1.2.
- Android 4.3 (Jelly Bean) and below - Not compatible with TLS 1.2.
Apple Safari
- Desktop Safari versions 7 and higher for OS X 10.9 (Mavericks) and higher - Compatible with TLS 1.2 by default.
- Desktop Safari versions 6 and below for OS X 10.8 (Mountain Lion) and below - Not compatible with TLS 1.2.
- Mobile Safari versions 5 and higher for iOS 5 and higher - Compatible with TLS 1.2 by default.
- Mobile Safari for iOS 4 and below - Not compatible with TLS 1.2.
API Compatibility Notes
Java
Compatible with the most recent version, regardless of operating system
- Java 8 (1.8) and higher - Compatible with TLS 1.2 by default.
- Java 7 (1.7) - Enable TLS 1.2 using the https.protocols Java system property for HttpsURLConnection. To enable TLS 1.2 on non-HttpsURLConnection connections, set the enabled protocols on the created SSLSocket and SSLEngine instances within the application source code.
- Java 6 (1.6) and below - Not compatible with TLS 1.2
.NET
Compatible with the most recent version when running in an operating system that supports TLS 1.2.
- .NET 4.6 and higher -Compatible with TLS 1.2 by default.
- .NET 4.5 to 4.5.2 - .NET 4.5, 4.5.1, and 4.5.2 do not enable TLS 1.2 by default. Two options exist to enable these, as described below.
Option 1:
.NET applications may directly enable TLS 1.2 in their code by setting System.Net.ServicePointManager.SecurityProtocol to enable SecurityProtocolType.Tls12. The following C# code is an example:
System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12 | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls;
Option 2:
It may be possible to enable TLS 1.2 by default without modifying the source code by setting the SchUseStrongCrypto DWORD value in the following two registry keys to 1, creating them if they don't exist: "HKEY_LOCAL_MACHINESOFTWAREMicrosoft.NETFrameworkv4.0.30319" and "HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoft.NETFrameworkv4.0.30319". Although the version number in those registry keys is 4.0.30319, the .NET 4.5, 4.5.1, and 4.5.2 frameworks also use these values. Those registry keys, however, will enable TLS 1.2 by default in all installed .NET 4.0, 4.5, 4.5.1, and 4.5.2 applications on that system. It is thus advisable to test this change before deploying it to your production servers. This is also available as a registry import file. These registry values, however, will not affect .NET applications that set the System.Net.ServicePointManager.SecurityProtocol value.
- .NET 4.0 - .NET 4.0 does not enable TLS 1.2 by default
To enable TLS 1.2 by default, it is possible to set the SchUseStrongCrypto DWORD value in the following two registry keys to 1, creating them if they don't exist: "HKEY_LOCAL_MACHINESOFTWAREMicrosoft.NETFrameworkv4.0.30319" and "HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoft.NETFrameworkv4.0.30319". Those registry keys, however, will enable TLS 1.2 by default in all installed .NET 4.0, 4.5, 4.5.1, and 4.5.2 applications on that system. We recommend testing this change before deploying it to your production servers. This is also available as a registry import file. These registry values, however, will not affect .NET applications that set the System.Net.ServicePointManager.SecurityProtocol value.
- .NET 3.5 and below - Not compatible with TLS 1.1 or higher encryption
Python
Compatible with the most recent version when running on an operating system that supports TLS 1.2.
- Python 2.7.9 and higher - Compatible with TLS 1.2 by default.
- Python 2.7.8 and below - Not compatible with TLS 1.2
Ruby
Compatible with the most recent version when linked to OpenSSL 1.0.1 or higher.
- Ruby 2.0.0 - TLS 1.2 is enabled by default when used with OpenSSL 1.0.1 or higher. Using the :TLSv1_2 symbols with an SSLContext's ssl_version helps ensure that TLS 1.1 or earlier is disabled.
- Ruby 1.9.3 and below The :TLSv1_2 symbol does not exist in 1.9.3 and below, but it is possible to patch Ruby to add that symbol and compile Ruby with OpenSSL 1.0.1 or higher.
As our list of customers continues to expand, understanding the evolving needs of our current customers as well as taking into account the needs of new customers has become a more demanding task. To consolidate this information and to ensure our product roadmap is in line with what the Targetprocess community wants, we conducted a few customer surveys throughout 2015. Here we would like to present the major findings and provide an overview of what we plan on doing next.
Here’s what you told us you like about Targetprocess. Most frequently you mentioned:
- Natural and out-of-the-box support for the Agile methodology
- Flexibility and customizability: it is possible to configure Targetprocess to support any process and to build any custom workflow, no matter how quirky. This frees you up to work with any variations and flavors of Scrum, Kanban, other Agile approaches, traditional project management or your own custom workflows.
- Visual approach to project management. Many of you said that you appreciate the ability to access and view any data in any way that you want. Having the power to view data from different angles gives you superior visibility into priorities, tasks and dependencies across teams, projects and your whole company.
- The boost in productivity Targetprocess gives in comparison to other established products like Jira Software, IBM Rational, Rally Software, and ThoughtWorks. We believe this is due both to the flexibility and visibility mentioned above.
- Customer service and product support: we heard “fantastic”, “instant”, “rapid”, “second to none” so often that we felt obliged to share some tips on how we achieve this.
- Slick, straightforward and appealing user interface. One customer even reported that their CEO wants to steal our UX team 😉
- QA & issue tracking functionality - you stressed it significantly improves your focus on quality
- Tempo of updates and product development
These strong points of Targetprocess are also often reiterated in reviews at third-party websites.
What you asked us to improve
Thanks to your critical remarks and suggestions, Targetprocess is getting better all the time!
Most frequently we heard the following requests:
- more flexibility with access rights (ideally you want licenses of different types: standard, read-only, read&comment)
- easier onboarding for new users
- improved notification functionality
- polished search functionality
- more intuitive Report Builder & Historical Reports
- improved Help Desk module for your own customers
- enhancements for mobile apps
- extended PPM functionality
What we’re doing next
The customer surveys have helped us to prioritize our product roadmap: https://tauboard.com/v/804e592912fa37b7ced3d467fed0cf83.
Keeping in mind the Agile Manifesto's principle of “responding to change over following a plan”, we would group our next steps into the following categories:
- Polishing various existing functionality (please see the improvement requests above)
We have already assigned two development teams to these activities and one additional team is working on improvements for the mobile apps. As for the sequence of improvements, first, we are going to add the Split Entity action and Batch Actions in order to simplify the management of various entities. Then we are going to remove the remnants of Targetprocess v.2 (which are often the cause of complications in the existing functionality). Afterwards, we will focus on easier permission management to provide licences of different types and to improve access levels. - Extending the Project Portfolio Management (PPM) functionality
While many customers already use Targetprocess for program management and Agile project portfolio management (PPM, Agile PPM) we are going to add advanced Resource and Capacity Management functionality, including Custom Metrics. In this regard, we are actively looking for customers to validate new ideas as well as for beta testers for our upcoming PPM features. Please email ppm@targetprocess.com to participate or for more information.
If you missed our surveys or have new requests, please make sure you post new suggestions or vote for the existing ideas at our User Voice portal which is our main source of information for prioritising the work for our development teams.
If you want to learn more about the global trends you can expect from agile management solutions, here is our view on it.
Is there anything you want to say about Targetprocess to other companies?
Check out what else people are saying about Targetprocess at these third-party review and product comparison sites. Even better, leave your own review and let everyone know what you think about Targetprocess. It only takes a few seconds!
