Skip to content

Commit b638d11

Browse files
committed
Reduce issue template complexity
Cut down on the number of sections of the user stories. This should increase focus on the most important points. Remove all the instructions how to fill out the template except the first (per template). The headings should be clear enough. The first instruction remains as a starting point.
1 parent 81edae5 commit b638d11

File tree

2 files changed

+2
-49
lines changed

2 files changed

+2
-49
lines changed

.github/ISSUE_TEMPLATE/01-user_story.md

Lines changed: 1 addition & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -17,25 +17,8 @@ assignees: ''
1717
1818
## Confirmation
1919

20-
*List one or more acceptance criteria with which to confirm that the problem has been solved.*
21-
22-
### QA Hints
23-
24-
*If necessary, give some hints for the QA how to setup the scenario or how to check the points of the confirmation.*
25-
26-
# Development
27-
2820
## Links
2921

30-
*Any links that help explain the problem or the desired solution, e.g.:*
31-
- *Customer Tickets*
32-
- *External Specifications*
33-
- *Documentation*
34-
35-
## Hints
36-
37-
*Any tips for the developer how to implement the solution.*
22+
# Development
3823

3924
## Progress
40-
41-
- *List all pull requests that created to implement the solution*

.github/ISSUE_TEMPLATE/02-bug_report.md

Lines changed: 1 addition & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -9,48 +9,18 @@ assignees: ''
99

1010
# Bug Report
1111

12-
*A clear and concise description of what the bug is.*
12+
*Start with a clear and concise description of what the bug is. Then try to fill out the points below.*
1313

1414
## Steps To Reproduce
1515

16-
*Steps to reproduce the behavior:*
17-
1816
1. ...
1917

2018
## Expected behavior
2119

22-
*A clear and concise description of what you expected to happen.*
23-
2420
## Screenshots
2521

26-
*If applicable, add screenshots to help explain your problem.*
27-
28-
## System Environment and Configuration
29-
30-
*A description of the system the error appeared on with any details of the environment and/or configuration that may be helpful.*
31-
3222
## Links
3323

34-
- *Links to customer tickets.*
35-
- *Any links to external content that is relevant to the bug, e.g. feature or interface documentation.*
36-
37-
## Additional context
38-
39-
*Add any other context about the problem here.*
40-
4124
# Development
4225

43-
## Links
44-
45-
*Any links that help explain the problem or the desired solution, e.g.:*
46-
- *Customer Tickets*
47-
- *External Specifications*
48-
- *Documentation*
49-
50-
## Hints
51-
52-
*Any tips for the developer how to implement the solution.*
53-
5426
## Progress
55-
56-
- *List all pull requests that created to implement the solution*

0 commit comments

Comments
 (0)