Earlier this week we launched a big Basecamp update that allows people to attach files and leave comments on to-dos and milestones.
Since we launched the new feature 72-hours ago:
- 220,568 comments have been posted
- 197,003 (89.03%) comments were posted on messages
- 18,481 (8.35%) comments were posted on to-dos
- 5088 (2.3%) comments were posted on milestones
(You may notice that the numbers don’t add up — that’s because new comments were added between the database queries)
We’re really happy that about 10.5% of the comments posted in the past 72 hours were comments posted on to-dos and milestones. That’s great uptake on a new feature in just 3 days. We’re thrilled that people are loving the new feature! Thanks for your continued support.
Royal8
on 11 Sep 08“Just when I thought I was out… they pull me back in. ”...
Great! new feature. Positively something our team and clients were waiting on.
...Leave the gun. Take the cannoli…
Andrew
on 11 Sep 08Couldn’t you have just done a query with a UNION to get a snapshot?
JF
on 11 Sep 08Note: I updated the post to 72 hours (was 48 in the original post). I forgot a day ;)
Ramon Leon
on 11 Sep 08Yea, now if we only had timestamps so we could see how old the task is and a label saying who assigned it, we’d be golden. Guess I’ll have to comment every task manually since the comment at least has a timestamp, which is weird since the task doesn’t.
Radoslav Stankov
on 11 Sep 08Very nice feature :) Can you please give some statistics, about the attachments in those 72 hours
Brett Atkin
on 11 Sep 08I’ve always thought the To-do’s and the Milestones where missing something. This was the answer. Thanks.
Tester
on 11 Sep 08it shows up on neither….
.
on 11 Sep 08Still says 48 hours in the last paragraph
Jay Owen
on 11 Sep 08We are definitely using the new features heavily for our business. The new comment improvements have really streamlined our workflow and made getting things done faster. Thanks for keeping things moving forward.
Bryan Sebastian
on 11 Sep 08This has been a huge enhancement for us. As software developers we no longer need to add “Please see document x in the files section for a screen shot of the problem” on our to do tasks for bug fixes. Everyone we collaborate with on projects is digging this.
Tobias Crawley
on 11 Sep 08I agree with Ramon: since the comments turn to-do’s into a conversation, it would be nice to know who started it – esp. when you are trying to figure out who should receive email regarding the comment. I know you say ‘no’ to suggestions, but maybe this one will float up soon.
David
on 12 Sep 08I’m sure I’ll get that naughty little troll hat for this comment, but maybe people are using it because it was one of those really obvious features that’s been being needed and requested for years now. Sort of like being able to put a due date on to-do’s, a feature that has been being asked for and pleaded for on a daily basis by your users for how many years?
David
on 12 Sep 08Tobias Crawley said:
”...since the comments turn to-do’s into a conversation, it would be nice to know who started it”
Now now Tobias, don’t get too greedy. Knowing who posted a comment is an extreme request ;-). Perhaps in another 3 years.
JF
on 12 Sep 08it would be nice to know who started it – esp. when you are trying to figure out who should receive email regarding the comment.
The first person who posted the first comment started it. Am I not understanding your request?
Anonymous Coward
on 12 Sep 08Jason, I think they are asking for an indicator on who created the task and when… not the first comment tied to the task. We have had a few clients who we collaborate with ask for this as well. We basically put a to do for everything and assign it later… sometimes the client wants to go thru a to do list and remove some that are really old. Since anyone on the project can add a task to the to do list, it would be cool to see who added the task and when. Ramon is saying he can achieve this now by placing a comment on the to do because there is a timestamp and indicator of who created the comment.
Bryan Sebastian
on 12 Sep 08Sorry… forgot to put my name on my post… I am the anonymous coward above. My bad.
Bryan Sebastian
on 12 Sep 08@David… you can tie due dates to a to do item(s) thru milestones. Granted the milestone is tied to a to do list and not a specific task. How often are you creating a list of tasks and each task has a different due date? I think you need to create the tasks as… here is a list of things that need to be done and this is when they should be completed (milestone), versus, here is a list of things and this 1 has to be done by then and this 1 by then etc. Just my opinion.
David
on 12 Sep 08Hi Brian,
I appreciate your suggestion but that’s just not how I and many other users want to do it. It’s critically important that we be able to assign due dates to to-do’s without jumping through hoops (i.e. workarounds). I fully respect that many people do not care about or need to use to-do due dates, nor would I want to force them on anyone, but for many of us do, they are a must, which is why, at least based on my observation, it’s probably the most requested feature on the BC boards and has been for years.
Thanks
p.s. Before someone tells me that I should use a product that does what I need to do, that’s what I am doing, thank you very much :), it’s one of the reasons I stopped using BC. I still think BC is a great program, but IMO it’s a little bit nutty to consistently refuse to implement a feature your users have been clamoring for. It’s not like we are talking about adding Gantt charts or dependencies or all the things BC doesn’t want to be. We’re talking about being able to tell someone when you need something done :).
This discussion is closed.