No process to track when operations are set to non-default priority

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Workload Resilience
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Internal operations can now opt for a non-default priority via their AdmissionContext.

      This ticket can serve as a placeholder for discussion:
      (1) Would it be useful to track all new commits which change an operations default priority?
      (2) What is the most practical approach?

      The solution could be a simple as "won't do", adding some sort of commit hook/ list which tracks server tickets make operations opt out of default priority, etc.

      A manual list could risk becoming stale quick, and as more operations utilize re-prioritisation, maybe we need a formal process.

            Assignee:
            Unassigned
            Reporter:
            Haley Connelly
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: