Loading Profile...
Help get this topic noticed by sharing it on
Twitter,
Facebook, or email.
Twitter,
Facebook, or email.
I’m
confident
Milestones for projects and tasks
Can you implement a milestones system so that we can set deadlines for the project and for each individual task?
-
This is the only feature that would prevent me from moving to DoneDone from LighthouseComment
-
-
We've got a couple other things more pressing on our to-do list at this time, but we'll consider it for a future release.
Thanks!
-Ka Wai -
-
I’m
hopeful
yes, please, please, please put this on your list - it would really increase DD's usefulness.
-
-
Hey guys-
We have not considered due dates or deadlines yet. We recently had a discussion internally regarding it. Here's some thoughts Craig posted:
----
There currently is a Priority label on issues (Critical/High/Medium/Low), which I’m sure you noticed. If we added a due date to an issue, it starts getting difficult for a user to decide “what to do next?”. As you’re aware, DoneDone is very focused on letting each team member know exactly what they’re supposed to do next. By adding a due date, it becomes less clear what the real priority is.
For example, a user may have a “low priority issue due tomorrow” and “a critical issue due the day after that” ... which one is more important? By leaving the ‘date’ out of the mix, we’re simpler, and more direct.
You may disagree. And we may be considering it in the wrong way, so happy to hear your thoughts. In the meantime, you can also use the Tags feature and label issues with due dates. Not perfect, but it at least allows you to express a time/date for completion, and you can then do sorts/searches for issues with dates in common.
-----
I find dates (as opposed to Priority systems) should be used to specify a HARD landscape. These are tasks that must be done before a specified time. If a task does not have a deadline, I use a Priority Label to indicate what level of impact I believe the completion of this task will have one me, my company, clients, etc. As I complete tasks that are part of my hard landscape, I transition to tasks with the Critical Label, then then High....etc.
I can see the confusion of having a "low priority issue due tomorrow." If using the operational definitions described above, it really becomes a non-issue. Unfortunately, we all have low priority issues that have deadlines for one reason or another. That is, they have little impact overall, but must be completed by a given deadline regardless.
Just my .2 cents :) -
-
-
-
-
I agree with Brian. And my programmers have been asking for due dates. If there is a conflict, then the project manager needs to step in to resolve it.
Just as an aside, I love all these systems. But they are tools, and have to be used in conjunction with common sense and active project management. -
EMPLOYEE
