In the upcoming version of Targetprocess (v.3.11.4), there will be two changes related to comments: the long awaited “private” comments, and the ability to pin comments. These will only be available for Requests, and are mostly designed to improve the Service Desk experience.
We fully support openness, transparency and all that, but when dealing with requests from external users, you often have to exchange some internal comments with developers or fellow support folks. Previously, this was tricky because all comments were available to customers in Service Desk. Now you can mark the comment as private so that it stays hidden for requesters.
Don’t go too far though; other people with a Targetprocess license will still be able to see the comment in both Targetprocess and Service Desk, so please don’t upload photos from your last party, or something like that.
If you're doing Idea Management and have some popular ideas, you might get dozens of comments from both customers and your own team. No one likes scrolling through through text to see whether or when an idea is going to be implemented, so what will people often do? That's right, post another question. Now you can “pin” a comment to a Request to give it its own "Last Official Comment" section in Service Desk. This way, customers will see current status at a glance.
User stories will now follow their parent Feature
Previously, if you moved a Feature to another Project, its User Stories did not follow the Feature to the new Project. This was fairly counter-intuitive. Starting with this release, if you move a Feature to a different Project, all of its User Stories will follow (as long as they were originally in the same Project as their parent Feature).
If you move a Feature to a Project with a different process, you will get a warning that this change might cause you to lose some custom fields.
Private Impediments have been removed
As described in this blogpost, we're removing this barely-used feature to improve performance and reduce complexity. Feel free to message our support team if you have any questions.
- Corrected the @user mention format for email notifications
- Fixed the creation of a Test Plan with multiple Test Cases via REST API POST
- The order of mandatory custom fields in Quick Add forms will now correspond to their order in entity views
- Fixed a case where it was not possible unlink a Bug from a Test Case Run if its Test Plan Run is the child of another Test Plan Run
- Improved the performance of Relations lookup
- Fixed an incorrect term: When completing Team Iterations, the system would incorrectly describe them as Iterations.
Did you know we have an integration with TestTrack? Probably not. It's a legacy plugin – a really old one – from Targetprocess 2 that connects to the TestTrack bug tracking tool and periodically synchronizes defects from TestTrack with bugs in Targetprocess. Even the research we did in 2008 indicated that it was the least used plugin of all, but now its usage is even lower since it's only available for On-Premises installations (we removed it from On-Demand accounts about 6 years ago).
We haven't added much functionality to the plugin over the last decade, but we still had to keep it as part of the code base (which we're working on reducing), maintain automatic tests, and so on.
It's very possible that this will not affect anyone reading this post, but it's still a formal part of the software and needs a special announcement. So yes, starting with Targetprocess v.3.11.4, integration with TestTrack will no longer exist.
This the part where I'm supposed to say something nice, maybe even dramatic about this feature... but I can't really think of anything. Sorry. Anyway, our code will be a little bit lighter and developers will be a little bit happier, so that's good news, even if it's minor.
Invalid formulas and old-style report formulas will not be saved
We have disabled the ability to save invalid and previous version graphical report formulas .
You can use special functions if you need to create reports using the formulas from previous version of graphical reports.
- RAW_TEXT(<Targetprocess DSL text expression>) for text or boolean formulas. For example:
- RAW_NUMBER(<Targetprocess numeric expression>) for numeric formulas. For example:
- RAW_DATE(<Targetprocess date expression>) for using text or boolean formulas. For example:
- RAW_ARRAY_TEXT(<Targetprocess text array expression>) for using text or boolean formulas. For example:
We will really appreciate your feedback on our reports editor. What do you like about it? What could be improved? Let us know what you think at firstname.lastname@example.org