best practices for labelling software defects in JIRA? "Blocker", "Critical", "High" are same

[Behrooz Sadigh]

Organizations seem to use terms such as "Blockers", "Critical" or "High" to categorize their software development defects.  But they are all almost the same.  Are there any best practices for labeling defects?

[Tarun Sapra]

Possible duplicate

https://community.atlassian.com/t5/Jira-questions/According-to-Jira-What-is-Blocker-Critical-Major-Minor-and/qaq-p/668774

[Patrick Ricciardi]

I kind of think this is depending on the organization. (For example, for our purposes Blocker/Critical was redundant, so we eliminated Blocker.)

But, in general here is how I see them.

Blocker: Things are not working. Problem needs to be fixed immediately, if not sooner. Drop everything and work on this and nothing else.

Critical: Things aren't great. And, they should be fixed right away. Drop everything you can. Get this fixed.

High: Things could be better. They should be fixed sooner than later, but no need to disregard other things.