Reparenting Categories, Workflows, etc.

Discuss problems installing or using TrackStudio.

Reparenting Categories, Workflows, etc.

Postby phancox » Sat Oct 22, 2011 10:49 am

What is the correct approach to changing the "owner" of a Category / Workflow etc.

For example, we have "Projects" ---> "Product Suite One" ---> "Product One" ---> "Support Request One" where "Projects" has category of "Folder", "Product Suite One" has category of "Product Suite", "Product One" has category of "Product", and "Support Request One" has category of "Support Request".

The "Support Request" category is currently defined within "Projects". We would like to move "Support Request" so it is defined within "Product Suite One". The reason for doing this is we want to move toward having different "Support Request" category and workflow for each "Product Suite". Technically we could probably achieve this without moving the existing categories (just create a new one for the new product suite), however, this leaves the hierarchy a bit "unclean" in its structure.

Can this type of restructure be achieved using the Web UI or does it need to be done with SQL?

How safe is it to perform this type of restructure?

Is there documentation, examples, scripts available to assist?

Our ultimate change will be a bit more complicated as we also have "Product Suite Two" that currently uses the existing "Support Request". So we actually need to move/clone the current "Support Request" into "Product Suite One", "Product Suite Two", ... "Product Suite N". Then customise each of the "Support Request" categories/workflows to be specific to the product suite.

REGARDS
Peter
phancox
 
Posts: 71
Joined: Mon Feb 27, 2006 1:14 pm
Location: Sydney, Australia

Re: Reparenting Categories, Workflows, etc.

Postby Petr » Sun Oct 23, 2011 2:08 pm

Hi. You need change only task id in gr_category table in database. Actually It is impossible to make through user interface. But you must be to sure that whole tasks which have this category, will be access for this task. I mean if you have hierarchy like this.
1.Project > is defined Categories (Project, Bug)
1.2. Task 1
1.2.1 Bug 1 > is category Bug
1.2.1 Bug 2 > is category Bug
1.3. Task 2
1.3.1 Bug 3 > is category Bug

and you want to move Category to Task 1, It will not work.

I hope it will be useful.
Regard.
TS Support
email: parsentev@yandex.ru
Petr
 
Posts: 1317
Joined: Wed Aug 12, 2009 4:38 pm

Re: Reparenting Categories, Workflows, etc.

Postby phancox » Mon Oct 24, 2011 11:13 am

I've made the changes directly to the database and everything seems to have worked OK. Mostly wanted to be sure that there wasn't any easier way.

THANKS
Peter
phancox
 
Posts: 71
Joined: Mon Feb 27, 2006 1:14 pm
Location: Sydney, Australia


Return to TrackStudio Support

Who is online

Users browsing this forum: No registered users and 0 guests