Separate defect severity from fix priority in a release meeting.

Instruction: Classify the supplied defects in words, explain your ordering, and identify facts that could change it.

Context:

A fictional team defines severity as impact when the defect occurs and priority as urgency of the next action. Numeric labels vary by team. Case A: the public campaign page misspells the brand name; its launch is in two hours, and purchasing works. Case B: a new export silently omits transactions from financial totals; all users can access it, and finance relies on it tomorrow. Case C: an old report crashes when opened; it is disabled for all users behind a verified flag, and nobody plans to enable it this month. You may propose disabling a feature as containment.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

I would treat B as high severity and urgent: silently incomplete financial totals can mislead decisions, and users can reach the export now. I would seek immediate containment, such as disabling the incorrect export, and prioritize correction and reconciliation of any already generated outputs...

Upgrade to view official answer

Related Questions