Park work in a team queue

Tilgjengelig i alle planerSlik gjør duÅpne i DealJourney

Some work belongs to a department before it belongs to a person. An ad that has to be produced is ready for graphics long before anyone decides which designer will draw it.

For that, give the work a team queue instead of an owner. The activity waits in the queue, everyone can see it, and the moment somebody is set as the Ansvarlig it leaves the queue and becomes their job.

A queue is an ordinary team, so it costs you nothing. You do not need to create a user account for the department, and nobody has to log in as it.

Set up the queue

Create the team once, under team management in the admin settings, and name it the way the department is actually called. That name is what everyone will see on the activity, so "Graphics" beats "Team 3". The team does not need any members: a queue is a place to put work, not a group of people.

Park work in it

  1. 1Open Aktiviteter from the sidebar.
  2. 2Create the activity as usual (Add an activity).
  3. 3In the assignment section, set Teamkø to the department that should hold it.
  4. 4Leave the Ansvarlig empty. That is what makes it *waiting* rather than somebody's job already.
  5. 5Save.

Move work that already exists

Work does not have to start in a queue. You can park an activity that already exists, one at a time or many at once.

One activity. Open it and find Teamkø under Ansvarlig. Pick the department, and it is saved straight away. Choose Ingen kø to take it out of the queue again.

Setting a queue here does not remove whoever is assigned, because somebody may already be working on it for that team. While a person is assigned, the activity belongs to the team but is not *waiting*, and the page says so under the field. Remove the Ansvarlig if you want it to wait in the queue.

Many activities. On the Aktiviteter page, tick the activities you want to move, open the bulk actions and choose Flytt til kø. Pick the queue and confirm. This does both steps in one go: the activities get the queue, and whoever was assigned is taken off, so they really do land in the queue as waiting. You need permission to mass update activities to use it, and anything you are not allowed to edit is left as it was.

From an import. A whole file of new activities can go straight into a queue, for example a batch of prospects you are about to email before anyone knows which seller takes each one. See Create many activities or deals from one file.

This is also the way to retire a stand-in user. If you have been parking work on a made-up person named after a department, filter the list on that person, select everything, and move it to the real queue.

See what is waiting

On the Aktiviteter page there is a queue filter beside the time and status filters. It lists every team with the number of items waiting on it, so the person running the department can read the backlog at a glance and open it in one click:

  • Alle tildelinger ignores queues entirely, which is the normal list.
  • Venter i en kø shows everything sitting in any queue, across all departments.
  • Picking a team shows only that queue.

The Kø column shows which queue each activity is waiting in. Turn it on from the column controls if you do not see it.

Everything else on the list behaves as it always does, so filters, saved views and export all work here too (Filter a list).

Hand it to somebody

Picking work up is an ordinary assignment. Set the Ansvarlig on the activity, either from the list or on the activity itself, and it stops counting as waiting straight away.

The team stays recorded on the activity, so you can still see which department the job came from after a designer has taken it. Only the count changes, which is the point: the queue is a list of work nobody has started.

What a queue is not

A queue is not an owner, and it is not a way of assigning work to several people at once. Nobody is notified when work lands in a queue, because nobody in particular is responsible for it yet. Somebody has to look. If work must reach a specific person, give it an Ansvarlig instead.

Var dette nyttig?

Relatert