Files
rxminder/.github/ISSUE_TEMPLATE/feature_request.yml
William Valentin e48adbcb00 Initial commit: Complete NodeJS-native setup
- Migrated from Python pre-commit to NodeJS-native solution
- Reorganized documentation structure
- Set up Husky + lint-staged for efficient pre-commit hooks
- Fixed Dockerfile healthcheck issue
- Added comprehensive documentation index
2025-09-06 01:42:48 -07:00

219 lines
6.3 KiB
YAML

name: ✨ Feature Request
description: Suggest a new feature or enhancement
title: '[FEATURE] '
labels: ['enhancement', 'needs-triage']
assignees: []
body:
- type: markdown
attributes:
value: |
Thank you for suggesting a new feature! Please provide detailed information to help us understand and evaluate your request.
- type: checkboxes
id: pre-check
attributes:
label: Pre-submission Checklist
description: Please verify these items before submitting
options:
- label: I have searched existing issues to ensure this is not a duplicate
required: true
- label: I have clearly described the problem and solution
required: true
- label: I have considered the user experience impact
required: true
- type: textarea
id: feature-description
attributes:
label: Feature Description
description: A clear and concise description of the feature you'd like to see
placeholder: Describe the feature...
validations:
required: true
- type: textarea
id: problem-statement
attributes:
label: Problem Statement
description: What problem does this feature solve? What user need does it address?
placeholder: This feature would solve...
validations:
required: true
- type: textarea
id: proposed-solution
attributes:
label: Proposed Solution
description: Describe your proposed solution in detail
placeholder: The feature should work by...
validations:
required: true
- type: textarea
id: medical-use-case
attributes:
label: Medical Use Case
description: How would this improve medication management or patient outcomes?
placeholder: This would help patients by...
validations:
required: true
- type: dropdown
id: user-type
attributes:
label: Primary User Type
description: Who would primarily benefit from this feature?
options:
- Patients managing their own medications
- Caregivers managing medications for others
- Healthcare providers
- System administrators
- All users
validations:
required: true
- type: dropdown
id: priority
attributes:
label: Priority Level
description: How important is this feature?
options:
- Low - Nice to have enhancement
- Medium - Would improve user experience
- High - Important for better outcomes
- Critical - Essential for core functionality
validations:
required: true
- type: dropdown
id: complexity
attributes:
label: Implementation Complexity
description: How complex do you think this feature would be to implement?
options:
- Simple (few hours)
- Medium (few days)
- Complex (few weeks)
- Major (significant architecture changes)
- Unknown
validations:
required: false
- type: checkboxes
id: affected-components
attributes:
label: Affected Components
description: Which parts of the system would this feature affect?
options:
- label: Frontend UI
- label: Authentication system
- label: Database schema
- label: Email notifications
- label: Mobile responsiveness
- label: API endpoints
- label: Third-party integrations
- label: Admin interface
- type: textarea
id: user-flow
attributes:
label: User Experience Flow
description: Describe the user journey for this feature
placeholder: |
1. User navigates to...
2. User clicks/taps...
3. System displays...
4. User completes...
validations:
required: true
- type: textarea
id: success-metrics
attributes:
label: Success Metrics
description: How will we measure the success of this feature?
placeholder: |
- User engagement metrics
- Medication adherence improvement
- User satisfaction scores
validations:
required: false
- type: checkboxes
id: design-requirements
attributes:
label: Design Requirements
description: What design considerations are important?
options:
- label: Follows existing design system
- label: Requires new design patterns
- label: Needs accessibility considerations
- label: Mobile-first approach needed
- label: Dark/light theme support
- type: checkboxes
id: security-privacy
attributes:
label: Security & Privacy Considerations
description: Does this feature involve sensitive data or security concerns?
options:
- label: Handles sensitive health data
- label: Requires data encryption
- label: Needs audit logging
- label: Affects user privacy
- label: Requires user consent
- label: GDPR compliance needed
- label: HIPAA considerations
- type: checkboxes
id: accessibility
attributes:
label: Accessibility Requirements
description: What accessibility features are needed?
options:
- label: Screen reader compatible
- label: Keyboard navigation support
- label: Color contrast compliant
- label: Mobile accessibility
- label: Language localization needed
- type: textarea
id: alternatives
attributes:
label: Alternative Solutions
description: What other approaches have you considered?
placeholder: I also considered...
validations:
required: false
- type: textarea
id: acceptance-criteria
attributes:
label: Acceptance Criteria
description: Define specific, testable criteria for when this feature is complete
placeholder: |
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3
validations:
required: true
- type: textarea
id: additional-context
attributes:
label: Additional Context
description: Any other context, mockups, or references
placeholder: Additional information...
validations:
required: false
- type: textarea
id: similar-features
attributes:
label: Similar Features
description: Are there similar features in other applications that work well?
placeholder: Similar implementations I've seen...
validations:
required: false