GothenburgBitFactory / GothenburgBitFactory/bugwarrior

Logseq items are closed when in DOING state

Open
#1,173 6 comments 0 reactions 0 assignees View on GitHub
bug logseq
Dominant language
Python
Stars
820
Forks
225
PR merge metrics
No merged PRs in 30d

Description

When a logseq block is set to `DOING`, the item seems to be closed in taskwarrior.

Steps to reproduce:
1. add a new `TODO` block to logseq and run `bugwarrior pull`
2. change the block to `DOING` and start the task in taskwarrior by running `task start $JOBID` with `$JOBID` the newly created task in taskwarrior. The command `task active` shows this task as active.
3. run `bugwarrior pull` again. The task will be closed in taskwarrior and a new task will be created.
With `LOGSEQUUID` set to the UUID of the block in logseq,  `task logsequuid:${LOGSEQUUID} all` will show two items.

taskwarrior: v2.6.2
bugwarrior: 2.0.0.post0 (rev 768c90f1afce7fcf892b19febd3bd83b580e6e44 )

logseq configuration in bugwarrior:
```
[logseq]
service = logseq
logseq.token = XXXXXX
logseq.add_tags = logseq
# 2025-11-21 Trying to use the labels as tags
# Currently they aren't there anymore
logseq.import_labels_as_tags = True
logseq.task_state = DOING, NOW, IN-PROGRESS, TODO, LATER
logseq.description_template = [logseq] {{logseqtitle|replace(":","")}}
logseq.inline_links = False
logseq.char_open_link = <
logseq.char_close_link = >
logseq.char_open_bracket = (
logseq.char_close_bracket = )
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.