[BUG] Priority is set to "5-medium" after syncing an in jtxBoard created or edited task

[wernharder]

Describe the bug
Tasks created in jtx-Board or tasks not created in jtx-Board but edited there are assigned priority ‘5-medium’ after synchronisation, even if priority was not used at all.
When tasks are created in Thunderbird and synchronised with jtxBoard, the priority remains unused. Only when these are edited with jtxBoard is the priority automatically set. Or if they are created in jtxBoard.

To Reproduce

1. Create a new task in jtxBoard with no priority set
2. Synchronise with Mozilla Thunderbird using DAVx5 and mailbox.org
3. See priority is set to "5-medium"

a. Create a new task in Mozilla Thunderbird with no priority set
b. Synchronise with Mozilla Thunderbird using DAVx5 and mailbox.org
c. See priority is not set at all.
d. Just edit and save the task in jtxBoard with no change at all
e. Synchronise with Mozilla Thunderbird using DAVx5 and mailbox.org
f. See priority is set to "5-medium"

Expected behavior
The priority is not set automatically, because it isn´t used in jtxBoard nor in Mozilla Thunderbird.

Screenshots
A task created in jtxBoard:

A task created in jtxBoard, after sync:

A task created in Thunderbird:

A task created in Thunderbird, after editing in jtxboard and sync:

Device and version

• Google Pixel 8a
• Android Version: 16 (GrapheneOS)
• jtx Board version: 2.15.00.ose
• Downloaded from: f-Droid

[patrickunterwegs]

Hi @wernharder , thanks for the issue report and sorry that it took a while.
So I tried to reproduce it with nextcloud, but it worked without issues. It seems to only appear with mailbox.org. I tracked the problem down. Basically jtx Board sends PRIORITY:0 when it's not set and mailbox.org sends back PRIORITY:5 for whatever reason. So this needs to be fixed on their side.

There is a small thing that could be improved on jtx Board side. The library was apparently updated, actually PRIORITY:0 doesn't need to be sent to the server as the missing property corresponds to PRIORITY:0. I would assume that the mailbox.org server doesn't deal with it correctly and defaults back to PRIORItY:5, which is just wrong.
I can work on updating the library and not send the value at all, which would probably make it work, but it's still mailbox.org that doesn't behave correctly.

[wernharder]

Hi @patrickunterwegs!

Thank you very much for your efforts. I understand that the error is on the mailbox.org side.

I would appreciate it if you could change it so that the value isn't transferred at all if it hasn't been set.

Best regards!