Skip to content

Commit 48e43aa

Browse files
authored
Merge pull request #679 from lightspeedwp/568-add-issue-templates
568 add issue templates
2 parents ef96e47 + 54192f0 commit 48e43aa

File tree

8 files changed

+222
-0
lines changed

8 files changed

+222
-0
lines changed
Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
name: Bug report
3+
about: Report a bug
4+
title: "[Bug] "
5+
labels: bug, needs-triage
6+
assignees: ''
7+
---
8+
9+
**Describe the bug**
10+
A clear and concise description of what the bug is.
11+
12+
**To Reproduce**
13+
Steps to reproduce the behavior:
14+
1. Go to '...'
15+
2. Click on '....'
16+
3. Scroll down to '....'
17+
4. See error
18+
19+
**Expected behavior**
20+
A clear and concise description of what you expected to happen.
21+
22+
**Screenshots**
23+
If applicable, add screenshots to help explain your problem.
24+
25+
**WordPress Environment:**
26+
- WordPress Version: [e.g. 6.4]
27+
- PHP Version: [e.g. 8.1]
28+
- Active Theme: [e.g. theme name]
29+
- Other Active Plugins: [list relevant plugins]
30+
31+
**Desktop (please complete the following information):**
32+
- OS: [e.g. iOS]
33+
- Browser [e.g. chrome, safari]
34+
- Version [e.g. 22]
35+
36+
**Smartphone (please complete the following information):**
37+
- Device: [e.g. iPhone6]
38+
- OS: [e.g. iOS8.1]
39+
- Browser [e.g. stock browser, safari]
40+
- Version [e.g. 22]
41+
42+
**Additional context**
43+
Add any other context about the problem here.
44+
45+
**Maintainer Checklist** *(for maintainers use)*
46+
- [ ] Bug confirmed and reproducible
47+
- [ ] Fix implemented
48+
- [ ] Changelog updated
49+
- [ ] Tests added/updated
50+
- [ ] Documentation updated (if applicable)
Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea or propose a new feature for this extensions
4+
title: "[Feature request] "
5+
labels: enhancement, needs-triage
6+
assignees: ''
7+
---
8+
9+
**Feature area**
10+
- [ ] Tour management
11+
- [ ] Booking system
12+
- [ ] Frontend display
13+
- [ ] Admin interface
14+
- [ ] Integrations
15+
- [ ] Other: ___
16+
17+
**Is your feature request related to a problem? Please describe.**
18+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
19+
20+
**Describe the feature**
21+
A clear and concise description of what you would like to see implemented. Include any specific functionality or user interface elements you envision.
22+
23+
**Use case**
24+
Describe how this would help tour operators or their customers.
25+
26+
**Describe alternatives you've considered**
27+
A clear and concise description of any alternative solutions or features you've considered.
28+
29+
**Additional context**
30+
Add any other context or screenshots about the feature request here.
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
name: Docs request
3+
about: Request additional documentation or clarification on existing documentation
4+
title: "[Docs] "
5+
labels: documentation, needs-triage
6+
assignees: ''
7+
---
8+
9+
**What documentation is needed?**
10+
Please describe the specific documentation you are requesting or the area that needs clarification.
11+
12+
**Why is this documentation important?**
13+
Explain how this documentation would help you or others better use the extension.
14+
15+
**Additional context**
16+
Add any other relevant information or examples here.
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
name: General question
3+
about: Ask a question that doesn’t fit into other categories, helping to keep other
4+
issue types focused
5+
title: "[Question] "
6+
labels: question, needs-triage
7+
assignees: ''
8+
---
9+
10+
**Question**
11+
Please describe your question in detail.
12+
13+
**Context**
14+
Provide any relevant context or background information that might help in answering your question.
15+
16+
**Additional context**
17+
Add any other information or details that might be helpful in addressing your question.
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
name: Integration Issue
3+
about: Report issues related to integrating the extension with other tools or platforms
4+
title: "[Integration] "
5+
labels: integration, needs-triage
6+
assignees: ''
7+
---
8+
9+
**Describe the integration issue**
10+
A clear and concise description of the issue you are experiencing while integrating the extension with another tool or platform.
11+
12+
**Steps to reproduce the issue**
13+
Detailed steps to reproduce the integration issue:
14+
1. Go to '...'
15+
2. Perform '...'
16+
3. Notice the integration issue in '...'
17+
18+
**Expected behavior**
19+
A clear and concise description of what you expected the integration to do.
20+
21+
**Affected tools/platforms**
22+
Please specify the tools or platforms you are trying to integrate with (e.g., Jira, Slack, etc.).
23+
24+
**Screenshots or logs**
25+
If applicable, please add screenshots, logs, or other relevant files that can help diagnose the integration issue.
26+
27+
**Additional context**
28+
Add any other relevant information or examples here.
Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
name: Performance issue
3+
about: Report performance-related issues such as slow response times or high resource
4+
usage
5+
title: "[Performance] "
6+
labels: performance, needs-triage
7+
assignees: ''
8+
---
9+
10+
**Describe the performance issue**
11+
A clear and concise description of the performance issue you are experiencing.
12+
13+
**Steps to reproduce the issue**
14+
Detailed steps to reproduce the performance issue:
15+
1. Go to '...'
16+
2. Execute '...'
17+
3. Monitor the performance in '...'
18+
4. Notice the slow response/high resource usage in '...'
19+
20+
**Expected behavior**
21+
A clear and concise description of what you expected the performance to be like.
22+
23+
**Screenshots or logs**
24+
If applicable, add screenshots, logs, or other relevant files that can help diagnose the performance issue.
25+
26+
**Environment (please complete the following information):**
27+
- OS: [e.g., Windows 10, macOS Big Sur]
28+
- Version of the extension: [e.g., 1.0.0]
29+
- Other relevant environment details:
30+
31+
**Additional context**
32+
Add any other context about the performance issue here, such as specific conditions under which it occurs (e.g., only with large files, after a certain action, etc.).
Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
name: User Experience Feedback
3+
about: Share feedback on the usability and interface design of the extension
4+
title: "[UX] "
5+
labels: UX, needs-triage
6+
assignees: ''
7+
---
8+
9+
**Describe your experience**
10+
A brief description of your experience using the extension, including what you liked and what could be improved.
11+
12+
**Suggestions for improvement**
13+
Any ideas or suggestions you have for enhancing the user experience.
14+
15+
**Screenshots**
16+
If applicable, please add screenshots that highlight the user experience issues or areas for improvement.
17+
18+
**Additional context**
19+
Add any other relevant information or examples here.

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: Bug report
4+
description: Report a bug or issue with the Tour Operator plugin
5+
labels: [bug]
6+
path: 01-bug-report.md
7+
- name: Feature request
8+
description: Suggest a new feature or enhancement for the plugin
9+
labels: [enhancement]
10+
path: 02-feature_request.md
11+
- name: Documentation request
12+
description: Request improvements or additions to documentation
13+
labels: [documentation]
14+
path: 03-docs-request.md
15+
- name: General question
16+
description: Ask a general question about the plugin usage
17+
labels: [question]
18+
path: 04-general-question.md
19+
- name: Integration issue
20+
description: Report problems with third-party integrations
21+
labels: [integration]
22+
path: 05-integration-issue.md
23+
- name: Performance issue
24+
description: Report performance-related problems or slowdowns
25+
labels: [performance]
26+
path: 06-performance-issue.md
27+
- name: User experience feedback
28+
description: Provide feedback on user experience and interface
29+
labels: [ux, feedback]
30+
path: 07-user-experience-feedback.md

0 commit comments

Comments
 (0)