LWM-Linux/IssueTemplate.md

79 lines
2.2 KiB
Markdown

## Issue Description
[Describe the issue or bug in detail]
## Steps to Reproduce
[Provide a clear set of steps to reproduce the issue]
## Expected Behavior
[Describe what you expected to happen]
## Actual Behavior
[Describe what actually happened]
## Additional Information
[Provide any additional information or context that might be helpful]
## Screenshots (if applicable)
[Insert any relevant screenshots here]
## Environment
[Specify the environment where the issue occurred (e.g., operating system, browser, version)]
## Possible Solution
[If you have any ideas on how to solve the issue, you can mention them here]
## Here are some commonly used prefixes for issues and commits, each serving a specific purpose:
feat:: Introduces a new feature to the codebase.
fix:: Fixes a bug in your codebase.
docs:: Changes to documentation only.
style:: Code changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc).
refactor:: A code change that neither fixes a bug nor adds a feature.
perf:: A code change that improves performance.
test:: Adding missing tests or correcting existing tests.
build:: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm).
ci:: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs).
chore:: Other changes that don't modify src or test files.
revert:: Reverts a previous commit.
## Priority Level
[Indicate the priority level of this issue (e.g., Low, Medium, High, Critical)]
## Impact
[Describe the impact this issue has on your project or workflow]
## Workaround
[If there is a known workaround for this issue, describe it here]
## Logs and Error Messages
[Attach any relevant logs or error messages that could help in diagnosing the issue]
## Suggested Assignees
[Suggest potential team members who might be best suited to address this issue]
## Tags
[Add relevant tags to categorize and filter the issue (e.g., frontend, backend, accessibility)]
## Related Issues
[Link any related issues here to provide additional context]
## Deadline
[If there is a specific deadline by which this issue needs to be resolved, mention it here]