search

obsidian-tasks-group / obsidian-tasks

Task management for the Obsidian knowledge base.
https://publish.obsidian.md/tasks/
MIT License
2.47k stars 232 forks source link

set item to a status that is of type DONE and new item not created even though recurs daily #2034

Closed pcause closed 1 year ago

pcause commented 1 year ago

Please check that this issue hasn't been reported before.

Expected Behavior

I created a custom status - skipped, symbol S, type DONE. Given a task that has a recurrence set when I set the status to S, the item should be treated as DONE in queries and the next item from the recurrece pattern should be created

Current behaviour

the item set to S is treated as done but no new recurrence is created

Steps to reproduce

1) create a custom status named skipped, symbol S and type DONE 2) create an item test, recurrence daily due today 3) open the tasks dialogue after the item is created and change the status to "skipped"

Which Operating Systems are you using?

Obsidian Version

1.3.5

Tasks Plugin Version

3.10.0

Checks

Possible solution

No response

claremacrae commented 1 year ago

Hi, manually following steps that require me to invent text to reproduce bug reports has been too unreliable and taking too much time away from development (and my life in the real world...)

So I wrote up some notes on how to submit reports that I can reproduce efficiently:

https://publish.obsidian.md/tasks/Support+and+Help/Report+a+Bug

So if you would like me to investigate this, then please give me exact steps to reproduce, including text to copy - preferably:

However before you do that, have a look at the red box in this bit of the docs first, in case it explains your problem:

https://publish.obsidian.md/tasks/Getting+Started/Create+or+edit+Task#Status

claremacrae commented 1 year ago

Possible duplicate of:

pcause commented 1 year ago

This is a duplicate BUT in that other issue you said to edit manually. I changed

image

but no new item for the recurrence was created. Did not use the model

claremacrae commented 1 year ago

This is a duplicate BUT in that other issue you said to edit manually.

Can you paste in the quote please, as searching for manual gives no hits...

claremacrae commented 1 year ago

(and link)

pcause commented 1 year ago

Sorry. Perhaps I took the docs wrong to mean I could edit the checkbox manually. I would update the docs warning not to create custom statuses that are of type DONE if a task has a recurrence because such statuses will not work properly with recurrences in terms of creating a new instance.

claremacrae commented 1 year ago

I would update the docs warning not to create custom statuses that are of type DONE if a task has a recurrence because such statuses will not work properly with recurrences in terms of creating a new instance.

That is a different issue to anything I have seen logged, and sorry to repeat myself, but if you would like to reopen this and add the requested steps to reproduce then I will willingly experiment with it.

claremacrae commented 1 year ago

add the requested steps to reproduce

Apologies, I meant, add the requested vault to reproduce...

claremacrae commented 1 year ago

Just to note that using custom DONE statuses very much works fine with recurring tasks.

This example in the docs is based on my own setup, which I have many recurring tasks for:

https://publish.obsidian.md/tasks/Getting+Started/Statuses/Example+Statuses#Separate+cycle+for+Important+tasks

So I feel that there must be something else going on with your setup that I am missing.

claremacrae commented 1 year ago

I would love to re-open this if the requested info can be supplied...

claremacrae commented 1 year ago

I would love to re-open this if the requested info can be supplied...

pcause commented 1 year ago

I will see if I can create a vault to demonstrate. The difference I see in what I am doing and the example is that I am going directly from [ ] to [S] . In your example you can click your way through the statuses. I want to go directly from task to a DONE but not use X as done (built in) but use S.

In the end, I am trying to have multiple "next" statuses from [ ] and can't use the modal (as above) and hence enter manually. I may want to have a flow like your example above, but then I have a second flow to go from [ ] to [S] to indicate that I didn't complete the task but skipped the task. Basically I think that given the current implementation what I want to do can't be done.

I think the solution is as follows. Allow various status characters to not have a next status setting, which is required today. When the user clicks the check box, if the current status character has a next state use it and if not have a popup like tasks collector that shows all the possible statuses and let the user choose what is next. This allows me to go from [ ] to any number of workflows. But it also allows one to chain together workflows, as any status that doesn't have a next flow defined would popup the choices again. For example I could create a code review set of statuses and when I get to the "approved" state I have no next status and so I can now invoke a "check in and build" set of statues or phase a deferred workflow which reminds me every week to see if this code is ready to go into the "check in and build" set of statues or the "cancelled feature" set of statues. Perhaps the modal could use the same logic/popup and you'd also resolve the other report??

Of course, that is a feature request and I don't mean to add to your currently overwhelming workload. I will just take this as a limit of the current implementation.