Issues

Please use the public community repository for all bug reports and feature requests:

• Bug report template: https://github.com/broadcreate/Lexipt-Community/issues/new?template=bug_report.yml
• Feature request template: https://github.com/broadcreate/Lexipt-Community/issues/new?template=feature_request.yml
• Issue list: https://github.com/broadcreate/Lexipt-Community/issues

Report Checklist

• Lexipt version
• Operating system version
• Reproduction steps
• Expected behavior
• Actual behavior
• Logs or screenshots

Severity Suggestion

• critical: data loss, startup failure, major workflow blocked
• high: major feature broken with workaround difficulty
• medium: functional defect with acceptable workaround
• low: UI/copy/style improvement

Temporary Questions (To Be Completed)

TODO

• Should we enforce issue labels by template?

  • Recommendation: Yes, enforce issue labels by template to ensure consistent categorization. Use GitHub's label enforcement features or automation to apply labels based on template selection (e.g., bug reports get "bug", feature requests get "enhancement").

• Should bug reports require anonymized sample files?

  • Recommendation: Yes for security and privacy. Require users to anonymize any sample files (remove personal data, replace with placeholders). Provide clear guidelines in the template on how to prepare samples.

• Do we need SLA targets by issue severity?

  • Recommendation: Yes, establish SLA targets to manage expectations and prioritize work:
    • Critical: Response within 24 hours, resolution within 1 week
    • High: Response within 48 hours, resolution within 2 weeks
    • Medium: Response within 1 week, resolution within 1 month
    • Low: Response within 2 weeks, best-effort resolution