Marks Tasks as 'Hey, I will do it'
Page: 1
"Question" because I don't know if has been thought about or will be implemented etc...
a)
Usage Scenario: Smaller Team of people, up to 20-30, organizing various projects of different kind.
One admin, who can start projects. (We're looking forward to the implementation of the "allowed to start projects"-rights)
Everybody else contributes, whereever he can.
Sometimes we contribute ideas of what could be done and put it on a task-list, with assigning a name yet.
Question:
Is there a feature that allows us to collect tasks at random - and then allows every user to voluntarily take up any of the tasks? Like marking it "Oh, hey, I will do, you don't bother..." ???
That would be awesome - in combination with b) an Overview of tasks to be done by whom (no idea, what would be the best way to do this)
Just some ideas.
a)
Usage Scenario: Smaller Team of people, up to 20-30, organizing various projects of different kind.
One admin, who can start projects. (We're looking forward to the implementation of the "allowed to start projects"-rights)
Everybody else contributes, whereever he can.
Sometimes we contribute ideas of what could be done and put it on a task-list, with assigning a name yet.
Question:
Is there a feature that allows us to collect tasks at random - and then allows every user to voluntarily take up any of the tasks? Like marking it "Oh, hey, I will do, you don't bother..." ???
That would be awesome - in combination with b) an Overview of tasks to be done by whom (no idea, what would be the best way to do this)
Just some ideas.
Ok, I'll see if this is easy enough to communicate to team members....
* If you assign tasks to "anyone", this makes the process kind of unclear, as you don't really know who is even considering doing it.
* Maybe one could label a task something like "Not assigned YET. (Will you do it?)". This should somehow be clearly be visible: This task is waiting for someone to do it.
* As a next step each of these tasks (not assigned yet) could come with a little extra button saying "I'll do it" instead of having to edit it. This should be an easy thing to script, isn't it? (Even though I can't do it, sorry)
All this does not consider your planned improvements regarding future tasks and to-do's - I have now idea how these will look...
cheers
* If you assign tasks to "anyone", this makes the process kind of unclear, as you don't really know who is even considering doing it.
* Maybe one could label a task something like "Not assigned YET. (Will you do it?)". This should somehow be clearly be visible: This task is waiting for someone to do it.
* As a next step each of these tasks (not assigned yet) could come with a little extra button saying "I'll do it" instead of having to edit it. This should be an easy thing to script, isn't it? (Even though I can't do it, sorry)
All this does not consider your planned improvements regarding future tasks and to-do's - I have now idea how these will look...
cheers
Well, if I'm the only one asking about this - bad luck for me I guess ;-)
Thanks...
Thanks...
viceroy321
on Feb 12. 2007. 12:35 pm
I believe this may be another instance of the "sub-department of owner company"-issue, or at least something similar.
you can currently assign a task to either the owner company or to a user of the owner company.
you can neither assign a task to a client company nor to a user of a client company.
you can not split the owner company into departments.
if (as was proposed some time ago) aC would include two new user groups: "departments" (parts of the owner company) and "subcontractors" (freelancers working for the owner company or other companies) floxk's problem would be (kind of) solved.
-------------------
as a workaround/hack/whatever:
make ActiveCollab cry out that a task is unassigned:
go to application\views\task\task_list.php and search for the following
<!-- Task text and options -->
<td class="taskText">
<?php if($task->getAssignedTo()) { ?>
<span class="assignedTo"><?php echo clean($task->getAssignedTo()->getObjectName()) ?>:</span>
<?php } // if{ ?>
then replace it with
<!-- Task text and options -->
<td class="taskText">
<?php if($task->getAssignedTo()) { ?>
<span class="assignedTo"><?php echo clean($task->getAssignedTo()->getObjectName()) ?>:</span>
<?php }else{ ?>
<span class="assignedTo">Free for Grabs:</span>
<?php } // if{ ?>
I concede, it is a brute force solution, but if you don't like it, you can easily disable it again, by replacing it with the original: nothing has happened.
you can currently assign a task to either the owner company or to a user of the owner company.
you can neither assign a task to a client company nor to a user of a client company.
you can not split the owner company into departments.
if (as was proposed some time ago) aC would include two new user groups: "departments" (parts of the owner company) and "subcontractors" (freelancers working for the owner company or other companies) floxk's problem would be (kind of) solved.
-------------------
as a workaround/hack/whatever:
make ActiveCollab cry out that a task is unassigned:
go to application\views\task\task_list.php and search for the following
<!-- Task text and options -->
<td class="taskText">
<?php if($task->getAssignedTo()) { ?>
<span class="assignedTo"><?php echo clean($task->getAssignedTo()->getObjectName()) ?>:</span>
<?php } // if{ ?>
then replace it with
<!-- Task text and options -->
<td class="taskText">
<?php if($task->getAssignedTo()) { ?>
<span class="assignedTo"><?php echo clean($task->getAssignedTo()->getObjectName()) ?>:</span>
<?php }else{ ?>
<span class="assignedTo">Free for Grabs:</span>
<?php } // if{ ?>
I concede, it is a brute force solution, but if you don't like it, you can easily disable it again, by replacing it with the original: nothing has happened.
wow Viceroy,
the code looks great - I'll try it later.
Just from looking on your code, I miss on last piece for my happiness:
A little button, or whatever for that matter, that cries out "Ok, I will do it" - taking your code a step further.
1. the task is assigned. fine, perfect
2. the task is not assigned - "Free for Grabs" is displayed.
3. clickable "Free for Grabs" - a shortcut to manipulating the database, to assign this task to the user clicking the link. (Sorry, I haven't got into the aC-code that much yet, to write this last piece myself, but shouldn't really be tooooo difficult... ??)
RE departments and subcontractors:
No, I wouldn't go that far - we would be totally happy with this - but I don't know about other usage scenarios.
We use it for projects, where sometimes someone from the team simply has to step up and say "Ok, I'll do the shopping" or whatever....
Thanks for your thoughts
the code looks great - I'll try it later.
Just from looking on your code, I miss on last piece for my happiness:
A little button, or whatever for that matter, that cries out "Ok, I will do it" - taking your code a step further.
1. the task is assigned. fine, perfect
2. the task is not assigned - "Free for Grabs" is displayed.
3. clickable "Free for Grabs" - a shortcut to manipulating the database, to assign this task to the user clicking the link. (Sorry, I haven't got into the aC-code that much yet, to write this last piece myself, but shouldn't really be tooooo difficult... ??)
RE departments and subcontractors:
No, I wouldn't go that far - we would be totally happy with this - but I don't know about other usage scenarios.
We use it for projects, where sometimes someone from the team simply has to step up and say "Ok, I'll do the shopping" or whatever....
Thanks for your thoughts
Topic is locked. If you have something important to say about issues discussed on this page please write at hi@a51dev.com.



