Let me know how it goes!

Any advise in how to fix this?

BTW, Tickets Plus will be out as a module with some interesting updates in coming week!

Thanks for adding the subscription plugin, hope it makes your site stickier than it already is!

1. Thanks!

2. You can edit tickets_plus_config.php in config folder to add / edit workflow statuses. There is no admin for it yet.

3. Hmm.. Ok.

5. It will be good to see how people use aC. You may want to try using Pages / Discussions for persistent information. I’ve found discussions can too work well if you want to avoid pages.

BTW, just added comment subscribing plugin!

:Nirav

+1! Massive props for the Men in Black reference, very creative indeed. I will spread the video far and wide when it comes out 😉

Thanks for the detailed responses too:

1. We use tickets 95% of the time but use aC for both departmental tasks and project tasks. This module and the next version of tickets plus will make our lives so much easier.

2. Ahh ok. I didn’t even realise Tickets plus added those workflow statuses, thought it came with aC. Is there an admin way of changing the workflow values without changing the DB?

3. Given that we use aC for departmental file storage as well, files just don’t give us the organisational flexibility. We prefer to attach them to the relevant ticket and use aC as a pseudo ECM/Document management system.

5. For persistent information we prefer to use tickets without a due date and just keep it open. In that sort of project, milestones serve more of a subfolder/organisational role than their original purpose. If tickets plus ever gets versioning ticket descriptions and versioning ticket attachments then we’d have no use for files and pages (given point 3 for persistent items). I’d the majority of your customers will act in a similar way based on my conversations with other aC’ers

Cheers,
Shaz

P.S Could you add the comment subscribe plugin for WP? Didn’t realise you had made a response until I randomly viewed the same post again.

Watch out for more…

So this has finally become “Confidential Items Module + Hack for activeCollab”! After a lot of back and forth, iterating over different solutions, I zeroed in on a combination of a module and some core hacks to activeCollab.

The module will allow making almost any project object confidential though. So you can make a ticket / page / discussion confidential. A confidential item will be visible only to people subscribed or assigned to it – or the administrator. All comments, tasks, file attachments to a confidential item will remain confidential too. And yes, even time records will remain confidential!

So you won’t need any agreements modules or private comment modules or anything that does half the job! You will now have a native, familiar way to protect items you want to!

This work is not going to be full proof though. I wanted to minimize the number of core files I needed to change. So I have omitted showing confidential items at a few places – e.g. in Recent Activities or Time Reports etc. But I feel this is still a powerful solution.

More details soon..

:Nirav