Module quiz

1. To designate the project as a request queue and define who can submit requests.
2. To create routing rules for assigning requests to teams.
3. To organize queue topics into topic groups.
4. To set up dashboards for monitoring incoming requests.

1. To group similar requests into categories.
2. To automatically assign requests to teams, job roles, users, or projects.
3. To create custom forms for collecting information.
4. To set the default duration for requests.

1. It is automatically converted into a project.
2. It is sent directly to the assigned team member.
3. It is stored in the Issues tab of the associated request queue project.
4. It is deleted if not assigned within 24 hours.

1. By allowing users to submit requests anonymously.
2. By limiting the number of requests submitted each day.
3. By centralizing all requests and automatically assigning them to the right people.
4. By converting all requests into tasks.

1. Creating a naming convention for request queues to help users identify them.
2. Attaching custom forms to the queue itself instead of individual queue topics.
3. Setting permissions to determine who can submit requests to the queue.
4. Ensuring the project status is set to "current" so the queue is visible in the requests area.