Cannot Prioritize Cards on a View

In Targetprocess you can change card priority (rank) using drag-n-drop. By default you have to hold Shift so that prioritization takes effect. However, in some cases the system might not allow you to prioritize. There could be several reasons for that.

Prioritization is disabled

Prioritization is turned off for this particular view. Check view settings and switch to prioritize tab:

In order to change the setting you need to be the view owner (or co-owner) or have administrator permissions.

Cards should be sorted by Rank in view settings

Prioritization won't work if cards are sorted by any property but Rank on a view.

Here's how the cards Sort option should be set in the View Settings -> Setup tab:

Sort cards by Rank

That is natural if you think of it. If your cards are sorted by some other parameter, like creation date, we cannot change the rank by dropping the card between two other ones.

In order to change the setting you need to be the view owner (or co-owner) or have administrator permissions.

List view is already sorted by some other column but Rank

One can sort entities in lists by clicking on a column name  now, and alternate ascending/descending order. Prioritization is disabled when a list is sorted by values within one of the columns. A column sorting has actually three modes available:

  • Sorted ascendant
  • Sorted descendant
  • Unsorted

So click your column header several times to let the items become Unsorted. Then the prioritization will be enabled again.

Sorting in Lists

Mismatching Entities are selected and displayed

Some card types cannot be prioritized together. The most common example is when you have Requests along with other cards, such as User Stories, Bugs or Tasks:

You can change the rank of requests on a separate view, but the way it is stored in the database does not allow you to do that in combination with other work items. It as well does not make much sense in real life situations. We recommend you to vote for the corresponding idea on our UserVoice portal if you would like to ask us to change it. Please share your feedback and exact use case as well, why is it required in your particular work flow.

Entity type doesn't support prioritization

Some cards cannot be prioritized at all since ranking is not applied to them. We really hope you do not use our software to prioritize users (as human beings). It also refers to Teams, Releases, Iterations, Team Iterations and Builds.

  • Alex

    http://tp3.uservoice.com/forum… vote please if you require a common view with all working items including Requests with ability to prioritize them

  • Alex

    In List views, a column has actually three positions: Sorted ascendant, Sorted descendant, Unsorted. If you’re unable to prioritize Cards, it means the column is already sorted – and not by Rank. So click your column header several times to let the items become unsorted. This should help to enable Prioritization back.

Still have a question?

We're here to help! Just contact our friendly support team

Find out more about our APIs, Plugins, Mashups and custom extensions. Join our community of passionate users and even discuss directly with our developers.