Files

Jeremy cf6d3bd319 fix: resolve modal dropdown z-index conflicts across application

Restructure 7 modal components to use 3-layer architecture preventing
native select dropdown menus from being blocked by modal overlays.

Components fixed:
- ProxyHostForm: ACL selector and Security Headers dropdowns
- User management: Role and permission mode selection
- Uptime monitors: Monitor type selection (HTTP/TCP)
- Remote servers: Provider selection dropdown
- CrowdSec: IP ban duration selection

The fix separates modal background overlay (z-40) from form container
(z-50) and enables pointer events only on form content, allowing
native dropdown menus to render above all modal layers.

Resolves user inability to select security policies, user roles,
monitor types, and other critical configuration options through
the UI interface.

2026-02-05 19:03:37 +00:00

created

chore: move processed issue files to created/

2026-02-04 10:27:07 +00:00

_TEMPLATE.md

chore: clean .gitignore cache

2026-01-26 19:22:05 +00:00

modal_dropdown_handoff_contract.md

fix: resolve modal dropdown z-index conflicts across application

2026-02-05 19:03:37 +00:00

README.md

chore: clean .gitignore cache

2026-01-26 19:22:05 +00:00

README.md

docs/issues - Issue Specification Files

This directory contains markdown files that are automatically converted to GitHub Issues when merged to main or development.

How It Works

Create a markdown file in this directory using the template format
Add YAML frontmatter with issue metadata (title, labels, priority, etc.)
Merge to main/development - the docs-to-issues.yml workflow runs
GitHub Issue is created with your specified metadata
File is moved to docs/issues/created/ to prevent duplicates

Quick Start

Copy _TEMPLATE.md and fill in your issue details:

---
title: "My New Issue"
labels:
  - feature
  - backend
priority: medium
---

# My New Issue

Description of the issue...

Frontmatter Fields

Field	Required	Description
`title`	Yes*	Issue title (*or uses first H1 as fallback)
`labels`	No	Array of labels to apply
`priority`	No	`critical`, `high`, `medium`, `low`
`milestone`	No	Milestone name
`assignees`	No	Array of GitHub usernames
`parent_issue`	No	Parent issue number for linking
`create_sub_issues`	No	If `true`, each `## Section` becomes a sub-issue

Sub-Issues

To create multiple related issues from one file, set create_sub_issues: true:

---
title: "Main Testing Issue"
labels: [testing]
create_sub_issues: true
---

# Main Testing Issue

Overview content for the parent issue.

## Unit Testing

This section becomes a separate issue.

## Integration Testing

This section becomes another separate issue.

Manual Trigger

You can manually run the workflow with:

# Dry run (no issues created)
gh workflow run docs-to-issues.yml -f dry_run=true

# Process specific file
gh workflow run docs-to-issues.yml -f file_path=docs/issues/my-issue.md

Labels

Labels are automatically created if they don't exist. Common labels:

Priority: critical, high, medium, low
Type: feature, bug, enhancement, testing, documentation
Component: backend, frontend, ui, security, caddy, database