Sub queues

[aeg]

I have 13 queues that I need to create, under each of those queue I need to create 22 subqueues.
That is 299 queue that is too much.

do you have any other ideas how i can mark tasks instead of creating all thoses sub queues?

[nedmaj]

I have 13 queues that I need to create, under each of those queue I need to create 22 subqueues.
That is 299 queue that is too much.

do you have any other ideas how i can mark tasks instead of creating all thoses sub queues?

What you mean when you say "mark tasks"? Could you explain a little more about that?

[aeg]

Basicly what I'm trying to say is I need to "mark" department(queue) when I create ticket and mark project there under (subqueue?)
or is it better to just create a dynamic fields for all that?

Then I need to be able to search for these field, based on project and department.

hope you understand what I mean.

[reneeb]

You should use DynamicFields for that. You can use those fields in the ticket search as well...

[nedmaj]

Basicly what I'm trying to say is I need to "mark" department(queue) when I create ticket and mark project there under (subqueue?)
or is it better to just create a dynamic fields for all that?

Then I need to be able to search for these field, based on project and department.

hope you understand what I mean.

Use queues as departments = ok.

Use queues as projects = sure not.

Projects are temporary. Better use another field for projects, maybe a dynamic field, or maybe a remote db dynamic field pointing to your projects database.

[crythias]

Queues are for groups of agents able to handle tickets in that category.
Don't use customer or task or project based Queues.
Use Services for what the Agents are servicing.