|
1 |
| -## Purpose |
2 |
| -> Describe the problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc. |
| 1 | +### Purpose |
| 2 | +<!-- Describe the problem, feature, improvement or the change introduces by the PR briefly. Add screenshots/GIFs if UI/UX changes are introduced. --> |
3 | 3 |
|
4 |
| -## Goals |
5 |
| -> Describe the solutions that this feature/fix will introduce to resolve the problems described above |
| 4 | +### Related Issues |
| 5 | +- |
6 | 6 |
|
7 |
| -## Approach |
8 |
| -> Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email [email protected] to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here. |
| 7 | +### Related PRs |
| 8 | +- |
9 | 9 |
|
10 |
| -## User stories |
11 |
| -> Summary of user stories addressed by this change> |
| 10 | +### Checklist |
| 11 | +- [ ] Manual test round performed and verified. |
| 12 | +- [ ] UX/UI review done on the final implementation. |
| 13 | +- [ ] Documentation provided. (Add links if there are any) |
| 14 | +- [ ] Unit tests provided. (Add links if there are any) |
12 | 15 |
|
13 |
| -## Release note |
14 |
| -> Brief description of the new feature or bug fix as it will appear in the release notes |
15 |
| -
|
16 |
| -## Documentation |
17 |
| -> Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact |
18 |
| -
|
19 |
| -## Training |
20 |
| -> Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable |
21 |
| -
|
22 |
| -## Certification |
23 |
| -> Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to [email protected] and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why. |
24 |
| -
|
25 |
| -## Marketing |
26 |
| -> Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable |
27 |
| -
|
28 |
| -## Automation tests |
29 |
| - - Unit tests |
30 |
| - > Code coverage information |
31 |
| - - Integration tests |
32 |
| - > Details about the test cases and coverage |
33 |
| -
|
34 |
| -## Security checks |
35 |
| - - Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no |
36 |
| - - Ran FindSecurityBugs plugin and verified report? yes/no |
37 |
| - - Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no |
38 |
| - |
39 |
| -## Samples |
40 |
| -> Provide high-level details about the samples related to this feature |
41 |
| -
|
42 |
| -## Related PRs |
43 |
| -> List any other related PRs |
44 |
| -
|
45 |
| -## Migrations (if applicable) |
46 |
| -> Describe migration steps and platforms on which migration has been tested |
47 |
| -
|
48 |
| -## Test environment |
49 |
| -> List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested |
50 |
| - |
51 |
| -## Learning |
52 |
| -> Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem. |
| 16 | +### Security checks |
| 17 | +- [ ] Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? |
| 18 | +- [ ] Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? |
0 commit comments