Staff
Ilija Studen
on Oct 1. 2008. 10:54 am
cyandesign:
Are we just wasting our time waiting for this?
No, you are not wasting your time, but I really cannot provide any details at this point.
As I mentioned many times before, we comment on future features only when they are ready for testing or at least close to testing phase or we keep them as a surprise. It proved to work just
fine.
activeCollab Team Member
Pro
cyandesign
on Oct 2. 2008. 4:40 pm
reggy1:
Too bad Casando,
It's marketing. Why release anything when you have a whole wave of early adapters who bought in right away? Why not wait until their year of free updates us up, and then release the much requested upgrades right after, so the folks will shell out another couple hundred bucks each?
Sad but seems like it could be true, as we were an early adapter and our year is coming up :(
Pro
junomedia
on Oct 6. 2008. 6:10 pm
I definitely add our +1 to this. We recently took on a project that had 195 tasks and the client who wished to re-order their priority and assignees had to go through and manually edit each one in various tabs.
Comments on tasks, and tasks assigned to tickets are others on our wishlist. Clients who create tickets for support often have multiple things they want doing by multiple people. A checklist or tasks added inline by us after they've posted the ticket would make this process much simpler.
Pro
Colin | Rocket No. 9
on Oct 6. 2008. 7:33 pm
We would love this functionality too! Both the draggable tasks/projects/etc and more priority levels.
www.RocektNo9.com
Cross Media Design & Branding
Staff
Ilija Studen
on Oct 6. 2008. 7:34 pm
reggy1:
It's marketing. Why release anything when you have a whole wave of early adapters who bought in right away? Why not wait until their year of free updates us up, and then release the much requested upgrades right after, so the folks will shell out another couple hundred bucks each?
Now that 1.1.4 is out, I can comment on this. Decision to include a specific feature in a release may be influenced based on number of Upgrade and Support renewals it would "harvest", but that is one of the least important reasons. Although it is there as one of the variables in the equation, we NEVER base our decisions on it. No matter when we add something, we will always have a constant stream of upgrades because that is how activeCollab licensing is structured.
Most important reason why feature may be excluded from a specific release or a branch is because it does not fit or we do not have "platform capacity" to do it right.
Let me explain on an example.
Subscription improvements added to 1.1.4 are important. They make the life easier for ALL activeCollab users because they make things going unnoticed less likely to happen. That is HUGE, but from technical perspective, it was easy to make because this change does not bring any radical changes to the system. Only default behavior is changed (smart defaults vs configuration) and although it has huge impact, it was easily implemented and just works.
Reordering tasks is also huge, but it requires a whole lot more work. It requires changes to both tickets and checklists, jQuery UI (not available in v1.1.x) and A LOT of testing. Reason why task reordering will not be added to 1.1 is not because we want to make a quick buck from upgrades and support renewal, but because it would make 1.1 unstable. Feature of this complexity is added only after proper beta testing, and never to something that is stable for a couple of months and should remain that way until new version comes.
Because of that, this type of feature needs to wait for major update that will go through at lease several weeks of beta testing. These major releases take time to be developed, and, as before, they do not take that long because we are lazy or want to make a quick buck, but because there is a LOT OF WORK that needs to be done.
It would be really bad if we had a release every week or had a constantly unstable system because we keep adding things like crazy. Task reordering is something that will be added at some point in the future, but not in activeCollab 1.1. Reason - 1.1 branch stability. It's been stable for the past couple of months and we plan to keep it that way.
activeCollab Team Member
Pro
cansado
on Oct 6. 2008. 9:28 pm
I understand, can we plan a solution for these today? Maybe more priority levels?