Subtasks not inheriting order of custom fields from parent.
not on the roadmap
Reneé Bibby
Prior to 3.0, when we automated a subtask generation it would inherit the ORDER of custom fields of the parent tasks. (I know there is a request for inheriting the custom task content of parent task, which is not quite the same.) This is not working correctly now. Is there a chance I need to change how I build the automations for this to work correctly?
Log In
Joey
marked this post as
not on the roadmap
Hey there! Thanks for sharing your feature request with us. We truly appreciate your input!
As part of our efforts to improve our feedback boards, we're closing this older feature request.
Removing old and inactive posts will increase the communication between the ClickUp team and our users, allowing us to hear more of your great ideas!
If you feel this request is worth revisiting, feel free to create a new post!
Thanks for being a part of our community!
Ivan Villa
Hey Reneé! Just want to make sure I understand the screenshots. You say order is not coming over but in the subtask you show there we are missing custom fields. is that a subtask from the parent task in the other screenshot?
Reneé Bibby
Ivan Villa: Yes, so the one on the left is the parent task and the one on the right is the automated subtask. Technically, she can expand the custom fields to find the items that need to be filled out, but the order/pinned fields are not being inherited. (The screen shots are not an exact match because this specific phenomena is happening when my designer is triggering the automation, but it doesn't happen when I trigger the automation. I had her screen shot what she sees, but to submit the feedback I wanted to provide what it should look like.)
Reneé Bibby
For more context, this issue popped up when I redid our automations. I'd built them long ago like jenga towers at the wrong levels and they were so layered it was causing redundant notifications, but I couldn't figure out how to fix. So, I moved the automation to the list level (instead of space) but the automation is intended to work across two lists, each in different spaces. In each space, I've pinned the same custom fields that should show. Yet, no matter what I do at the list level, I can't get the subtask to show the right thing when she triggers the automation by changing a custom field that shows the phase of the project.
Ivan Villa
Reneé Bibby: This one is so strange, I kind of want to get technical support involved here so they can take a look at your setup and get us more context on what this could be. would you mind reaching out to the team via this link.
Reneé Bibby
Ivan Villa: OKAY! So, I think I fixed the issue. But, it was tricky. The way I have it set up is a primary task in one list, when I manually assign a design subtask it automatically adds the list to a separate list for the designer. Then when she changes the status, which is a custom field, it triggers a subtask to our coordinator to send to print. So, I had to set up the PRIMARY task with the same pinned tasks and that seemed to solve it. However, that means the primary task has pinned custom fields that aren't directly related and I don't love that.