People management should be people-centric
Page: 1
Recent posts in this topic
Instead of adding people to projects, we should be able to add projects to people (also). It's more logical in the sense that you want to define what projects someone has access to, as a person.
Right now, when someone new pops up, you have to manually add to each project from within each project, which is just too time consuming if you are running a lot of projects. It's a bit like booking a trip for someone and going down to the airport, the hotel, the car rental service etc. yourself to add the person to their lists instead of just arranging the schedule for that person.
At the current rate, at least once a week I lose half an hour adding someone new to all our projects. That's just crazy. And given the fact that our project numbers increase constantly, the amount of lost time is bound to increase in the future.
Is this addressed in 1.1? If not, (when) will it be addressed?
Right now, when someone new pops up, you have to manually add to each project from within each project, which is just too time consuming if you are running a lot of projects. It's a bit like booking a trip for someone and going down to the airport, the hotel, the car rental service etc. yourself to add the person to their lists instead of just arranging the schedule for that person.
At the current rate, at least once a week I lose half an hour adding someone new to all our projects. That's just crazy. And given the fact that our project numbers increase constantly, the amount of lost time is bound to increase in the future.
Is this addressed in 1.1? If not, (when) will it be addressed?
www.synergetics.be | www.davor.be
Ilija Studen
on May 16. 2008. 11:38 am
Davor:Is this addressed in 1.1? If not, (when) will it be addressed?
What you are asking for is not present in activeCollab 1.1. We'll consider it for future releases, but I really cannot promise anything at moment.
activeCollab team member
lemonadesoda
on May 19. 2008. 11:11 pm
This is a very sensible suggestion by the user. One can think of it this way:
1./ If you have a few BIG projects, with lots of people on each project, it's intuitive to work with the "project" as being the more senior element in the permissions hierarchy, but
2./ If you have lots of SMALL projects, with just one or a few people on each project, but the same person(s) are on many projects at the same time, it's intuitive to work with the "person" as the relevant point for managing permissions.
This is what we are. We are a small training company. We have a team of 6 people. We do approximately 150 "training projects" each year, across about 10 clients. Please put this feature onto the *hot list*. IMO, it is an important productivity issue for the people administering people/projects.
PS. I came across aC for the first time today. I'm investigating this (and other) software as our management tool. Looks great so far! But I registered just a minute ago to support this topic, because adminstrative burden is a "deal maker/breaker" for us.
1./ If you have a few BIG projects, with lots of people on each project, it's intuitive to work with the "project" as being the more senior element in the permissions hierarchy, but
2./ If you have lots of SMALL projects, with just one or a few people on each project, but the same person(s) are on many projects at the same time, it's intuitive to work with the "person" as the relevant point for managing permissions.
This is what we are. We are a small training company. We have a team of 6 people. We do approximately 150 "training projects" each year, across about 10 clients. Please put this feature onto the *hot list*. IMO, it is an important productivity issue for the people administering people/projects.
PS. I came across aC for the first time today. I'm investigating this (and other) software as our management tool. Looks great so far! But I registered just a minute ago to support this topic, because adminstrative burden is a "deal maker/breaker" for us.
+0.5. Sure would be nice, but if not simple to implement, there are a hundred other things I'd like ;P
Although the new system roles concept is good, the new user management just introduced a minimum extra click to the process... 9 clicks X number of projects now to add a single user :-(
To demonstrate: I added one new user to 25 of our projects, which means I clicked 225 times. Luckily she did not need access to all our projects and no custom permissions either, or it would have easily gone to 500+ clicks... For ONE user!
So I'm moving this back to the top of the feature requests.
To demonstrate: I added one new user to 25 of our projects, which means I clicked 225 times. Luckily she did not need access to all our projects and no custom permissions either, or it would have easily gone to 500+ clicks... For ONE user!
So I'm moving this back to the top of the feature requests.
www.synergetics.be | www.davor.be
+1
At the moment I've just completed a project that was along the lines of 'Identity creation for x company' where we created a logo. The final logo was uploaded to the files section for this project. Now a new project is created (called 'brochure design') ... a key file for this project is the logo, but to get it I have to go back to the previous project file section and download it.. This just seems a bit cumbersome.
If the logo was added to a 'people-centric' files section, we could organise files better (ie, People/Company > Files > Categories (Logos, Stationary, etc.) which would save us a lot of time, and also serve as a resource for clients to login and easily get files when they need them.
Also, as others have mentioned, we do many small tasks too that don't warrant its own project. People-centric management sounds like the right solution for this issue...
At the moment I've just completed a project that was along the lines of 'Identity creation for x company' where we created a logo. The final logo was uploaded to the files section for this project. Now a new project is created (called 'brochure design') ... a key file for this project is the logo, but to get it I have to go back to the previous project file section and download it.. This just seems a bit cumbersome.
If the logo was added to a 'people-centric' files section, we could organise files better (ie, People/Company > Files > Categories (Logos, Stationary, etc.) which would save us a lot of time, and also serve as a resource for clients to login and easily get files when they need them.
Also, as others have mentioned, we do many small tasks too that don't warrant its own project. People-centric management sounds like the right solution for this issue...
Well, my thoughts are that rather than focusing on this particular issues, there might be some attention paid to a systematic overview of user interactions and tasks narratives in aC.
Want to unassign/unsubscribe someone from a project, or change the responsible party? I'm not going to count, but Edit-click, click, click, submit, click click click click...
This shouldn't require going to a separate page, just for instance. I should be able to do this from the frontpage of a ticket, ideally, via drag-and-drop or such.
Per above, much of the UI interactions in aC require multiple-page interactions where they could be consolidated onto a single page/interface. Adding a client co/people/ people to projects is just slow, whether people-centric or project-centric.
In the end, a little more "data normalization" :) and ability to see the data/projects/people/tasks/lists/etc from any conceivable view, and manipulate/add as you wish, would seem the direction to work towards.
K
Want to unassign/unsubscribe someone from a project, or change the responsible party? I'm not going to count, but Edit-click, click, click, submit, click click click click...
This shouldn't require going to a separate page, just for instance. I should be able to do this from the frontpage of a ticket, ideally, via drag-and-drop or such.
Per above, much of the UI interactions in aC require multiple-page interactions where they could be consolidated onto a single page/interface. Adding a client co/people/ people to projects is just slow, whether people-centric or project-centric.
In the end, a little more "data normalization" :) and ability to see the data/projects/people/tasks/lists/etc from any conceivable view, and manipulate/add as you wish, would seem the direction to work towards.
K
