Dependencies, Epics
A
Alex Kuznetsov
It could be awesome to create collection of tasks, like epics or actually any grouping method with progress indication. Subtasks are not valid tool for this they are too obscure on boards. Main goal of this feature is to create some container with progress indication (done, in progress) that can be used as higher picture overview for big planning.
I don't think that deep hierarchy is needed here, just one level down. Basically group of tasks is task with collection of other tasks and calculated progress of that collection. Since collection is a task itself you can create collection of collections and treat it the same way. Again only one level down is needed.
Log In
A
Alberto Alonso
Another way to achieve a similar functionality could be implementing this other feature:
Right now the biggest issue when using task as containers/epics is that when you add a subtask to a list the parent task is also added to that list, which could be annoying for this purpose. Once this solved, and subtasks behaves more like individual tasks, multilevel structures as Initiative/Epics/Stories (Jira like) became possible.
So you can vote for that other feature and try to get something close to this.
S
Shanon Hart
Alberto Alonso Yeah I agree, we can't use subtasks because of the "move main task" behavior, so we use dependencies, but dependencies are much clunkier to manage.
A
Alberto Alonso
This would also be very useful in the Gantt charts too, in order to have a high level view of the project instead of having to present all tasks. Using subtasks for this is possible but kind of suboptimal, as it affects other views.
So one kind of task collection of task container could be very useful for this too.
Caroline Ginty
Hi voters - we want to hear from you about Epics in ClickUp! Specifically, we're interested in seeing you walk through how you manage Epics/agile workflows in ClickUp today (screenshare), any pain points, and top feature requests. If interested, please use this link to schedule a short chat with the product team.
K
Kelsey Ruff
We want one list with our epics, and we want to be able to link sprint tasks to them while keeping track of progress towards completing the epics.
None of these options below work effectively for our team:
Subtasks - since parent tasks can already calculate progress automatically, show rollup fields, etc. This makes it difficult if you haec multiple team mates assigned to tasks inside of one epic. ClickUp doesn't currently allow subtasks to have a different set of custom fields than the parent, which is really clunky to work with. Also, this doesn't work if you have team members in multiple lists.
Linked Tasks / Relationships - you can connect tasks across different lists, but there's no way to keep track of the progress of epics based upon them... No way to rollup completion of other tasks into a related task.
Creating a custom field/label/category: You cannot do "rollup" on progress based on a category. Or use it for Gantt charts.
Using Goals: You can set a goal to rollup task completions from a specific list, but if you have one list that multiple epics could apply to, this categorization doesn't work.
You also cannot use a custom item/task type - since that feature is not available yet.
Laura Stringer
Kelsey Ruff: So glad to see I'm not the only one frustrated by this! I also tried using lists as epics but it got out of control really quickly, and as soon as you bring a task into a sprint you lose its epic.
The custom field is what I've been going with but the inability to view a rolled up report on tasks within an epic makes it an incomplete solution.
K
Kelsey Ruff
Laura Stringer: Yes. It feels like we have to do all kinds of workarounds to have 'Epic' housings like I've seen in other tools such as Jira. It makes it hard to just run everything off of labels. I really hope they create this feature, or at least give us a custom task that I can create regular tasks as dependencies under. Just so I can have that Epic parent relationship. Fingers crossed!
B
Brendan Jones
Actually made this comment elsewhere but repeating it here:
For every task you should (be able to) have the following info:
- Milestone
- Epic
- Release
These should all be default item types when https://clickup.canny.io/feature-requests/p/custom-item-types-instead-of-only-tasks comes out.
Which milestone/epic/release each task belongs to would display neatly on the task (like how https://shortcut.com/product/build do it). Clicking on the milestone/epic/release would show you all tasks belonging to it.
Go to a roadmap view to see all milestones and/or epics for a project.
In views like list view, you'd be able to add columns for which epic or milestone a task belongs to, and filter/sort on those.
Tie a Clickup release to a release in Github/Gitlab and use an automation to set all tasks to Closed automatically when they're released to production in Github/lab.
All this is done manually right now, and it takes major effort.
R
Roman Reynebeau
As much as I desperately want to move away from JIRA, I don't think it's realistic until this feature exists. Tracking progress against an epic is a key part of any agile project.
Guillaume Cougard
Roman Reynebeau: same here ☹️
B
Brendan Jones
Roman Reynebeau: Really hoping they make epics one of the default item types when https://clickup.canny.io/feature-requests/p/custom-item-types-instead-of-only-tasks is done. Milestones also, because right now those are just tasks with different icons.
M
M
I don't understand how to use ClickUp without this feature. I have the following hierarchy:
Epics -> Stories -> Tasks w/ Story Points
I schedule work by creating a relationship between Tasks and Sprints.
I need to know the overall % completion (in terms of of story points) for each Story (and in turn, each Epic).
I need to be able to manage which Task as associated with which Sprint.
So far, I have discovered the following limitations:
- Sprints can't contain subtasks
- Only subtasks can influence automated progress
So I can't have tasks in a sprint that contribute to automated progress of the stories they define, but if I create tasks as subtasks, I can't associate them with sprints.
How do I do what I need to? Am I missing something obvious?
M
M
If you consolidate the votes for this feature across multiple redundant requests, you get a pretty high vote count:
https://clickup.canny.io/feature-requests/p/automatic-dependencies-progress (18 votes as of this writing)
https://clickup.canny.io/feature-requests/p/progress-bar-auto-dependancies-and-time-tracked (16 votes as of this writing)
https://clickup.canny.io/feature-requests/p/task-progress-bar-progress-percentage (at least two votes in interior comments)
https://clickup.canny.io/feature-requests/p/progress-bar-dependency (5 votes as of this writing)
https://clickup.canny.io/feature-requests/p/dependencies-epics (51 votes as of this writing)
Those are just the ones I found so far.
N
Nick Shel
Is there any progress on this? Currently we're using different Lists as Epics and linking them to Sprint folders for agile planning, but having a straight out link link to a high level "Epic" task would probably be a bit nicer as can put a lot more info into it. I think that's one thing Jira does relatively well.
Eric Wightman
Merged in a post:
Create another layer (EPIC/FEATURE)
L
Lucas Pinheiro
It would be nice the possibility to create epics and features so we won't lose track of the task and where it belong. The image is how it works on Devops and it's preety amazing.
Load More
→