Support Forum

[PavelKolarik]

I would very appreciate the new feature:
The category of a task could be changed by a user under these conditions:
a/ Both categories use the same workflow
b/ Category relation rules allow the new category to be contained in the task's parent

We need quite often to change a task's category eg. from Bug to Request, or from Request to ToDo as the task's history evolves and we want to keep the meaning of the categories. This feature would be nice for us.

[admin]

This feature can lead to security issue. Suppose, user can create/edit tasks, but not projects. With this feature available, users can create "bug" (he can), and then edit it (also can), and set category "project". But he cannot save project, and TrackStudio will crash.

So, you can change category with SQL when TrackStudio stopped, but not using web GUI.

[a-b-c]

Why not? Because of the first criteria (both categories use the same workflow) bug won't be converted to project.
Yes, there is a potential security problem when bugs and projects share the same workflow, but in my opinion advantages of such a feature outweigh that problem.

[PavelKolarik]

So, you can change category with SQL when TrackStudio stopped, but not using web GUI.

Yes, I do change it this way. That exactly why I am asking for the feature

Suppose, user can create/edit tasks, but not projects. With this feature available, users can create "bug" (he can), and then edit it (also can), and set category "project". But he cannot save project, and TrackStudio will crash.

It is just a matter of validation, is not it? If you have good programmers, TrackStudio cannot crash in a situation like this.

[admin]

It is just a matter of validation, is not it? If you have good programmers, TrackStudio cannot crash in a situation like this.

It's very deep architecture feature. If user has no access to the task, he cannot reach it using SOAP, scripts/triggers, e-mail templates, and TrackStudio cannot finish operation in this case without error.

[PavelKolarik]

It's very deep architecture feature. If user has no access to the task, he cannot reach it using SOAP, scripts/triggers, e-mail templates, and TrackStudio cannot finish operation in this case without error.

Yes Maxim, I can understand that as we are also developers of enterprise SW systems But:
a/ It a difference between "finishing with an (handled) error" and "crashing"
b/ I think the list of possible new categories offered to the user can contain only "problem-less" categories (the same workflow, category relation rules OK, the user has "create" permission to the new category, etc...)