Tim Jasper Yes, I second this!

Caroline Ginty Hi Caroline, FYI the form doesn’t work for me on iPhone 15 Pro, last version of iOS , Safari: I am unable to select options on the second question. Weird because normally typeform is amazing on mobile, but this form seems to use a custom layout.

I hope I’m the only one with the issue but I’m gonna have to give up on answering the survey for now, I’m stuck at that page

Thanks

Caroline Ginty Awesome! Here are my replies for open discussion! And because it's easier to type out my answers here & paste them into the survey.

Q1: What is your use case for different statuses for tasks and subtasks? What would this unlock for you? A1: I do product development (real product development, not software); 3D printing for production. So physical prototypes are an important part of the process. Now this might not be quite such an issue for bigger companies, but for now, each product is just a ("Product") task for my current stack. So let's say I have a "Prototyping" Milestone Subtask under the "Product" (Task). Well that's just going to be say; "On The List", "In Progress", "Review", "Stuck!", "On Hold", "It's Real Now! 😅". However, for the actual making of each prototype (sub/sub/subtask) I need statuses like "Setup", "Printing", "Evaluating", "Failed", "Working Sample", Retired". Currently I just use a CF called "Prototype Status". Which works fine, but wouldn't really be necessary if we could just have separate statuses for sub, sub/sub, sub/sub/sub tasks. I don't know that there's really much of a technical advantage to having it as a separate CF? Reporting maybe? ¯\_(ツ)_/¯

Q2a: The ability to assign a different set of statuses to subtasks than their parent task Q2aA: Somewhat Important

Q2b: The ability to customize subtask statuses. Q2bA: Somewhat Important

Q2c: The ability to set default subtask statuses at the space or project level Q2cA: Not Important

Q3: Please describe your ideal feature for having separate subtask statuses in ClickUp. What would be important to include? Q3A: In a bigger, brighter future where I have say, physical locations other than my garage, and I'm tracking all my assets, those main level items like "Location 001" and "3D Printer 007" would only need basic statuses like "Scouting", "Negotiating", "Under Lease", "Moved", or "ON LIST", "ORDERED", "SHIPPING", "RECIEVED", "SETUP", "ONLINE", "OFFLINE", "RETURNED", "DISCARDED/SOLD". But for maintenance, I might need subtasks with statuses such as "Nozzle Time", "Calibration Needed", "Belt Replacement", "Electronics Disaster", "MMU Effing Up Again", "Crashing", "Clog", "Deathwad". Again, I'm managing these with CFs currently, and may keep it that way for some things, but sometimes I feel like a whole CF isn't really necessary.

Q4: If we built the first version of this feature to only include simple statuses (to do, in progress, done) without the ability to customize, would you use it? This question is required.* Q4A: No, I need the ability to customize in order to use the feature

Q5: A: Sure, why not?

VINÍCIUS TEIXERA: Hi, my team works on scheduling and time tracking so I don't have any info on this area of the product. I'll find someone who would and ask them to check in on this request.