A bunch of pre-sale questions
Page: 1
First, I apologize in advance for the length of this and the number of questions....
I'm evaluating aC (Corporate version) for use by my company. I've been playing with the trial, but with the inability to add more sample projects, the inability to see how administration (especially user management) works across projects, and the terseness of the docs, I'm finding it difficult to develop a complete understanding of how the software works. Thus, I'm hoping you fine folks in here can help me out.
Here, briefly, is our situation. We have a handful of developers scattered around the world. All of them are managed at a high level by our CTO. What we want is for him to be able to assign entire projects to one or more developers, and then easily follow the overall progress of those projects. The developers themselves need to be able to do most of their own PM, but in such as way that there's transparency so that the CTO may follow along. Additionally, some developers will be getting small teams underneath them, and those lead developers should be able to perform CTO-like management over their own teams. That's the gist of our situation; here are some specific questions and requirements in no particular order:
1) Projects need to have tasks, and tasks need to have sub-tasks. All tasks need to have the option of being tracked through a series of phases (like "Coding" or "Awaiting Change Management").
2) Each task needs to have the ability to have associated notes and comments stored with it.
3) It doesn't appear to be possible to specify milestones without dates. Doing so would be helpful for us in many cases because a lot of our smaller projects are done on an as-time-permits basis. In these cases, there are no deadlines, and no way to make even slightly educated guesses about deadlines, and yet, it'd be nice to still follow these projects through a series of milestones. Is stripping this requirement in the code a large modification (i.e., it would require changes in several places and affect database integrity)? Or is this a change already planned for a future version?
4) When dates are used on milestones, and you change one of them, it'd be nice to have the option of having aC automatically push the subsequent ones back by the same amount of time.
5) I'd like to be able to attach files and comments to any object, but this doesn't seem to be possible.
6) It'd be nice to be able to easily reference other objects in comments, and have aC automatically make the references into links. A similar feature can be found in Bugzilla, where, for example, you can refer to "bug 6 comment 2" in a comment, and Bugzilla will automatically make the phrase a link to the referenced bug and comment. This would be a nice future addition.
7) For the CTO and team leader roles, we need easy ways to see the overall status of all projects (% complete, ETA if available, etc.), the tasks that everyone is working on, and the status of those tasks (% done or phase ["Coding", etc.]). How are these goals best accomplished in aC?
8)How does one create subtasks on tasks? I'd like to reflect inter-task dependencies.
9) We'd like to have some basic integration between our PM system and our corporate wiki. In particular, when we create a project, we want a project page created in the wiki, with the link readily available wherever it makes sense in the system. Additionally, we want to optionally create a new wiki page for each task, and put a link to it on the parent project's wiki page. And again, we want the tasks' wiki links visible in the PM system where it makes sense.
10) What's the best way to support a sign-off process? When a developer completes a task, we want them to mark it as waiting for a sign-off, then have the team leader do a code review or whatever other checks are necessary before doing the actual deployment.
11) Elsewhere in the company, we're using Gemini, another PM system. We have some hooks for our SVN system that catch Gemini task references in commit comments (e.g., "gem:367" to refer to task number 367), then create comments on the Gemini task that includes the commit message as well as a list of the files effected by the commit. Is there anything out there that would provide a similar integration between aC and SVN?
12) Is there a way to get data out of aC, like an XML export method?
13) I've noticed that the formatting toolbar for text fields doesn't support Safari or its many derived browsers (like OmniWeb). Any chance this'll be fixed in the future? We're an enlightened company that doesn't just use Windows and Win IE :-). (FWIW, I found that if I change my browser's user agent string to that of Firefox, the bar appears and mostly works just fine.)
14) The web site talks about an API for plugins, but the docs don't seem to have any mention of it. Where are the API docs? Or are they only available after purchase?
I recognize that some of these things (and other things that we'd like) aren't in aC and won't ever be. We're very open to customizing it to add those things. What I'm wondering about is, what's the code like? Is it heavily OO, heavily procedural, or somewhere in the middle? How well commented is it? How about things like variable naming consistency? Is the HTML separate from the PHP? Customizing always presents difficulties when it comes to application upgrades, but code cleanliness and structure can make the problem better or worse; for those who've gone down this road, what's your experience been like?
I'm evaluating aC (Corporate version) for use by my company. I've been playing with the trial, but with the inability to add more sample projects, the inability to see how administration (especially user management) works across projects, and the terseness of the docs, I'm finding it difficult to develop a complete understanding of how the software works. Thus, I'm hoping you fine folks in here can help me out.
Here, briefly, is our situation. We have a handful of developers scattered around the world. All of them are managed at a high level by our CTO. What we want is for him to be able to assign entire projects to one or more developers, and then easily follow the overall progress of those projects. The developers themselves need to be able to do most of their own PM, but in such as way that there's transparency so that the CTO may follow along. Additionally, some developers will be getting small teams underneath them, and those lead developers should be able to perform CTO-like management over their own teams. That's the gist of our situation; here are some specific questions and requirements in no particular order:
1) Projects need to have tasks, and tasks need to have sub-tasks. All tasks need to have the option of being tracked through a series of phases (like "Coding" or "Awaiting Change Management").
2) Each task needs to have the ability to have associated notes and comments stored with it.
3) It doesn't appear to be possible to specify milestones without dates. Doing so would be helpful for us in many cases because a lot of our smaller projects are done on an as-time-permits basis. In these cases, there are no deadlines, and no way to make even slightly educated guesses about deadlines, and yet, it'd be nice to still follow these projects through a series of milestones. Is stripping this requirement in the code a large modification (i.e., it would require changes in several places and affect database integrity)? Or is this a change already planned for a future version?
4) When dates are used on milestones, and you change one of them, it'd be nice to have the option of having aC automatically push the subsequent ones back by the same amount of time.
5) I'd like to be able to attach files and comments to any object, but this doesn't seem to be possible.
6) It'd be nice to be able to easily reference other objects in comments, and have aC automatically make the references into links. A similar feature can be found in Bugzilla, where, for example, you can refer to "bug 6 comment 2" in a comment, and Bugzilla will automatically make the phrase a link to the referenced bug and comment. This would be a nice future addition.
7) For the CTO and team leader roles, we need easy ways to see the overall status of all projects (% complete, ETA if available, etc.), the tasks that everyone is working on, and the status of those tasks (% done or phase ["Coding", etc.]). How are these goals best accomplished in aC?
8)How does one create subtasks on tasks? I'd like to reflect inter-task dependencies.
9) We'd like to have some basic integration between our PM system and our corporate wiki. In particular, when we create a project, we want a project page created in the wiki, with the link readily available wherever it makes sense in the system. Additionally, we want to optionally create a new wiki page for each task, and put a link to it on the parent project's wiki page. And again, we want the tasks' wiki links visible in the PM system where it makes sense.
10) What's the best way to support a sign-off process? When a developer completes a task, we want them to mark it as waiting for a sign-off, then have the team leader do a code review or whatever other checks are necessary before doing the actual deployment.
11) Elsewhere in the company, we're using Gemini, another PM system. We have some hooks for our SVN system that catch Gemini task references in commit comments (e.g., "gem:367" to refer to task number 367), then create comments on the Gemini task that includes the commit message as well as a list of the files effected by the commit. Is there anything out there that would provide a similar integration between aC and SVN?
12) Is there a way to get data out of aC, like an XML export method?
13) I've noticed that the formatting toolbar for text fields doesn't support Safari or its many derived browsers (like OmniWeb). Any chance this'll be fixed in the future? We're an enlightened company that doesn't just use Windows and Win IE :-). (FWIW, I found that if I change my browser's user agent string to that of Firefox, the bar appears and mostly works just fine.)
14) The web site talks about an API for plugins, but the docs don't seem to have any mention of it. Where are the API docs? Or are they only available after purchase?
I recognize that some of these things (and other things that we'd like) aren't in aC and won't ever be. We're very open to customizing it to add those things. What I'm wondering about is, what's the code like? Is it heavily OO, heavily procedural, or somewhere in the middle? How well commented is it? How about things like variable naming consistency? Is the HTML separate from the PHP? Customizing always presents difficulties when it comes to application upgrades, but code cleanliness and structure can make the problem better or worse; for those who've gone down this road, what's your experience been like?
Ilija Studen
on Feb 9. 2008. 7:58 am
1. Projects can have unlimited number of tickets and every ticket can have unlimited number of subtasks. There is no custom status - only open and completed.
2. Tickets have long description field and can have comments. You can also attach as many files as you wish and much more. Subtasks do not offer this functionality and can have only task text, priority, time when the task is due and one or more assignees (optional).
3. If there is no date associated with a task than it's not a milestone. Create a ticket and leave due date blank.
4. activeCollab can do this on Reschedule milestone form
5. This is not possible for any object, but it is for most (Pages, Tickets, Files etc)
6. Not possible but we'll consider introducing this in one of the upcoming releases
7. Overall project progress is listed on the dashboard and on projects page. In order to see how things are progressing in more details person needs to access the project and check tickets or milestones page.
8. You can try it out in the demo - go to tickets and create one new ticket. On ticket details page click New Task. After first task is created you'll be able to define more subtasks directly from the list.
9. activeCollab is extensible and can be integrated with other applications if you have PHP programming skills. However, you will need to wait for v1.1 to be released for this system to be documented (currently you need to analyze existing modules in order to see how the system is working).
10. Not possible. As I mentioned before, there is only open - completed states. Person who is responsible for verification can subscribed to ticket and get notified when it is completed. Then he or she can check it out and if everything is OK leave it completed or reopen it with a comment. This process can work only for tickets, not for subtasks because subtasks do not support email notifications just yet (this feature is already implemented in development branch but I really cannot promise when it will be available).
11. See #9.
12. Not currently but you have access to the database so you can export anything you want in any format you need.
13. Visual editor is not working on any WebKit powered browsers and you said the reason - it mostly works. Mostly in this case is not good enough so we disabled it for Safari. If you are on a Mac and need this functionality use Firefox.
14. API docs will be prepared for launch of v1.1 as I mentioned above. Here is why. Sorry :(
Code is OO, but PHP4 compatible so we had to make some compromises. It is well documented (docblocks). We strongly recommend that you use an editor that can understand inline documentation and provide you with a code completion (Zend Studio for example). activeCollab works really well with such an editor and cna save you a ton of time. Presentation layer is completely separated and handled by Smarty.
2. Tickets have long description field and can have comments. You can also attach as many files as you wish and much more. Subtasks do not offer this functionality and can have only task text, priority, time when the task is due and one or more assignees (optional).
3. If there is no date associated with a task than it's not a milestone. Create a ticket and leave due date blank.
4. activeCollab can do this on Reschedule milestone form
5. This is not possible for any object, but it is for most (Pages, Tickets, Files etc)
6. Not possible but we'll consider introducing this in one of the upcoming releases
7. Overall project progress is listed on the dashboard and on projects page. In order to see how things are progressing in more details person needs to access the project and check tickets or milestones page.
8. You can try it out in the demo - go to tickets and create one new ticket. On ticket details page click New Task. After first task is created you'll be able to define more subtasks directly from the list.
9. activeCollab is extensible and can be integrated with other applications if you have PHP programming skills. However, you will need to wait for v1.1 to be released for this system to be documented (currently you need to analyze existing modules in order to see how the system is working).
10. Not possible. As I mentioned before, there is only open - completed states. Person who is responsible for verification can subscribed to ticket and get notified when it is completed. Then he or she can check it out and if everything is OK leave it completed or reopen it with a comment. This process can work only for tickets, not for subtasks because subtasks do not support email notifications just yet (this feature is already implemented in development branch but I really cannot promise when it will be available).
11. See #9.
12. Not currently but you have access to the database so you can export anything you want in any format you need.
13. Visual editor is not working on any WebKit powered browsers and you said the reason - it mostly works. Mostly in this case is not good enough so we disabled it for Safari. If you are on a Mac and need this functionality use Firefox.
14. API docs will be prepared for launch of v1.1 as I mentioned above. Here is why. Sorry :(
Code is OO, but PHP4 compatible so we had to make some compromises. It is well documented (docblocks). We strongly recommend that you use an editor that can understand inline documentation and provide you with a code completion (Zend Studio for example). activeCollab works really well with such an editor and cna save you a ton of time. Presentation layer is completely separated and handled by Smarty.
activeCollab team member
First, thanks for all the information! Just a couple of clarifications....
This an important one for us. How much effort do you think it would take to add this, assuming a programmer who has strong PHP skills (and yes, a good IDE) but isn't familiar with the code? And would the nature of the changes make upgrading overly difficult in the future? Put another way, would there be changes scattered all over the place?
Any estimates on when 1.1 might be released?
Ilija Studen:1. Projects can have unlimited number of tickets and every ticket can have unlimited number of subtasks. There is no custom status - only open and completed.
This an important one for us. How much effort do you think it would take to add this, assuming a programmer who has strong PHP skills (and yes, a good IDE) but isn't familiar with the code? And would the nature of the changes make upgrading overly difficult in the future? Put another way, would there be changes scattered all over the place?
9. activeCollab is extensible and can be integrated with other applications if you have PHP programming skills. However, you will need to wait for v1.1 to be released for this system to be documented (currently you need to analyze existing modules in order to see how the system is working).
Any estimates on when 1.1 might be released?
Ilija Studen
on Feb 11. 2008. 5:29 pm
Completion status is one of the "system" things - entire system is based on an assumption that tasks (tickets, milestones, checklists, subtasks - all types of "completable" objects) have only two states - open and completed. I haven't actually put much thought in what would it take to implement such feature, but from possible implementations that cross my mind now I don't see an easy and clean way to do it.
Easy trick would be to simply put status in ticket summary - like '[DELAYED] Do this and that' or '[CANCELED] Implement this or that'...
More on v1.1 can be found here.
Easy trick would be to simply put status in ticket summary - like '[DELAYED] Do this and that' or '[CANCELED] Implement this or that'...
More on v1.1 can be found here.
activeCollab team member
andrewCharron
on Feb 12. 2008. 1:34 pm
Ilija Studen:3. If there is no date associated with a task than it's not a milestone. Create a ticket and leave due date blank.
I tend to not agree on this one. Sometimes a milestone cant start until the customer says, and therefore no date can be set immediatly. However, one might want to put all milestones, checklists and tasks into the project. Dates being optional should be allowed.



