Import full subtasks and nested subtasks via CSV (custom fields, checklists, etc.)
planned
Kirk Mullis
I would like to be able to import details about Subtasks via CSV, such as Time estimates, Custom field values, Checklists, etc. There is no way to bulk update this info in subtasks so being able to do so via CSV is critical to be able to take advantage of those additional details
Log In
Lily Chan
Merged in a post:
Import Multiple Checklists
P
Proyectos Empresys
When importing user stories, it doesn't allow me to add several control lists, it's only conditioned on creating a single one (1), which is impractical, since then I have to enter each task to separate these control lists, I haven't found the correct configuration to recognize several control lists and I don't know what separator would be the most correct one. If they can allow them to create multiple columns inbound to their native “Checklist” field, that would be great. Otherwise, they would share a CSV with an example of what it would be like for the ClickUp import to understand that it must generate several control lists.
Lily Chan
Proyectos Empresys Thanks for your feedback. I'm going to merge your request into an existing feature request that will cover this use case.
S
Shaheer Jameel
I believe Click-Up supports 7 levels of subtasks. Giving the ability to adding Columns ST1 (Subtasks level 1), ST2 and so on till ST7 in csv uploads will allow users to add Subtasks with fields and cutome fields. It should have been there from the start. Asana offer something similiar
William Gets
ASAP please
Lily Chan
Merged in a post:
CSV Import - Rich Checklists
Wes Brummette
Currently, the CSV importer can import 1 checklist. This thread is for the ability to import rich checklists into a task via CSV. (Nesting, multiple checklists, assignee).
Lily Chan
Merged in a post:
Import data as checklist
Truc Thi Thanh Tran
Ability to import data as checklist as task
Lily Chan
marked this post as
planned
Lily Chan
Merged in a post:
Ability to import subtasks with different information
Jennifer Hall
Currently when importing you can have it create subtasks but it doesn't populate the information for each subtask, if I want the information that comes with a subtask then I have to import it as a task instead and then bulk edit it once in list to go under the proper parent task but if you're importing a 100 or 200 or more bunch of tasks and subtasks, this is VERY cumbersome to then have to go and bulk edit things to move and also opens one up to making mistakes. Would be better if there was a way on important to let the importer know hey this is a subtask and you need to put it under this parent task
Attached a SS of an example of what I envision, would be easy in prepping my import sheet to quickly show which ones are supposed to be subtasks or which task name (campaign column being task name).
Lily Chan
marked this post as
open
Lily Chan
marked this post as
considering
Load More
→