Usability Blog

1 year ago

Deprecating private impediments

Good day everyone!

In our efforts to continuously improve the Targetprocess experience for you, we're analyzing the performance of some core features, such as visualizing your data on dozens of different views or accessing that data through our API. It's a well-known fact in the software engineering industry that every feature comes with a cost. Unfortunately, sometimes the features we build become obsolete or just don't fire off at all. In a perfect world, such features would be free or extremely cheap to maintain and we could simply ignore them. However, the real world is much more cruel, and quite often there is a cost associated with the ongoing support of these features.

Our "private impediments" feature is a good example of this. According to our analysis, its usage is close to none, but it adds a significant performance overhead to our data querying operations, most notably for inbound/outbound relations lookup. Therefore, we'd like to remove private impediments from Targetprocess in our upcoming release.

So, what does this mean for you?

If you don't use impediments at all, then nothing changes for you. If you use impediments but don't use the "Private" flag on them, then once again nothing changes for you. If you have private impediments, they will be deleted from your Targetprocess account, unless you make them public before the new release.

Wait, what? Are you really going to delete my private impediments?!

Well, yeah, but we've thought this through. There are basically 2 options: either delete them, or make them public. We assumed that it would be terrible to make someone's private data publicly visible. Also, given the fact that the private impediment usage is quite low, and we also continuously make backups for our on-demand instances, we'd be able to restore the data for individual customers if you ask us to.

Hopefully, this all makes sense for you. Don't hesitate to get in touch and contact our support if you have any questions!

1 year ago

How to open views with the currently selected Projects and Teams

Some time ago, we redesigned the Projects-Teams selector. It became a part of views, and the global selector was removed. This helped to standardize and simplify views, but made it impossible to set Projects and Teams just once and navigate through several views with that selection.

To make this scenario work, in v.3.11.0 we’ve implemented a keyboard shortcut that lets you navigate to a new view with the currently selected Projects and Teams.

As usual, you can select the needed Projects and Teams in the selector on the top of the view (this selection won't override the predefined Projects and Teams for this view).


Explore the data. If you need to navigate to another view with the same selected Projects and Teams, simply hold Alt and click on the view you wish to explore.


As a result, the view will be opened using the Projects and Teams that were selected on the previous view.


You can use Alt+Click to navigate through any number of views with the currently selected Projects and Teams.

For more details on how the Projects and Teams selector works, see the guide post.

2 years ago

Would you like to see a Batch Actions feature in Targetprocess?

We’ve recently started developing a Batch Actions feature. As you know, creating a great user experience starts with understanding the needs and behavior of users. To achieve this, we’re looking for Targetprocess users who are ready to tell us about their use cases related to working (or not) with multiple work items at a time.

We’d greatly appreciate it if you could take 2 minutes to fill out this short survey. Your feedback helps us to make continuous improvements and grow as a tool.

3 years ago

Prototype for new Custom Graphical Reports editor

We are working on a new editor for Custom Graphical Reports. Its main goal is to give the possibility to explore Targetprocess data and make it easy to experiment.

Let’s talk about the areas that the new editor will have.

cgr new editor 2

The Data section is quite similar to the current report setup. It allows selecting entities, filtering them out.

Fields that can be used for the selected entities are listed in the Fields section. It will be possible to filter them by type (numeric, text, or date) and by name.

Axes setup will be more visual compared to the current editor, where you need to type information in text fields. Now you will be able to drag-and-drop fields right to the axis (X, Y, Color, or Size).

cgr report gif

It will be easy to set up properties of the axis field (the name, aggregation, sorting, and filter) - just click on the axis field and the setup pop-up will appear.

cgr new editor field setup 3

In addition to that there will be the Action Menu, with many useful items for reports.

cgr new editor actions

Try the interactive prototype and let us know what can be improved, what you like and what you don’t like.