As a way to categorize the urgency in which you should approach bugs reported, we now tag priority tests with priority levels.
Being able to analyze the severity of a bug also helps the Meeshkan team decide which notification channel is most appropriate (pager duty vs GitHub issue vs slack vs email).
Security focused bugs although don't prevent a client from operating, often make it unsafe to do so. Meeshkan automatically labels security bugs as
A complete business down situation. The client is unable to operate.
A major component of the clients ability to operate is affected. Some aspects of the business can continue but its a major problem.
The clients core business is unaffected but the issue is affecting efficient operation by one or more people.
The issue is an inconvenience or annoying but there are clear workarounds or alternates.
The issue is a background or planned task and will be addressed when time permits or on the planned date.