Support Forum

[Andy]

Can I setup the default handler for new tasks and bugs to be the submitter?

[admin]

Can I setup the default handler for new tasks and bugs to be the submitter?

Currently default handler for new tasks is handler of the parent task. Possible you should create several subprojects and set handler for each of them.

[Andy]

Perhaps, but it's quite cumbersome because you cannot set the handler when creating a task -- you have to add a message. This seems to be an unnecessary restriction.

[admin]

Perhaps, but it's quite cumbersome because you cannot set the handler when creating a task -- you have to add a message. This seems to be an unnecessary restriction.

OK, agree. Possible, we'll implement it in the next version

[admin]

Perhaps, but it's quite cumbersome because you cannot set the handler when creating a task -- you have to add a message. This seems to be an unnecessary restriction.

OK, agree. Possible, we'll implement it in the next version

Done, enjoy

[victor]

Perhaps, but it's quite cumbersome because you cannot set the handler when creating a task -- you have to add a message. This seems to be an unnecessary restriction.

OK, agree. Possible, we'll implement it in the next version

Done, enjoy :-)

done? what do you mean? have you done this improvement?

(expectant silence)

[admin]

Perhaps, but it's quite cumbersome because you cannot set the handler when creating a task -- you have to add a message. This seems to be an unnecessary restriction.

OK, agree. Possible, we'll implement it in the next version

Done, enjoy

done? what do you mean? have you done this improvement?

(expectant silence)

Yes, it is available in Beta 3 (available to download and at TrackStudio Host).
When you create new task, you can choose handler from the list of available handlers. The handler of parent task should be default handler.

The available handler = handlers that has access to the task and can move task from start state to some state.

And some restriction - now you can't change task category after you click the "add" button. We found that this cause many cumbersome (logical) problems. Suppose, you can create "bug", and can't create "task" (defined by settings in Edit Category). Both use "Default" workflow.
Early you can create "bug", and change category to "task", because you can create/modify "bug" and task has the same workflow as bug.

Another sample - developer can process "bug" in some state, but can't process "task" in the same state. After somebody change category from "bug" to "task" - we got bug that handler can't process.

[victor]

Great! :) I am anxious to enjoy the TrackStudio 2.8. Thanks for your enforcement.

[Andy]

Looks great, thanks. Also, the speed is much better for adding tasks.

[victor]

And some restriction - now you can't change task category after you click the "add" button. We found that this cause many cumbersome (logical) problems. Suppose, you can create "bug", and can't create "task" (defined by settings in Edit Category). Both use "Default" workflow.
Early you can create "bug", and change category to "task", because you can create/modify "bug" and task has the same workflow as bug.

Another sample - developer can process "bug" in some state, but can't process "task" in the same state. After somebody change category from "bug" to "task" - we got bug that handler can't process.

Glups! Ok, I understand the restriction but now I have a problem.

Like the move task system is a bit poor I actually use a manual procedure to dont do every task a project and dont overload the jump to list. I use this procedure until trackstudio has a good move task solution.

Well I have defined a subproject category and practically all my projects have subproject category. I only use project category for four main folders.

Only the administrator can move tasks because the procedure is very manual.

The procedure?
- first I change the category for the new parent task and change it to project category.
- I move the task to the new parent (that now appear in the tasks list).
- Finally I come back the new parent category task to subproject.

And now?... what I can do?... could you allow to the administrator change the category of a task?

Thanks