# 2ticketss

2 complementary command-line tools for GitHub issue management
- **00-jira-to-gh-issues**: A Rust tool that converts Jira CSV exports to GitHub issue markdown files compatible with gh-issue-generator. It handles messy CSV data and preserves issue metadata
- **01-gh-issue-generator**: A Rust tool that creates GitHub issues from Markdown files with YAML front matter. It parses structured Markdown, supports batch processing, and integrates with GitHub CLI

01-gh-issue-generator/examples/issues/bugs/login-error.md

@@ -0,0 +1,57 @@
+---
+title: Fix login error with special characters in password
+status: ready
+labels:
+  - bug
+  - security
+  - critical
+assignees:
+  - backend-dev
+milestone: v1.0.1
+project: Bug Fixes
+parent: 123
+---
+
+# Login Error with Special Characters in Password
+
+## Bug Description
+
+Users are unable to log in when their password contains certain special characters (specifically `#`, `&`, and `%`). The login form submits successfully but returns a 400 error.
+
+## Steps to Reproduce
+
+1. Create a user account with a password containing one of the special characters: `#`, `&`, or `%`
+2. Log out of the account
+3. Attempt to log in with the correct credentials
+4. Observe the error message and failed login
+
+## Expected Behavior
+
+Login should succeed with the correct credentials regardless of special characters in the password.
+
+## Actual Behavior
+
+When submitting the login form with credentials containing special characters, the request fails with a 400 Bad Request error. The following error appears in the console:
+
+```
+POST https://api.example.com/auth/login 400 (Bad Request)
+Error: {"error":"Invalid request parameters"}
+```
+
+## Environment
+
+- **Browser**: Chrome 98.0.4758.102, Firefox 97.0.1
+- **OS**: Windows 10, macOS Monterey 12.2.1
+- **Backend Version**: v1.2.3
+
+## Technical Analysis
+
+Initial investigation suggests that the password is not being properly URL-encoded before being sent to the backend, causing the server to reject the request.
+
+## Possible Fix
+
+Add proper URL encoding to the login form submission or update the backend to handle special characters in the request payload correctly.
+
+## Severity
+
+Critical - Affects user authentication and prevents access to the application. 

01-gh-issue-generator/examples/issues/feature.md

@@ -0,0 +1,51 @@
+---
+title: Add dark mode support
+status: ready
+labels:
+  - enhancement
+  - ui
+  - accessibility
+assignees:
+  - ui-designer
+  - frontend-dev
+milestone: v2.0
+project: UI Improvements
+---
+
+# Dark Mode Support
+
+## Description
+
+We need to add a dark mode option to our application to improve accessibility and user experience in low-light environments.
+
+## Requirements
+
+- Toggle switch in user settings
+- System preference detection (respect user's OS preference)
+- Persistent setting (remember user's choice)
+- Properly themed components for all UI elements
+- Appropriate contrast ratios for accessibility compliance
+
+## Tasks
+
+- [ ] Create dark color palette
+- [ ] Add theme toggle component in settings
+- [ ] Set up theme context/provider
+- [ ] Implement system preference detection
+- [ ] Refactor components to use theme variables
+- [ ] Add theme persistence in user settings
+- [ ] Test across all major browsers and devices
+- [ ] Verify accessibility compliance
+
+## Technical Approach
+
+We should use CSS variables and a theme provider context to implement the theming system. This will allow us to switch themes without requiring a page reload.
+
+## Resources
+
+- [WCAG Contrast Guidelines](https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html)
+- [Material Design Dark Theme](https://material.io/design/color/dark-theme.html)
+
+## Implementation Notes
+
+The main challenges will be ensuring all third-party components also respect the theme, and making sure we maintain proper contrast ratios in both themes.