Selecting No project as Project on Add Task adds a __None__ value by default

[its-me-abhishek]

Describe the bug
The previous implementation while iterating over the project field to create and store tasks introduced a bug.
If someone tries to choose no project as a project, either they have to leave the space empty, or it will just add __NONE__ as a value, to that project. This needs to be fixed

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Add Task'
2. Click on 'Project field'
3. Select None
4. See error

Expected behavior
It should have been an empty string ideally, but a value is being passed down

Screenshots
If applicable, add screenshots to help explain your problem.

Recording.2026-01-06.174954.mp4

Additional context
There are no unit tests to check this edge case, hence it probably got skipped. Shall also add the same to prevent further errors.

[ShivaGupta-14]

Hi @its-me-abhishek! I’d love to work on this bug. I’ll submit a PR soon