Sort by operational priority

Scenario

Review support incidents before standup

Priority and impact use numeric parser maps, while State uses a custom sorter so active incidents appear before waiting or resolved work.

Try it

Use custom order, not alphabetic order

• Sort Priority and confirm Sev 1 comes before Sev 2 and Sev 3.
• Sort State and confirm Investigating comes before Waiting.
• Activate the sorted column again to clear sorting.
• Read the status message after each sort.

Example

Incident queue

Developer notes

Options used in JavaScript

const instance = createSortableTable(table, {
  statusElement: "#incident-sort-status",
  allowUnsort: true,
  customParsers: {
    priority(value) {
      return { "sev 1": 1, "sev 2": 2, "sev 3": 3, "sev 4": 4 }[value.toLowerCase()] ?? 99;
    },
    impact(value) {
      return { global: 1, region: 2, team: 3, "single user": 4 }[value.toLowerCase()] ?? 99;
    }
  },
  customSorters: {
    state(rowA, rowB, context) {
      return stateOrder(context.getValue(rowA)) - stateOrder(context.getValue(rowB));
    }
  },
  labels: {
    sortedBy: "Incident queue sorted by {label}, {direction}.",
    unsorted: "Incident queue returned to original order for {label}."
  }
});

Accessibility notes

What to inspect