queues are simply filtered lists so you don't really 'move' them to a queue. Rather you construct your queues to align w/ what you are trying to do. For example, you could have queues by facility or agent or issue type, etc. What do your queues represent? We use a Triage queue for all unassigned issues. All agents monitor this queue to keep it empty. When they take ownership it goes into their queue.
@Staci Cavalcante, i'm a bit confused but maybe i understand your question. Whether the "queues underneath" total to the one above is completely up to how you set them up. Lets look at some examples that may help you understand.
By default you should have an "All Open" queue unless you deleted. For me the JQL is - resolution = Unresolved ORDER BY created DESC, "Time to resolution" ASC
So lets say I then create three new queues, one for each of my agents: Fred, Sally, Jose that show their open issues.
Then assume we see the following numbers when we look at these four queues:
All Open (65)
So 27+13+10 only = 50 so where are my other 15? Well based on my queue definitions they must be either "unassigned" or assigned to someone else.
In otherwords queues are filters and anytime you construct filters the sum of the parts will only add up to the whole IF you have ever condition factored into your filters.
Bottomline - construct your queues to work the way the team works or needs to work. BUT be sure not to leave any issue hidden.
sorry if this was off base from your question.
...be more productive while being fun to use at the same time. For some, getting started can be a bit intimidating. This is especially true if Jira Service Desk is your first exposure to Atlassian...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs