Organize and prioritize tickets based on urgency and importance with four priority levels: Low, Medium, High, and Urgent.
Priorities in Ravenna help your team organize and manage tickets based on their urgency and importance. Whether you’re dealing with a critical system outage or a routine feature request, priorities ensure the right tickets get attention at the right time.
For critical issues that require immediate attention and can’t wait. These are typically system outages, security incidents, or blocking issues that affect multiple users.
Important issues that should be addressed soon but aren’t blocking critical operations. These might include time-sensitive requests or issues affecting key processes.
Standard priority for most tickets. These are routine requests, non-critical bugs, or general support issues that can be handled in the normal workflow.
Priority is a required field - all tickets must have a priority assigned. When users create tickets, they’re assigned a Medium priority by default. However, you can customize this behavior:Request Type Defaults:
Each request type can have its own default priority
Override the system default based on the type of request
Ensure consistent prioritization across similar ticket types
Example: You might set “Bug Report” request types to default to High priority, while “Feature Request” types default to Low.
Priorities in Ravenna provide a simple yet powerful way to organize and manage your team’s workload. By using the four priority levels effectively, you can ensure that urgent issues get immediate attention while maintaining a balanced approach to all support requests.The priority system integrates seamlessly with reporting features, giving you comprehensive control over how your team handles different types of tickets. Start with the default settings and adjust as you learn what works best for your organization.