On removing parent, task removed from day view
complete
C
Concerned Rebe
When I want to remove the parent of a subtask I have today, the subtask (which is now a regular task) is no longer in my day view (even though the date is still set I think).
Log In
Hamish
complete
Hamish
Hamish
in progress
I'm solving the issue by adding a notification below the drag, which will let you to restore the previous date
Hamish
under review
Thanks, I'll have a think on your suggestion
Hamish
closed
I can't reproduce this, for me when I set a date to a subtask, and then remove the parent, the date stays
C
Concerned Rebe
Hamish the date does stay, but the subtask isn't actually shown on that date for me...
Hamish
Concerned Rebe Do you mean removing parent by drag and drop, or removing parent by tapping three dots > remove parent?
C
Concerned Rebe
Hamish steps to reproduce:
- Drag-and-drop task to make it a subtask
- Tap the now-subtask
- Three dots > Remove Parent
Now, the date is gone for me. Literally just reproduced it as we speak.
[Edit] As I was doing this, I noticed the date actually gets removed once I make it a subtask. Not sure why...
Hamish
Concerned Rebe: Ah yes, I see - it's dragging and dropping that removes the date and that was a decision I made, so not a bug.
I've had another report of confusion around that here: https://bullet.canny.io/bugs/p/removing-parent-from-a-sub-task-deletes-previous-data
The reason I made that choice is that if the date is not removed, it will remain where it was dragged from. Essentially I was choosing between two different confusing functionality - either it's confusing if the person drags the item stays where it was dragged from, or it's confusing if the person drags the item and data from the context of where it was dragged is lost.
Ultimately, I decided that it should always be removed from the context of which it was dragged, i.e. when dragged from a date it should lose its existing date so that it doesn't stay there.
This may have been the wrong choice since there is this confusion about it 🤔 but maybe there will be more confusion about it if I choose the other option!
I wonder if it should be made a preference
C
Concerned Rebe
Hamish I think your choice is sound, but what maybe would be helpful is that if a subtask without a due date is dragged away to become a main task, it automatically inherits the due date of the parent task. That way, at least you avoid subtasks "growing up and becoming independent" getting lost because people don't expect them to not have a date.
Hamish
Thanks, but I can't reproduce this. Subtasks don't share the date of the parent task, so if you have set the date of the parent task to today, but the subtask is not set to today, then the subtask won't stay on today - that's intended behavior.
P
Poor Barbara
Hamish I have reproduced it as follows:
1) I create a task (1), which is dated today and will act as a parent.
2) I create another task (2), which has today's date and will act as a daughter.
3) add task 2 as a subtask of task 1
4) I have noticed that in this step, task 2 loses the attribute of its date (besides reminders and priority, among others)
5) inside task 2, if I use the delete parent option, task 2 does not recover its original date (nor the rest of parameters), it remains without date and therefore lost.
Hamish
Poor Barbara Ah, I see - thanks for the reproducing steps.
When I designed drag & drop, I made a design decision that whenever an item is dragged, it will be removed from where it is being dragged from. That means when being dragged from a date context, it will lose its date. If it didn't lose its date, it would remain in the place that it was dragged from (as well as being in the place it was dragged to).
Another way you can make an item a sub-task is by tapping on the entry, go to the three dots, and selecting 'make subtask' this won't remove the data.
Re. deleting an entry - after deleting a parent task, I would expect the subtasks to be deleted anyway. This isn't the functionality currently but I do plan to implement that.
P
Poor Barbara
Hamish Thank you for taking the time to explain it to me.
Understood then, it's not a bug, it's a feature!
I will use the second method to save the data :)