Hi Community,
This is Wednesday again, and Weekly knowledge growth with Jira Guru!
Today's topic is "Request Types in Jira Service Management"
-----
Request types in Jira Service Management are specific categories that help organize and manage service requests. They define how a request appears in the customer portal and what information is gathered from the customer. Request types are crucial for categorizing different kinds of service requests, ensuring efficient management and resolution. They allow customization to meet specific needs and help in streamlining service request management.
For more detailed information, you can visit the Atlassian Support page on request types.
With request types in Jira Service Management, you can:
Click view to see and get the request link
By following these steps, you can effectively set up request types in Jira Service Management, tailoring them to your organization's specific requirements and improving the service request process for both users and your service desk team.
In Jira, the main methods for handling requests are typically aligned with IT Service Management (ITSM) best practices and include:
Incident management involves handling unplanned events or disruptions to service that affect the quality of your service or threaten to do so. The goal is to restore normal service operations as quickly as possible. Incidents are typically categorized, prioritized, investigated, and resolved.
Service request management deals with predefined and planned requests from users. These requests are often routine and documented, such as password resets, software installations, or hardware provisioning. Service request management aims to ensure that these requests are processed efficiently and according to established workflows.
Problem management focuses on identifying and addressing the root causes of recurring incidents or potential issues. It involves a proactive approach to prevent incidents from happening in the first place. Problem management includes root cause analysis and the implementation of permanent solutions to prevent incidents from recurring.
Change management is concerned with managing changes to the IT environment to ensure that they are planned, approved, and implemented with minimal disruption to services. It involves assessing the impact of changes, obtaining approvals, and monitoring the implementation process to mitigate risks and prevent incidents.
Post-incident reviews are conducted after critical incidents to evaluate their impact and assess the response to those incidents. The goal is to learn from incidents, identify areas for improvement, and refine incident response procedures.
These methods are commonly used in IT Service Management (ITSM) frameworks like ITIL (Information Technology Infrastructure Library) to ensure efficient and effective handling of requests, incidents, and changes in IT organizations. They help organizations deliver high-quality services while minimizing disruptions and improving overall service management processes.
You can work by Choose a category for your request type
Certainly! Here are additional tips, along with examples, related to managing request types in Jira Service Management:
Tip: Hide specialized request types that are meant for internal use or specific scenarios from the customer portal to reduce clutter.
Example: Hide "Employee Onboarding" request type, which is handled internally by HR, from the customer portal.
Tip: Include clear and concise instructions to guide users in selecting the appropriate request type.
Example: "For hardware issues, please select 'Hardware Support' from the dropdown menu."
Tip: Utilize tooltips to provide additional information when users hover over request types or form fields.
Example: Hovering over "Software Installation" request type displays a tooltip saying, "Request software installations on your device."
Tip: Offer links to self-help articles or FAQs within request types to assist users in resolving common issues independently.
Example: Include a link to the knowledge base article on "Troubleshooting Network Connectivity" in the "Network Issue" request type.
Tip: If a request type requires specific error messages or codes, instruct users on how to provide them accurately.
Example: "If you encountered an error, please provide the error code and a brief description in the 'Error Details' field."
Tip: If selecting one request type depends on a previous selection, clarify this in the instructions.
Example: "After selecting 'Hardware Request,' you will be prompted to choose the specific hardware type."
Tip: Avoid technical jargon and use language that is easily understood by your target audience.
Example: Instead of "ITSM Incident Report," use "Report an IT Issue."
Tip: If your user base is multilingual, provide instructions in multiple languages.
Example: Offer instructions in both English and Spanish to cater to a diverse user base.
In this blog, we've delved into the best practices for managing request types in Jira Service Management. Efficient request-type management is essential for streamlining workflows, enhancing customer satisfaction, and delivering high-quality service.
Key takeaways for best practice include:
By following these practices, you can optimize your request type management and provide a smoother, more efficient service experience for both your team and your customers.
Stay tuned for more Jira Information and remember, being a 'JIRA GURU' is all about continuous learning!
------------
Learn more about Jira, Confluence and Atlassian with Jira Guru
💬 If you have any questions or suggestions for the next topic please leave a comment below 👇
🙌 Please like, and share this article with new beginners