Jump to content

Community Wishlist/Wishes/Centralized Incident Management/ja

From Meta, a Wikimedia project coordination wiki
This page is a translated version of the page Community Wishlist/Wishes/Centralized Incident Management and the translation is 29% complete.
Centralized Incident Management Open

要望を編集 この要望について話し合う

説明

再び Community Wishlist Survey 2022/Miscellaneous/Centralized Incident Management を要求する

Summary: We should have a central helpdesk that tracks and manages problems and incidents. Before someone says "that's what phabricator is for" - perhaps it COULD be, but in our current operational model it is not. Someone can report an incident or problem to phab, which may trigger some software work - but this never tracks the report to resolution of the actual user story. It can track that someone thinks they have a fix, that may one day get deployed - but not that it ever was deployed and certainly not that there was acceptance of the production resolution. Possibly changing the phab workflow would help.

Current workflow:

  • User finds a production problem
  • phabチケットの開設者
  • Someone claims to have fixed the problem cause
  • The phab ticket is resolved, user gets notified. (Note: at this stage the ticket almost never gets updated again)
  • At this stage, the fix is almost never actually in production, and the instance of the problem continues to be occurring
  • (無期限保留)
  • The likely fix gets deployed to production
  • No further notifications are sent, no acceptance testing is done or logged

Ideally, some staff funding for incident/problem management would also be available to manage such a process.

割り当てられ済の重点領域

未割り当て

「要望」の分類

System change

関連するプロジェクト

全てのプロジェクト

影響を受けている利用者

誰でも

その他

  • 作成済: 13:51, 16 September 2024 (UTC)
  • 最終更新: 17:00, 18 September 2024 (UTC)
  • 記入者: xaosflux Talk