Is such urgency calculations expected?

[DDzwiedziu]

The same task with only a difference of priority has the same urgency score.

No command specified - assuming 'information'.

Name                  Value
ID                    300
Description           [CENSORED! Too hot for GitHub!]
Status                Pending
This task is blocking 248 [CENSORED! Hot Hot Hot]
Entered               2021-12-11 00:14:37 (5d)
Last modified         2021-12-16 16:34:07 (14s)
Tags                  domoweIT
Virtual tags          BLOCKING PENDING PRIORITY READY TAGGED UDA UNBLOCKED
UUID                  nope
Urgency               17.56
Priority              L

    blocking            1 *    8 =      8
    tags              0.8 *    1 =    0.8
    age             0.014 *    2 =  0.027
    UDA priority.L      1 * -5.4 =   -5.4
                                   ------
                                    17.56

Date                Modification
2021-12-13 00:54:42 Wait set to '2021-12-15 06:54:42'.
                    Status changed from 'pending' to 'waiting'.
2021-12-16 16:34:07 Priority set to 'L'.

❯ task 300 modify priority:
Modifying task 300 '[CENSORED! Too hot for GitHub!]'.
Modified 1 task.
❯ task 300
No command specified - assuming 'information'.

Name                  Value
ID                    300
Description           [CENSORED! Too hot for GitHub!]
Status                Pending
This task is blocking 248 [CENSORED! Hot Hot Hot]
Entered               2021-12-11 00:14:37 (5d)
Last modified         2021-12-16 16:34:34 (1s)
Tags                  domoweIT
Virtual tags          BLOCKING PENDING READY TAGGED UNBLOCKED
UUID                  nope
Urgency               17.56

    blocking      1 *    8 =      8
    tags        0.8 *    1 =    0.8
    age       0.014 *    2 =  0.027
                             ------
                              17.56

Date                Modification
2021-12-13 00:54:42 Wait set to '2021-12-15 06:54:42'.
                    Status changed from 'pending' to 'waiting'.
2021-12-16 16:34:07 Priority set to 'L'.
2021-12-16 16:34:34 Priority deleted.```

[tbabej]

Hi @DDzwiedziu,

this would be expected if you have urgency.inherit set to 1. I suspect that is the case for you? Quoting from man taskrc:

urgency.inherit=0
        Not  actually  a  coefficient.  When  enabled, blocking tasks inherit the highest urgency value found in the
        tasks they block. This is done recursively.  It  is  recommended  to  set  urgency.blocking.coefficient  and
        urgency.blocked.coefficient to 0.0 in order for this setting to be the most useful.

since 250 is blocking 248, which has higher urgency than 250, the task 250 "inherits" the urgency value from 248.

[DDzwiedziu]

Ok, that's definitely what's happening here, as I've wanted to have urgency inheritance from my first days with TW.

So thanks for this, I'll experiment with the coefficient mentioned.