Logseq items are closed when in DOING state

[wimvinckier]

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 768c90f )

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 = )

[scross01]

I'm not able to reproduce the issue following these steps, used the same bugwarrior commit version and config settings.
The only difference in my environment is I have the latest taskwarrior v3.4.2.

[wimvinckier]

Looks like I'll have to switch to the newer version.
Is there any way I can debug the current issue I have?

[ryneeverett]

Is there any way I can debug the current issue I have?

Per, my latest comment on #1168, I wonder if the logseqid is changing? That's the most reasonable explanation of how you'd have multiple tasks with the same logsequuid.

[ryneeverett]

I suspect this is a duplicate of #1168 after all. Could you confirm if the closed task and new task have differing logseqid and logsequuid?

[wimvinckier]

Hi @ryneeverett , I think I found what was going wrong. I had my uda configuration wrong in taskwarrior. My uda.logseqid.type was set to numeric. By running bugwarrior uda I saw there was a difference. I've updated my configuration and now it looks like it doesn't close the item anymore.

[ryneeverett]

Thanks for reporting. Can you clarify that and how that happened? Had you defined that uda in your taskrc?