Priority doen't seem to have an effect

[wynillo]

Maybe I just misunderstand the priority system.

Version
Beta 1.7.32

Steps to reproduce
1. I set up a team with max Task 1.
2. I create a new software. Set this task priority to 1
3. I accept a few contracts. Default priority stays 5.

Expected result
Tasks will be processed in priority order. 10 -> 1

Actual result
Tasks get processed by the order in the task list in the right sidebar, ignoring priority completely.


EDIT: Damn, it is even stated in the "Max task"-setting. I make it a feature request instead, as it is not intuitive this way and leads to a lot of shuffeling in the task bar. May let me sort that bar via priority.

[Personal Responsibility]

Yeah it's a bit weird for me too. I believe what it does is just shift the workload by the ratio of the priority. If I want to set priorities, I do that by using the secondary tasks of the users, and secondary tasks of the team. That is the most clear and efficient for me.

[Arthur Wolf-Rayet]

When you hover over the max tasks slider it tells you the this will result in the team working on the top-most tasks on the task manager in order until the maximum is reached. This ignores priority.

So having them set to max 1 task that team will only work on the first task they are assigned to in your task list, regardless of priority.

Also, priority goes backwards so a priority 10 task will be performed first and a priority 1 will be performed last (or with least importance).

In effect, you can use max tasks to assign an order that the team would do a list of things in sequentially, or you can tell the team they have a series of tasks to complete all at once and then use the priority system to assign a level of importance.

Max tasks = 1 will result in the team doing tasks in order (A, then B, then C) but max tasks = unlimited & priority 10,9,8 assigned will result in the team doing all three tasks at the same time but with more effort on the 10 than the others (AABbcc)