Understand request queues

Transcript

understand request cues. In this you’ll learn about what a request queue is, how to submit a request, and how request queues are structured in work front. Whenever there is an issue with a project or a task, that information is directly tied to the original work item. However, what if you run into an issue that is not related specifically to a project? Where do you submit software? Hardware upgrades? Suggestions submitted by clients? Functionality improvements or even PTO request queues allow you to have one central location to make these requests. Here are a few examples we use request queues for all sorts of things. We use request queues for PTO requests, T-shirt size, request for when the company wants to buy a swag or even training needs. Requests that are sent to the training team before we start creating a request queue. Let’s take a look at the request area within the system and walk through submitting a request. In the Global Navigation bar. We’ll go to the request area. This is where users will view and submit request in the system. As you can see here, this page displays a list of requests that you have personally submitted. This page will also display for you the status of the request, to submit a new request, simply click on the new request button. Here you will select what type of request you want to make. In this example, we selected infrastructure and software ticket. From here we entered the subject of the request beneath the subject field. We have a description field beneath the description. We have a variety of fields that are typically not required. This includes the document field where you can add any format of document. This added information can be useful to the person receiving the request at the bottom of the request. We have a custom form. We do recommend completing the custom form. As these fields are specific to this request type. Once the form is complete, we click the submit button. This navigates us back to request where we are able to locate the request we just submitted. But how were these requests handled in the system? To truly understand requests in work front, it is vital that you understand what is going on behind the scenes. As far as work front is concerned. Each request is actually an issue and all issues within the system must be associated with a project. A project which only contains requests is called a request queue. You could handle all of your request within a single project. However good queue management practices will separate requests by their type and manage them separately. The structure of these various request queues is important. Not only does it drive the user interface when choosing what type of request to make, but it also customizes what information is required on that individual request as well as who the assignments are made to. Each time a request is submitted, it gathers all of the information filled out in the request area and goes to the associated Request queues issue tab, where it is automatically assigned to be handled. If we wanted to find where the request that we just submitted was, we need to look for the project that it was associated with. The first decision we made when making the request was to click on infrastructure requests. This is the name of the request queue or project in work front that we will look for. So let’s go to the project’s area then to all projects. After clicking on infrastructure requests, we’ll navigate to the issues where we can see the requests that we just submitted. This is what appears on the back end. If you have access to this queue in the next video, we will show you how to set up a project to act as a request queue.