Queues are showing the requests based on the place they're on in the life cycle. This is useful because (a) helps in prioritizing the effort, (b) you know how to move things forward in the request's flow and (c) it follows the COS checklist.
Full list of queues in inbox:
New Request
--- Operations ---
New Message
Pre-delegation
Delegation
Waiting for QA
Final Response
Completed
--- Freestyle ---
New Message
COS
Delegation
Waiting for QA
Final Response
Completed
—————
New Request
Request status: New
AND
Gig status: N/A "no linked gig"
--- Operations ---
New Message
This queue is unique - every request here appears in a second queue as well (based on the different statuses).
Owner: Operations
Request status: all except for new
Unread message (Rules: An unread message from a user. Once an admin user reads it (assigns to self), it removes it from this queue. If an admin user clicks on "mark conversation as unread", it should get it back to the queue.)
Pre-delegation
Gig status: Pre-Delegation
Owner: Operations
Delegation
Gig status: Delegated
Owner: Operations
Waiting for QA
Gig status: QA
Owner: Operations
Final Response
Gig status: Final Response
Owner: Operations
Completed
Request status: Completed
Owner: Operations
--- Freestyle ---
New Message
This queue is unique - every request here appears in a second queue as well (based on the different statuses).
Owner: Freestyle/specific person
Request status: all except for new
Unread message (Rules: An unread message from a user. Once an admin user reads it (assigns to self), it removes it from this queue. If an admin user clicks on "mark conversation as unread", it should get it back to the queue.)
COS
Gig status: COS
Owner: All
Delegation
Gig status: Delegated
Owner: Freestyle/specific person
Waiting for QA
Gig status: QA
Owner: Freestyle/specific person
Final Response
Gig status: Final Response
Owner: Freestyle/specific person
Completed
Request status: Completed
Owner: Freestyle/specific person