linear: map issue priority onto taskwarrior priority#1198
linear: map issue priority onto taskwarrior priority#1198ryneeverett merged 3 commits intoGothenburgBitFactory:developfrom
Conversation
Linear's GraphQL exposes a per-issue priority integer (0=No priority, 1=Urgent, 2=High, 3=Medium, 4=Low) that wasn't being queried, so every imported task got the service-wide default_priority. Add the field to the issues query and translate it onto taskwarrior's H/M/L buckets, falling back to default_priority for "No priority".
7b3953e to
2715883
Compare
Co-authored-by: ryneeverett <ryneeverett@gmail.com>
djmitche
left a comment
There was a problem hiding this comment.
Apologies if I've forgotten some magic here, but I don't see get_priority defined.
It seems the 0 priority from linear should map to the BW default priority, rather than always being H. The tests suggest that is the case but I can't see where that's implemented.
BTW as a daily user of the linear integration I'm looking forward to this. It's been at the end of my +rainyday tasks for a long time.
It is inherited. bugwarrior/bugwarrior/services/__init__.py Lines 169 to 173 in ac52c2a
Since |
Linear's GraphQL exposes a per-issue priority integer (0=No priority, 1=Urgent, 2=High, 3=Medium, 4=Low) that wasn't being queried, so every imported task got the service-wide default_priority. Add the field to the issues query and translate it onto taskwarrior's H/M/L buckets, falling back to default_priority for "No priority".