From 6a3f123c0574c3add6f22fd95b4a1de267bceb99 Mon Sep 17 00:00:00 2001 From: Adam Williamson Date: May 27 2026 22:53:41 +0000 Subject: bug_status: update refs for program_management -> operations rename program_management was renamed to operations, and now all these references are broken. Signed-off-by: Adam Williamson --- diff --git a/modules/ROOT/pages/bug_status.adoc b/modules/ROOT/pages/bug_status.adoc index e9f0960..8d16728 100644 --- a/modules/ROOT/pages/bug_status.adoc +++ b/modules/ROOT/pages/bug_status.adoc @@ -1,25 +1,25 @@ = Bug Status Workflow This document describes best practices for setting Bugzilla status for bugs and feature requests. -For Change proposal trackers, use the Bugzilla status described in the xref:program_management::changes_policy.adoc#_bugzilla_trackers[Changes policy]. +For Change proposal trackers, use the Bugzilla status described in the xref:operations::changes_policy.adoc#_bugzilla_trackers[Changes policy]. == Statuses The image below presents a general flow chart for bugs in the typical case. The flow is bi-directional: a bug can revert to a previous status if, for example, a proposed fix is incomplete. -image::program_management::fedora-bug-lifecycle.png[] +image::operations::fedora-bug-lifecycle.png[] The table below summarizes the statuses. More details, including additional keywords, flags, and resolutions are given in the following sections. -include::program_management::partial$bz_status.adoc[] +include::operations::partial$bz_status.adoc[] == Resolutions The table below describes the resolutions that can apply to the _CLOSED_ status. -include::program_management::partial$bz_resolution.adoc[] +include::operations::partial$bz_resolution.adoc[] == Priority and Severity