feature_request.yml

name: "✨ Feature Request"
description: Propose a new feature or enhancement to Heimdall.
title: "[FEAT] <short description>"
labels: ["enhancement", "needs-triage"]
assignees: []
body:
  - type: markdown
    attributes:
      value: |
        Thank you for suggesting an improvement to Heimdall. Please be as specific as possible so we can evaluate and prioritize your request.

  - type: dropdown
    id: component
    attributes:
      label: Target Component
      description: Which area of Heimdall would this feature affect?
      options:
        - Dashboard (Request List)
        - Request Inspector (Detail Panel)
        - Collections / Blueprints
        - Authentication (LDAP/SSO)
        - API Routes (backend)
        - Audit Logging
        - Database / Prisma Schema
        - Docker / Deployment
        - Developer Tooling (tests, CI)
        - New Feature / Standalone
    validations:
      required: true

  - type: textarea
    id: problem
    attributes:
      label: Problem Statement
      description: |
        What problem does this feature solve? Describe the current limitation or pain point.
      placeholder: "Currently, there is no way to add comments or notes to a request. As an APPROVER, I want to leave feedback when rejecting a request so that the REQUESTER understands why it was denied."
    validations:
      required: true

  - type: textarea
    id: solution
    attributes:
      label: Proposed Solution
      description: Describe the feature or change you'd like to see.
      placeholder: |
        Add a "Rejection Reason" text field to the approval/rejection flow.
        The reason should be:
        - Stored in the database (new `rejectionReason` column on `HttpRequest`)
        - Displayed in the Request Inspector under a new "Feedback" tab
        - Included in the structured audit log output
    validations:
      required: true

  - type: textarea
    id: alternatives
    attributes:
      label: Alternatives Considered
      description: Have you considered any alternative approaches?
      placeholder: "Alternatively, we could use the existing `response` field to store rejection notes, but that would pollute execution data."

  - type: dropdown
    id: priority
    attributes:
      label: Priority (your estimate)
      options:
        - Low — Nice to have
        - Medium — Meaningfully improves UX or security
        - High — Blocking significant use cases
    validations:
      required: true

  - type: textarea
    id: acceptance
    attributes:
      label: Acceptance Criteria
      description: How would we know this feature is complete? List measurable outcomes.
      placeholder: |
        - [ ] APPROVER can type a reason when rejecting a request
        - [ ] Reason is persisted to the database
        - [ ] REQUESTER sees the reason in the Inspector's "Feedback" tab
        - [ ] Reason is included in the structured JSON audit log
        - [ ] Unit tests cover the new API endpoint

  - type: checkboxes
    id: checklist
    attributes:
      label: Pre-submission Checklist
      options:
        - label: I have searched existing issues and this is not a duplicate.
          required: true
        - label: This feature aligns with Heimdall's role as a security governance layer.
          required: true