Option to turn a checklist item into a task or subtask (and vice-versa)
in progress
Log In
M
Melissa Diemand
Just tested this out. It works well except it's odd it makes you re-name the Task. It would be ideal to turn the existing checklist text into the Task name as a default and then allow someone to edit to the Task name if need be.
D
Dustin Taylor
Automatic deletion
Roman
In most cases I'd appreciate automated deletion of a subtask, but in cases, where it has comments and activity, it might be useful to keep it, but close it, and keep it linked, so we don't lose the discussion.
Jeff Kemp
options are good
Smokie Lee
The best UX is always providing the user with an option, automatic deletion is too risky for complex projects with lots of hands in it.
J
John Hunt
The option during the conversion is a great idea. I can see this feature serving well in trials. Some items are better tried as subtasks while other times as a checklist. I would not have to start from scratch if I decide to standardize by creating a template
Kamau Cooper
Since having projects with multiple hands and in different departments having a checklist task item has been most helpful for maintaining order. Especially if one check list item needs to be completed triggering an automation for a notification to another parties to start their task.
Ivan Villa
Hello everyone! Just wanted to touch base with an update and gather some thoughts.
A few months back, we rolled out the feature allowing you to create tasks and subtasks from your checklist items. We'd love to hear about your experiences with this functionality and any thoughts you might have on how it's working for you so far.
We're now exploring the next part: enabling conversion from tasks/subtasks back into checklist items. We're curious about your preferences on handling the original items during conversion - would you prefer automatic deletion of the originals, or would you rather have deletion presented as an option during the conversion process?
Looking forward to your feedback!
Konstantinos Tsio
Having the option to delete during the conversion process seems way more efficient since it will act as a safety-latch against accidental actions.
E
Edward Prados
Ivan Villa I'm okay with automatic deletion to avoid one more step, since I feel that by definition, if you want to make a checklist into subtasks, you aren't going to want to keep the same items as a checklist. But I have another idea - see below. Also, the popup that comes up about posting about this to the card is confusing. The "Cancel" option could be interpreted to mean that you want to undo the conversion, but that's not what it means (I think). To deal with all of these issues, I'd recommend that the popup contain the following buttons: "Post", "Don't Post", "Cancel" (to undo automatic subtask creation), and a checkbox that the user can check to "Don't delete the checklist items when converting to subtasks".
Rob Peeler
Ivan Villa Having the option to delete would be preferred. I like being able to make subtasks from checklists, but it's almost too easy. I, and others on my team, have accidentally created them without realizing it. It would be great to have a visual confirmation or additional level of "are you sure" on both creating subtasks from checkilsts and the reverse.checklists
Nathaniel Cassidy
Ivan Villa like Konstantinos and Rob have both said giving the option to delete feels more robust from a safety point of view to stop accidental deletions.
Also means that if the original subtasks have context you might want to merge into the parent or another task then this is an option.
Leslie Surel
Ivan Villa I would not want the original subtask details deleted without warning. Users might not realize there were notes or conversations or attachments that were needed. I agree with the others where we either get an "are you sure" option, or even better have the option to keep the subtask. My ideal workflow:
1) Select "Convert Subtask to Checklist Item"
2) Popup box explains what's happening, similarly to when you move a list to a new space and statuses don't agree. Remind folks that subtasks may contain details that won't carry over to a checklist item, including notes, chat, etc.
Could there be something where it tells you if the subtask does have other info? Like "This subtask contains: [Y] due date, [Y] description, [N] checklist, [N] attachments"?
3) Then the choices are:
a) Create a new checklist item and delete the subtask and all its details. (But have subtask go to trash where it could be retrieved if needed.)
b) Create checklist item and retain a copy of the subtask (so you now have both the original subtask and a new checklist item)
c) Cancel
So essentially, a checklist item would be created using the subtask title, and the subtask itself is put into trash, vs. an actual "conversion" where you lose the subtask permanently.
Does that make sense?
H
Henrik Hjort
Ivan Villa To me I would expect that clicking "create task" would either ask me to if I want to delete original .If it said "convert to task" I would expect the list item to be deletede automatically.
I suppose the first option is the most flexible and would also give a chance to cancel if you click accidentally.
Melanie von Schorlemer
Ivan Villa Thanks for sharing this feature. I would you rather have deletion presented as an option during the conversion process
R
Ralph Stokes
Ivan Villa
I think I probably wouldn't mind if they just got deleted but an option sounds like the best way to go, just in case.
Any idea how long this will take? I have a lot of subtasks I want to convert into checklists! checklists into subtasks I didn't really need for anythign so I can't comment on how that's going!
A
Ann-Makir Magloire
I would also like to be able to easily switch a parent to subtask or vice versa. Just a click and switch to parent and move to subtask.
J
John Doe
Needed to do this right now, big agree
Load More
→