Moving milestones across projects. (And three extra features)
Last week, we introduced a new feature where you could finally move elements across projects. When we did, we received the usual (and gratifying) lot of emails to thank us for the new feature -- and obviously asking for more.
One of the common "complaints" was that we didn't allow users to move milestones across projects. We didn't think it would be that important -- and we were wrong!
So, we escalated the issue, and implemented it. So there you are: you can finally move a milestone from a project to another.
With this deployment, there have been several small (but important) features as well:
1) When a new version of Apollo is available, you can chose to reload it later. This means that if we decide to release a new Apollo just while you were writing a long, long message, you don't have to worry about losing it anymore.
2) The person who creates a task is automatically subscribed to its comments. This will prevent situations where other users write a comment on a task, and forget to notify the original poster (assuming s/he would get a notification regardless!)
3) The activity stream has a new look for messages, which also shows if they have one or more files attached.
I hope you'll enjoy Apollo this week!
Merc.
2 comments so far
Thijs Kaspers
Tue, 10/18/2011 - 14:01
Nice job guys! Those small features make a big difference :)
Rita
Mon, 04/01/2013 - 02:59
These are some of the same issues I have with Basecamp. Once the proejct grows, the messages become unwieldy and hard to keep organized. One of the (many) things I love about LiquidPlanner is that it makes it very easy and simple to keep messages organized by task, proejct subfolder or main proejct folder. So, you'll always be able to find the message you're looking for because it will be organized properly.(Note: I am hired by LiquidPlanner to spread lots of love for them online but I was a very happy user of the system beforehand)