File jira tickets for NEEDS_REPLACEMENT and USE_REPLACEMENT tag

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Server Programmability
    • Programmability 2025-08-04, Programmability 2025-08-18, Programmability 2025-09-01
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      There should be one ticket per NEEDS_REPLACEMENT API, assigned to the team that owns the declaration, and one per call site of a USE_REPLACEMENT API, assigned to the team that owns the calling code.

      NEEDS_REPLACEMENT and USE_REPLACEMENT classes should have a ticket per class, not per individual API.

            Assignee:
            Ronald Steinke
            Reporter:
            Ronald Steinke
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: