Hello.
I'd like to get a permanent link to a task that is recurring.
Currently I can only get a link to an instance of the task, which is problematic.
What I'd like is taking notes on the task and get a permanent link to those notes. But once the task recurs, those notes get buried in the old task instance.
I think there is a design problem here - you should separate task notes from the recurring nature of the task itself.
Hi @tilusnet , thank you for sharing your suggestion.
I would like to double-check what you are looking for. Are you trying to find a way to link back to the previous recurring task from the new one? If so, we current don't have a way to link back to the previous recurring task, I will pass your feedback to our team and keep you posted if we have any changes.
About the part 'separate task notes from the recurring nature of the task itself', could you please kindly elaborate more on this? Thank you again for your feedback!
Peggy, Sep 13, 2022
Hi Peggy.
Thanks for getting back to me.
I'll outline my usecase. There are two facets to it:
- I want to be able to add details to a recurring task globally ─ irrespective of recurrence "instance".
- I want to be able to retrieve a permalink to such unique / global description of the recurring task.
Conceptually a recurring task is a single task which happens to be recurring. As such, the task's Title and Description should never be duplicated and entirely separated from the information bound for a recurrence instance. Now if you separate the changing info from the not changing info, you can also design a unique permalink to the recurring task as a whole. This is what I need in order to reference the entire recurring task from anywhere outside of Quire.
Currently the task id gets discarded and assigned anew every time a new recurrence happens on the task, making permalink generation to a recurring task impossible ─ I believe this is not a good design.
Let me know if you have questions.
tilusnet, Sep 13, 2022
Hi @tilusnet,
Sorry for the late reply. 😭 We consider each recurring task as its own individual task. When the recurring task is completed each time, the number count will be counted towards the stats shown on the Overview page. That's why we have decided on a recurring task as a single task rather than multiple and separated tasks. We are sorry that there is no better news for this right now. Thank you again for your feedback.
Peggy, Oct 11, 2022
Hi tilusnet, I will pass your feedback to our team. 👍
I think adding a link in the newly created task to the original task can be one of the solutions to this problem. If we have any updates regarding this, I will let you know.
Peggy, Oct 12, 2022
Hi Peggy,
I don't think that treatment of recurrences as individual / independent tasks is a requirement for counting them as tasks. The analogy is that of a family: while you can count each member individually, there is also a relationship amongst them, the family itself. You can count both things, eg. 4 individual members and 1 family.
To fix the design problem I documented, you'd need to do the same: add the concept of relationship on top of the recurring tasks.
This is probably best taken forward by a design discussion of your software engineers.
tilusnet, Oct 11, 2022
Hello,
How are you getting on understanding this problem? Is there any update?
tilusnet, Oct 9, 2022