Skip to content

TASK: Enforce Sprint parent hierarchy for Project work #223

Closed

Description

@ramioooz

Parent: STORY: Standardize organization engineering workflows

Objective

Make GitHub Project #1 hierarchy a hard governance rule for all future planning work.

Scope

  • Require every new task, story, bug, and supporting issue added to Project STORY: Establish Java service quality gates and SonarQube strategy #1 to be a native sub-issue below one of the eight Sprint epics.
  • Require a new parent story or epic to be created and attached first when an item does not fit an existing branch of the Sprint hierarchy.
  • Require the native GitHub Issue Type, Project Sprint value, assignee, and status to be set when an item is added.
  • Record the parent relationship through GitHub sub-issues; a Parent: line in the issue body is documentation only and is not sufficient.
  • Audit and repair existing parentless non-Sprint items without changing historical issue content unnecessarily.

Acceptance Criteria

  • Organization-level AGENTS.md contains the parent-before-project rule and the repair procedure.
  • docs/project-handoff.md records the current hierarchy audit and the repaired items.
  • Project STORY: Establish Java service quality gates and SonarQube strategy #1 contains exactly the eight Sprint epics as root planning items and no parentless non-Epic issue.
  • Future PRs reference the supporting parented issue and related PRs where applicable.

Verification

Activity

  1. self-assigned this
    on Sep 4, 2026
  2. added theissue type on Sep 4, 2026
  3. ramioooz commented on Sep 5, 2026

    @ramioooz
    MemberAuthor

    Hierarchy audit (2026-09-05): queried all 20 active non-Epic items in Project #1 and verified every item has a native GitHub parent. No unparented active task, story, or bug remains.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions