How requests are sizedThe right size depends on effort, risk, and evidence.
We look at the Oracle product, module, version, environment, urgency, access path, evidence quality, expected remediation, testing needs, and production risk. A clean report defect may fit a Small ticket. A recurring close issue touching SLA, subledger data, and custom reports may require a Medium ticket, Large ticket, or advisory path.
Product scopeEBS, Fusion, APEX, OIC, OCI, database, reporting, middleware, or adjacent Oracle workload.
Evidence qualityErrors, logs, screenshots, report samples, run history, versions, and recent change details.
Change riskRead-only review, non-production fix, production change, data repair, integration impact, or close-cycle dependency.
Validation pathWho confirms the result, what test proves success, and whether rollback steps are required.