A dedicated view for planning sprints.
Review current and past sprint progress, plan for upcoming sprints, understand past sprint metrics, team velocity, etc, all to help plan future sprints.
This is a MAJOR MAJOR missing feature.
Very excited for this!! The gantt view will be essential for this... one thing I wanted to mention was that I think the new milestone tasks (as they currently are visually represented on the gantt) are a bit confusing in relation to normal tasks since they sit right on the line when tracking date whereas the normal tasks feel more like a progress battery that fills the days. If the diamond sat within the lines I feel like that might make one less confused when reading what day it's set to be due. Also, maybe eliminate the start date field for milestones if it isn't visually represented on the gantt? Don't really see the point for it if I only see it under task details.
@Nick: super curious!
@Nick: awwwwww yeeeeahhh! Been waiting SO long for this!!!
There is a related topic here:
Related to Sprints feature to be specific.
And I hope you are working on 3 distinct features here as all of them have their specific attributes.
Cheers and looking forward to this.
@Nick: Yes would love to get some details of what you guys intend here, been waiting eagerly for this, too! Perhaps a separate container like goals that would be able to collect tasks from various lists? And be seen on the Gantt on its own?
@Bill: You'll just have to wait and see 🙂!
@Nick: Eagerly Awaiting Nick!
@Nick: ya boi! 🤘🚀
I just want to show my interest on that too !
Really milestones described as Julien THIERY said is exactly what is needed !
Milestones that :
- cannot be moved easily
- are not tasks
- that can be filtered ("see milestones only")
It has been 2.25 Years since this feature was 'Planned' and no update since then
Hey guys @Ivan Villa & @Zeb, great to see this post getting some activity. We've spoken about this quite a bit (offline) and highly concur with my fellow colleagues here. I continue to struggle with properly accounting for Sprints. Goals v.2 might be a solution depending on how you guys formulate that, but would love to see a dedicated Sprint "container" which lives "separately" in ClickUp, perhaps as its own view? @Drag Ivko that is a terrific list!
It seems a lot of dev teams are using ClickUp and you really have a chance to continue to bridge as a tool where development, and the rest of a team's work, can live, without overly needing to integrate.
And for some inspiration, look at this great post from stackshare.io. Asana, Wrike, Smartsheet for that matter, are weak in the dev implementations, so if you guys can keep the foot on the gas you can continue to separate yourselves from those guys, and most importantly get some increased usability into ClickUp.
Yes!! For now it's very difficult to properly keep up with metrics and plannings for sprints. It needs to be a dedicated feature, maybe integrated with dashboards, in which we can set up sprints and it creates the relatories with the last sprint's burndown, done stories, etc, and also a proper velocity widget in which we can compare the velocity of each sprint. I don't exactly like JIRA but that's something they do really well.
Jira style sprint planning view is much needed
Preferably one that can be built from custom filter
Several milestones per task would be amazing!
Task = "Design Concept" (for lets duration of 2 weeks)
Milestones inside this task = "First internal review", "Second internal review", "Client Presentation" (with no duration, they are just dimond shaped milestones)
Our curent PM tool (Teamwork) only allows 1 milestone per task wich I think is not ideal...
Attached a sample of multiple milestones in one task.
I just updated a task to a list. It preserved the timer hours, which is great but I can't add directly to the list hours besides it being an aggregate from a list task.
I thought it would be helpful to be able to add estimate hours to a list and for the list to track time spent. This would be helpful in laying out a project outline with milestones, prior to filling in the list tasks. Perhaps the list hours can be a task budget, with each task allocated estimate subtracting from this budget.
Eg. Say Design task list is assigned 2 weeks. The list would then auto populate a suggested milestone and establish the budget estimate for design. Each task entry that is then added to the list can be assigned an estimate, which will subtract from the Design task budget.