Suggestions for handling small tasks
Page: 1
Recent posts in this topic
jwtdigital
on Nov 20. 2007. 3:39 am
Hello,
A lot of our workload consists of small amends or updates, maybe a couple of hours work. It's not worth starting an entire project for these tasks so I wondered how other people might use ActiveCollab to handle smaller projects? I thought 'tickets' might be the answer but it seems there MUST be a 'parent' project before tickets can be assigned.
Ideally we would just like to open a ticket, associate it with a client and assign it to a member of staff to carry out the tasks.
Ticket/Project numbering would also be VERY useful for us.
Thanks
A lot of our workload consists of small amends or updates, maybe a couple of hours work. It's not worth starting an entire project for these tasks so I wondered how other people might use ActiveCollab to handle smaller projects? I thought 'tickets' might be the answer but it seems there MUST be a 'parent' project before tickets can be assigned.
Ideally we would just like to open a ticket, associate it with a client and assign it to a member of staff to carry out the tasks.
Ticket/Project numbering would also be VERY useful for us.
Thanks
Ilija Studen
on Nov 20. 2007. 6:31 am
A friend of ours has a project where he puts all this "small projects that are not projects" as tickets. Tickets support time tracking, can have subtasks, can be discussed, support email notifications etc. Works well for his team.
activeCollab team member
jwtdigital
on Nov 21. 2007. 5:20 am
Thanks Ilija. Unfortunately we would need a way of associating individual tickets with clients.
Since everything in AC is project-based, and all projects are linked to a single client, I doubt it will be possible, unless you create that "generic" project for every single client you manage...
cbtrussell
on Nov 26. 2007. 7:10 pm
We're planning on creating a generic 'maintenance' project for handling requests that aren't associated with a pre-existing project/development effort. Now this precludes any sort of client interaction, but for small maintenance requests, we don't need the clients to interact with aC... just a place to post tickets, assign responsibilities, etc related to the update.
We use active collab like this:
We have four projects that are used for different types of projects:
0 - Sales Order
1 - Active Tickets
2 - Completed and Paid
4 - To be invoiced
EVERYTHING IS A TICKET - We enter tickets like this:
20080524 CUSTOMER_NAME - Do something for this customer
We move tickets from "0 - Sales Order" (if it indeed is) to "1 - Active Tickets" to "2 - Completed" and Paid OR to "3 - to be invoiced"
After invoicing, we move to a historical project for the customer. It prevents enabling a customer to have access to see current active stuff but was the best workaround we could come up with at the time - because until v1.1 - we were not able to see who was assigned to what and we had a lot of little stuff coming in and did not want to go through the tedious job of setting up a new project every time the customer called on the phone.
We have four projects that are used for different types of projects:
0 - Sales Order
1 - Active Tickets
2 - Completed and Paid
4 - To be invoiced
EVERYTHING IS A TICKET - We enter tickets like this:
20080524 CUSTOMER_NAME - Do something for this customer
We move tickets from "0 - Sales Order" (if it indeed is) to "1 - Active Tickets" to "2 - Completed" and Paid OR to "3 - to be invoiced"
After invoicing, we move to a historical project for the customer. It prevents enabling a customer to have access to see current active stuff but was the best workaround we could come up with at the time - because until v1.1 - we were not able to see who was assigned to what and we had a lot of little stuff coming in and did not want to go through the tedious job of setting up a new project every time the customer called on the phone.
Ari Maniatis
on May 24. 2008. 8:55 pm
I've just purchased ActiveCollab, but just hit this roadblock too. It wasn't easy to tell from the demo online, but now I realise this limit of one client per project exists. Sure there might be a lead client, but how do we deal with contractors and others who need to be involved in a project from other companies? How does A51 set up their ActiveCollab project and assign tickets against the particular customers who reported a bug/feature request so that they can be notified when that bug is resolved?
The problem would be largely mitigated if individual tickets could be assigned to people from any company, even if the project as a whole has only one sponsor. I know this makes for a slightly complex user interface for adding people but it is essential for managing anything but the simplest client/project relationship. The flow on effect is that access rights would be required at a ticket level (that is, clients might be able to see some tickets and not others within the same project), but this would be very very useful.
The problem would be largely mitigated if individual tickets could be assigned to people from any company, even if the project as a whole has only one sponsor. I know this makes for a slightly complex user interface for adding people but it is essential for managing anything but the simplest client/project relationship. The flow on effect is that access rights would be required at a ticket level (that is, clients might be able to see some tickets and not others within the same project), but this would be very very useful.
Agreed 100%. Just purchased AC corporate and learning the ropes.
Similar issue where we have internal team, 2 different consulting organizations, and an outsourced contractor group. I'm trying to figure out how to make this work...?
Similar issue where we have internal team, 2 different consulting organizations, and an outsourced contractor group. I'm trying to figure out how to make this work...?
Ari Maniatis:I've just purchased ActiveCollab, but just hit this roadblock too. It wasn't easy to tell from the demo online, but now I realise this limit of one client per project exists. Sure there might be a lead client, but how do we deal with contractors and others who need to be involved in a project from other companies? How does A51 set up their ActiveCollab project and assign tickets against the particular customers who reported a bug/feature request so that they can be notified when that bug is resolved?
The problem would be largely mitigated if individual tickets could be assigned to people from any company, even if the project as a whole has only one sponsor. I know this makes for a slightly complex user interface for adding people but it is essential for managing anything but the simplest client/project relationship. The flow on effect is that access rights would be required at a ticket level (that is, clients might be able to see some tickets and not others within the same project), but this would be very very useful.
http://www.linkedin.com/in/chrisduncan1
Ilija Studen
on Jul 17. 2008. 8:13 am
If you wish to have multiple clients on one project, but don't want them to be able to see each other than it's not possible. Instead, use a separate project for interaction with every client.
activeCollab team member
