Vega. Defect Priority Definition for Functional Issues.
Priority | When | System Impact | Business impact |
P1- urgent | Must be fixed right away or in the next build. Everything else can wait. If found in production, requires hot fix patch to be deployed as soon as possible | Release blocker. Unless fixed, will hold up a release. Renders FOLIO as a whole, or a core FOLIO function, unusable and has no workaround. Examples: Causes loss/corruption of stored data; exposes security vulnerabilities; causes race conditions, database deadlocks etc; serious performance issues; library unable to perform core functions, such as checking out items to patrons | An issue causing FOLIO as a whole, or a core function of FOLIO, to be unusable |
P2 - high | Should be fixed as early as possible. There is a temporarily acceptable workaround If found in production, may require hot fix patch delivered outside of a regular release schedule. | An issue has significant repercussions but does not render FOLIO as a whole, or a core FOLIO function, unusable or has a temporarily acceptable workaround | Known workaround is forcing the customer into unplanned spending of additional resources. |
P3 - medium | May be fixed in one of the next releases If found in production, the fix can wait until the next scheduled release | The product or application doesn’t meet certain criteria or still exhibits some unnatural behavior while affecting one isolated piece of functionality. An issue is self-contained and has an acceptable & easily reproducible workaround. | An issue causes minor impact on productivity. |
P4 - low | Fixing can be deferred until all other priority defects are fixed If found in production, the fix can wait until the next scheduled release | An issue causing almost no impact to the functionality, but is still a valid defect that should be corrected | An issue has minimal impact on normal operations. |
P5 - cosmetic | Fixing can be deferred indefinitely |