When we talk about major defects, we also talk about the availability of workaround. I need to know what do we mean exactly by a workaround. Example: If a function is not working at all, however, the user can use another function to get his desired result, then can we consider this as a workaround?
Yes, your insinuation is how I understand 'workarounds' as well, in the context of software testing. Defining it more verbose you could say it's a process (a number of actions) achieving a result that is normally achievable through an easier, more dedicated or user-friendly process. (*)
In practice, a workaround might differentiate between critical and high severity (business impact).
For example, there is a major difference in impact on business processes between:
- "We do not receive any orders placed via our web shop." - This can be considered critical as business stalls.
- "We do not receive any orders placed via our web shop, but a helpdesk employee can manually trigger the event queue so we get the orders anyway, albeit with a few hours of delay." - This can be considered high severity, because business processes aren't working optimally, but due to a workaround the process is flowing (but it's still important because the workaround is demanding resources and/or costs money in some way).
(*) Note, the inverse interpretation is also possible: a shortcut that users have found, which was not intended by design but allows them to perform a task faster or easier.