I would like to be able to “unlink” sub-tasks, so that different groups can use a different set of columns. This could even be extended so that sub-tasks from different parent items also do not share the default sub-task columns.
I have a board used to track various projects in HR. One of these tasks contains multiple steps required for a number of forms with different plan year ends. There are a different amount of versions for each form.
Currently, I have to create a parent item for each version, with each sub-task being the exact same list of steps. It would be easier to create and visually more organized if I could make a table. I would have each plan year end as an item in the group, the different tasks required as their sub-items, and the status of each version as a column. This would mean I’d have 9 status columns for one plan year end, 2 status columns for another, and only 1 status column for a third. Right now, the three plan year ends are forced to all have 9 status columns.
At this stage, this isn’t possible due to the underlying structure of subitems.
Subitems are essentially another board that is linked to a parent item. All subitems for their parent’s items are on the same ‘board’, this is why you can’t have different column structures for different subitems.
This feature has been asked before, so it may be something that monday look at implementing in the future, but I don’t believe that it is on the roadmap at this time.
I second this request; it logically making sense to be able to instantiate new columns for different groupings of subitems as they aren’t children of sibling items in a group.
+1 as well. The inability to make different columns on different groups of subitems makes them useless in a lot of cases for me. Subitems should be children of their parent items, not the entire board. That doesn’t make a ton of sense. New here. Aside from posting on these topics how else can we upvote feature requests to hopefully get Monday’s attention?
+1 on this request. Different parent items have different subitem needs for me. I’d like to be able to have control over the columns that show in the subitems for each parent item, rather than having to completely reorganize my board or use way too many subitems with each new project
You could also rethink the structure of the data. Right now you are showing “Plan Year End 12/31” and “Plan Year End 4/30” as items, with lots of subitems. You’re kind of using an item like a group. So why not have “Plan Year End” as a date column? Then, “Plan 1”, “Plan 2”, “Plan 3” etc could be items, and their subitems could be the tasks that they require.
The way you are using subitem columns for each plan is not very scalable. Right now you have Plan 1 through 9, but what about when you add Plan 10 and Plan 11? You would add those columns, then have a bunch of empty cells for the older items.
Groups are meant to be like simple text labels that bundle together items. If you’re thinking of groups as indicating very different behavior, those should probably be on different boards. Items can be moved between groups freely. If each group had a different set of columns (for items or subitems), you would have to “hide” that data in the background, then it’s not accessible, unless you moved the item back to the original group. It’s not very intuitive. Just like when you move an item to a different board, you have to map which columns correlate between the old and new board, anything that doesn’t correlate would be lost. That would be happening every time you move an item between groups.
Going on two years, just curious if this is on any kind of road map, radar, etc.?
I have an application where I would like an open project (the “item”) to have two subitems but the columns for the first subitem are incompatible with the desired information in the second subitem.
Allowing us to have a sort of “subitem template” that allows us to create subitems with different columns under the same item would be a great help. Sometimes we want to have organized information under our items that convey different variables (contact, site address in one subitem but two status cells and a contact cell in another subitem).
I want to further this request. On the one hand it would already be nice to decide the kind of subitem based on a parent. This could work using subitem templates when creating the first subitem.
But even better would be to decide the structure of each subitem individually. Meaning which columns the subitem needs.
My use case is we have tasks working with clients. Each task is an item. The steps to complete this task are our subitems. The differ according to the people responsible. E.g. the client needs to upload files, we need to set statuses and timelines. It would now be great to have subitems that show only what is relevant for a client-task and subitems that show what is relevant for our to dos.
So far we try to achieve this with views for clients and views for us. The thing is we actually need to also see the data provided by the clients but we don’t need a clutter of columns that stay empty on our to do-subitems.
More concretely we would have (shown here in an extremely reduced way):
Project
– Client Task with Columns | Briefing | Files
– To Do with Columns | Status | Timeline
As we need to access briefing and files for us this leads to:
Project
Client Task | Briefing | Files | Empty Column | Empty Column
To Do | Empty Column | Empty Column | Status | Timeline
