要点

one flat categoryでなく3 independent facet:customer need、evidenceあるimpact/specialist risk、next actionを制御するworkflow/evidence state。multi-label、provenance/confidence必須、priority/resolutionは別field、human correctionを記録。

label=contextfind、route、measure、reviewを助けるがproof、priority、ownership、outcomeではない。
multi-facetone ticketにneed.defect_report + risk.multi_user + workflow.specialist_review + workflow.monitoring。
govern changedefinitionをversion、quality sample、co-occurrence/unlabelled work監視、label変更時history migration。

3-facet support tagging taxonomy

customer need

requested outcome/help。primary needは一つ、別workが実在する時だけsecond。

impact / risk

observed scope/harm/specialist trigger。0/1/multiple適用、priority/incidentへinputするが置換しない。

workflow / evidence

next actionを制御するtemporary state。evidence変更でremove/replace/retainしpermanent customer attribute化しない。

各labelのquality contract

required taxonomy field
fieldpurposefailure prevented
label_id + facetstable machine key / independent dimensionrename break / one-bucket confusion
definition + include/excludeshared boundary / counterexamplesynonym drift / overlap
evidence + provenancewhy label appliesAI confidence=truth
owner + actioncontext to accountable workdecorative tag / unowned queue
version + review triggersafe change / reassessmentsilent historical drift

25 support ticket tagging taxonomy labels

各labelはstarting point。clear action、query、control、learning use caseを作るlabelだけ採用。unused tagはnoise。

01

How-to guidance need.how_to

NEED

meaning

supported taskの手順を求め、expected behavior failureは未提示。

include / exclude

procedure学習が目的ならinclude。reproducible failure、missing entitlement、access denial、feature gap、complaintはexcludeし別label。

evidence / route

task、product/version、attempted step、docs、desired outcome、channelを保持。knowledge/frontlineへrouteしdefect evidenceならreclassify。

02

Account access need.account_access

NEED

meaning

sign-in、verify、recover、join、expected role/permission取得ができない。

include / exclude

authentication、invitation、recovery、role、permission、lockout、session accessをinclude。service-wide incident/account takeover疑いはimpact/security label追加。

evidence / route

safe account ID、identity state、affected role、exact error、time、permitted device/session context、recovery attemptを保持しidentity/access ownerへ。secretを要求しない。

03

Setup / configuration need.setup_configuration

NEED

meaning

supported product、workspace、policy、workflow、integration setting、deployment optionのconfigurationが必要。

include / exclude

known capabilityのunresolved configurationをinclude。pure how-to、unsupported feature、integration failure、defectはexclude。

evidence / route

target state、current config/version、environment、dependency、change history、validation、rollback needを保持しimplementation/product specialistへ。

04

Feature request need.feature_request

NEED

meaning

未確認のcapability、behavior、control、channel、format、integrationを求める。

include / exclude

future capability/confirmed gapをinclude。existing feature誤解、configuration、access、defect、未確認contract commitmentはexclude。

evidence / route

job-to-be-done、workaround、affected users、frequency、need evidence、constraint、outcomeを保持。delivery dateを作らずproduct discoveryへ。

05

Product defect report need.defect_report

NEED

meaning

reproducible conditionでobserved behaviorがdocumented/configured/previously verified expectationと異なる。

include / exclude

evidence付きreproducible mismatchをinclude。preference、feature request、config error、data-source error、misunderstandingはexclude。不確かならco-label。

evidence / route

expected/observed、steps、timestamp、version、environment、provenance付きlog/screenshot、frequency、workaround、regression pointを保持。

06

Performance issue need.performance_issue

NEED

meaning

latency、timeout、throughput、resource、responsivenessがevidenceあるexpectation外。

include / exclude

measured/repeatable slownessをinclude。complete outage、未検証local-device原因、evidenceなしslow、billing complaintはexclude。

evidence / route

operation、timestamp/timezone、region、tenant、volume、percentile/sample、baseline、trace/request ID、network context、workaroundを保持。

07

Integration issue need.integration_issue

NEED

meaning

OpenMaxとAPI、connector、webhook、identity provider、business systemのboundaryでdata/action failure。

include / exclude

authentication、schema、mapping、rate、delivery、state-sync failureをinclude。boundaryなしnative defect、unsupported connector requestはexclude。

evidence / route

system/version、direction、endpoint、safe request/response ID、status/error、timestamp、retry/webhook、mapping、change、ownership boundaryを保持。

08

Data / reporting issue need.data_report_issue

NEED

meaning

missing、delayed、duplicated、inconsistent、transformed、exported、calculated dataへの疑義。

include / exclude

lineage、sync、aggregation、dashboard、export、metric disputeをinclude。access-only、data無関係UI defect、new analytics requestはexclude。

evidence / route

source/destination、record/metric definition、query/filter、time range/zone、expected/observed、freshness、sample ID、lineage、transformation version、reconciliationを保持。

09

Billing / payment question need.billing_payment

NEED

meaning

invoice、price、plan charge、tax、payment status、credit、payment method、account balanceへの質問。

include / exclude

refund/cancellation決定前のexplanation/reconciliationをinclude。formal refund/cancel、fraud疑い、usage defectはexclude/co-label。

evidence / route

merchant entity、invoice/payment ID、amount/currency、line item、tax/discount、payment state、plan/version、prior credit、question、finance ownerを保持。

10

Refund / cancellation request need.refund_cancel

NEED

meaning

money back、credit、reversal、subscription cancellation、renewal stop等commercial remedyを明示要求。

include / exclude

eligibility不明でもrequested outcomeとしてinclude。approval、legal entitlement、fraud evidence、completed refundとはしない。

evidence / route

exact request、transaction/contract、effective date、customer words、fulfillment/usage、prior recovery、dispute、policy candidate、authority、decision stateを保持。

11

Task blocked risk.task_blocked

RISK

meaning

reasonable workaroundがなくtime-relevant core taskを完了できない。

include / exclude

frustrationだけでなくblocked outcome evidenceをinclude。effective workaroundまたはbroader incidentならexclude。priorityは別計算。

evidence / route

blocked task、identity/role、deadline/source、workaround、dependency、start time、impact owner、reassessmentを保持。

12

Multi-user impact risk.multi_user

RISK

meaning

same issueが複数distinct user/account/tenant/region/workflowへ影響するverified evidence。

include / exclude

shared pattern evidenceをinclude。one loud report、duplicate message、見かけの相関からscope推定しない。

evidence / route

affected unit、denominator、first/last observed、signature、correlation method、sample ID、confidence、incident linkを保持。

13

Service degradation risk.service_degradation

RISK

meaning

monitoring/corroborated reportでshared serviceのavailability、correctness、capacity、performance低下。

include / exclude

validated shared-service condition/incident linkをinclude。isolated ticket、local config、communicated maintenance、past recovered incidentはexclude。

evidence / route

service/component、telemetry、baseline、region、scope、start/recovery、incident ID/status、workaround、owner、updateを保持。

14

Security signal risk.security_signal

RISK

meaning

unauthorized access、credential compromise、malicious activity、vulnerable behavior、CIA risk indicator。

include / exclude

security review必要signalをinclude。breach/attacker/customer faultの証明にしない。ordinary accessはexclude。

evidence / route

minimal indicator、source/time、asset/account、safe artifact location、exposure window、containment、security owner、disclosure restriction、incident linkを保持。

15

Privacy signal risk.privacy_signal

RISK

meaning

personal data collection、access、disclosure、correction、deletion、consent、retention、identity right、unintended exposureの可能性。

include / exclude

specialist triage用potential privacy issue。incomplete textからviolation/identityを断定しない。

evidence / route

minimum data category/subject relationship、system、event time、request authority、exposure hypothesis、restriction、privacy owner、deadline source、correction trailを保持。

16

Accessibility barrier risk.accessibility_barrier

RISK

meaning

accessibility barrier/incompatible accommodationでperceive、understand、navigate、operate、communicate、task complete不可。

include / exclude

reported/observed barrierをinclude。disability assumptionでcapability推定せずrequested format/accommodationを保持。

evidence / route

affected task/content/control、任意のassistive technology、environment、expected/observed、accommodation、alternative quality、deadline、owner、reviewを保持。

17

Complaint / escalation risk.complaint_escalation

RISK

meaning

response必要なdissatisfaction、handling/finding dispute、review request、unfair treatment allegation、external complaint route。

include / exclude

expression/review requestをincludeするがtoneだけでmisconduct/high priorityにしない。local definitionに従う。

evidence / route

customer words、issue、outcome、prior case/decision、review right/deadline、conflict check、accessibility/representative need、independent owner、update、non-retaliationを保持。

18

Identity / authority unverified evidence.identity_unverified

EVIDENCE

meaning

requester identity、account relationship、representative authority、action authorizationを信頼するpermitted evidence不足。

include / exclude

temporary evidence stateでhonesty判断ではない。verification成功またはsafe no-identity pathならremove。

evidence / route

requirement、permitted method、attempt、result、confidence、document location、restriction、expiry、owner、next stepを保持。credential禁止。

19

Evidence missing evidence.missing

EVIDENCE

meaning

required record、observation、permission、version、confirmation不足でdefined decision不可。

include / exclude

missing itemとdecision dependencyがnamedならinclude。vague need more info、既存fact、excessive collectionはexclude。

evidence / route

missing field/artifact、必要性、lawful source、request owner、dependency、due、alternative evidence、status、expiryを保持。

20

Possible duplicate evidence.duplicate_candidate

EVIDENCE

meaning

複数ticketがsame issue/event/transaction/root causeの可能性だがequivalence未検証。

include / exclude

candidate linkとしてinclude。wording、email、timing、model similarityだけでmergeしない。distinct person/transaction/remedy/privacy boundaryはexclude。

evidence / route

candidate ID、match signal、difference、boundary、primary proposal、history plan、human decision、linkage、undo pathを保持。

21

Customer action required workflow.customer_action

WORKFLOW

meaning

組織が代行できないspecific/reasonable/accessible customer actionにprogress依存。

include / exclude

named action、reason、safe methodがある時include。internal work、既存情報、unreasonable burden、inaccessible step、secret request、silent SLA pauseはexclude。

evidence / route

action、reason、minimum input、secure/accessible method、instruction、due/expiry、delivery、alternative、reminder、owner、continuing internal workを保持。

22

Internal action required workflow.internal_action

WORKFLOW

meaning

named internal teamのinvestigation、configuration、correction、approval、deployment、reconciliation、communicationにprogress依存。

include / exclude

concrete owned actionをinclude。unowned engineering queue、customer updateからdependency隠蔽はexclude。

evidence / route

action、owner/backup、acceptance evidence、dependency、priority、time、status、blocker、update owner、completion proof、recoveryを保持。

23

Specialist review required workflow.specialist_review

WORKFLOW

meaning

security、privacy、safety、accessibility、legal、fraud、finance、tax、compliance、incident等qualified authorityが必要。

include / exclude

required specialty/decisionをinclude。violation、breach、fraud、liability、entitlementの証明ではない。

evidence / route

trigger、specialty、question、bounded evidence、access、reviewer/backup、deadline、authority、outcome、rationale、restriction、reassessmentを保持。

24

Monitoring / verification workflow.monitoring

WORKFLOW

meaning

immediate action/containment後もresult、recurrence、recovery、delivery、sync、stabilityをobserve必要。

include / exclude

measurable observation planをinclude。signal/owner/threshold/end conditionなしpassive waiting、silence=recoveryはexclude。

evidence / route

signal/query、baseline、expected result、scope、cadence、threshold、start/end、owner、alert route、update、decision、snapshotを保持。

25

Reopened workflow.reopened

WORKFLOW

meaning

previously resolved/closed ticketがrecurrence、remedy failure、material evidence change、outcome dispute、incomplete dependencyで再active。

include / exclude

prior closureへlinked activation eventをinclude。unrelated new issue/routine questionは別ticket。

evidence / route

prior closure evidence、reopen trigger/time、changed fact、recurrence signature、failed remedy/dependency、customer words、new owner/priority、correction、reviewを保持。

実例:「CSV export broken」が2回relabel

顧客が「finance teamのCSV exportがbroken」と報告。classifierは語句からneed.data_report_issueとrisk.task_blockedを提案するがhypothesisであり結論ではない。

  1. report保全。 customer words、tenant、role、export type、time、UI error、redacted request IDを保持。「finance」からpriority推定しない。
  2. first correction。 new roleのみ403再現、data intact、admin export可能。need.account_access + evidence.missingへ変更しpolicy確認。verified workaroundでrisk.task_blocked削除。
  3. new scope evidence。 deployment後18 tenantでsame policy mismatch。need.defect_report + risk.multi_user + workflow.specialist_review追加。case linkするがidentity mergeしない。
  4. recovery evidence。 controlled fix後workflow.monitoringを残しtelemetry/sample exportでrecovery確認。historyにmodel proposal、human add/remove、evidence、time、owner。

taxonomyのgovernance・measurement

version / migration

各definitionにowner、version、effective date、example/counterexample、downstream use、retirement path。old→new mappingを明示しhistory meaningをsilent rewriteしない。

quality sampling

language、channel、product、label、confidence、model/rule version、reviewer、route、outcomeでsample。precision/recallはdocumented review setとdisagreement resolutionで。

operational usefulness

unlabelled、unknown/other、co-occurrence、correction、stale temporary label、routing change、time to owner、reopen、privacy defect、no-consumer labelを追跡。popular≠useful。

minimum auditable assignment record

ticket_id · label_id · facet · taxonomy_version · proposed_by · model_rule_version · evidence_refs · confidence · assigned_by · assigned_at · reason · corrected_from · correction_reason · expires_at · route_action · owner · downstream_consumers · access_class · review_sample · retention_event

OpenMaxによるticket tagging governance

OpenMaxはpermitted ticket context、versioned definition、evidence/confidence付きmulti-label proposal、facet/incompatibility rule、human review、owner route、temporary label expiry、change monitor、correction保全を調整。raw sensitive contentをtag valueに入れずspecialist evidenceはrole制限。

1 · observeticket、product、customer words、system evidence、current state
2 · proposefacet別label、evidence、confidence、missing field
3 · reviewhumanがambiguity/consequential specialist routeをcorrect
4 · route / monitorowner割当、temporary state expiry、evidence change検出
5 · governquality sample、usage分析、definition version、安全migration

misclassification・privacy・governance boundary

  • lawful/necessary/specialist purposeなしにprotected characteristic、health、vulnerability、sentiment、customer value、blame、fraud、legal conclusionをordinary routing label化しない。
  • labelはproof、priority、SLA、incident declaration、root cause、ownership、resolution、consentではなく別governed field。
  • credential、full payment data、personal narrative、medical fact、security artifact、confidential investigation textをtag name/valueに入れない。
  • security、privacy、safety、accessibility、fraud、discrimination、complaint、legal、regulatory、high-impact routeはqualified human review。
  • accessible correction/appeal/reopen pathを提供。lawfulなlanguage/group quality監視でもsensitive dataをpermanent profile化しない。

よくある質問

one ticket=one label?

primary customer-needは可能なら一つ、impact/riskとworkflow/evidenceは0以上。synonym duplicateを避ける。

tag=priority?

いいえ。tagはcontext。priorityはimpact、urgency、override、owner、reassessment ruleが別途必要。

AI auto-tag可能?

validated threshold内low-consequenceは可能だがevidence、version、confidence、correction、sampling必須。specialist/adverse routeはhuman。

いつlabel remove?

evidence不適用、temporary expiry、human correction、migration replacement時。assignment history/reasonを保持。

labelはいくつで多すぎ?

distinct definition、action、query、control、owner、learning consumerがないlabelはexcess。usage測定しsafe merge/retire。

OpenMaxの役割?

versioned definition、evidence-backed label proposal、review request、route、state expiry、correction monitor、auditable historyをcoordination。

情報源、編集方法、制限

OpenMax編集部はAtlassian request/work type/ITSM category、NIST SP 800-61r3、NIST AI RMF、ISO 10002、WCAG 2.2を確認しoriginal 3-facet 25-label starting taxonomyとcorrection caseを作成。2026年9月3日再確認。

範囲注記 Atlassianはone implementation、NIST/ISO/W3Cはincident、AI risk、complaint、accessibility boundaryを支援。25-label setを定義/fit保証しない。actual sample、user language、system、route、right、downstream decisionで検証。