Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

Commit ce93a2c

Browse files
v30.1.37
1 parent af38459 commit ce93a2c

File tree

2 files changed

+154
-0
lines changed

2 files changed

+154
-0
lines changed

‎.github/PULL_REQUEST_TEMPLATE/Bug.md

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
### Bug description
2+
Clearly and concisely describe the problem (this cannot be empty).
3+
4+
### Root cause
5+
Briefly describe the root cause and analysis of the problem.
6+
If there is an internal discussion on the forum, provide the link.
7+
8+
### Solution description
9+
Describe the changes made in the code in detail for the reviewers.
10+
11+
### Reason for not identifying earlier
12+
* [ ] Guidelines not followed. If yes, provide which guideline is not followed.
13+
14+
* [ ] Guidelines not given. If yes, provide which/who need to address.
15+
Tag label `update-guideline-coreteam` or `update-guideline-productteam`.
16+
17+
* [ ] If any other reason, provide the details here.
18+
19+
### Areas tested against this fix
20+
Provide details about the areas or combinations that have been tested against this code changes.
21+
* [ ] Tested against feature matrix. [Feature matrix link](https://syncfusion.sharepoint.com/sites/EJ2ProductOwners/Shared%20Documents/Forms/AllItems.aspx?viewid=ae81c682%2D3d0f%2D462a%2Db8ec%2D7358748d489d&id=%2Fsites%2FEJ2ProductOwners%2FShared%20Documents%2FGeneral%2FFeature%20Matrix%20%2D%20Documents)
22+
* [ ] NA
23+
24+
### Is it a breaking issue?
25+
* [ ] Yes, Tag `breaking-issue`.
26+
* [ ] NO
27+
28+
If yes, provide the breaking commit details / MR here.
29+
30+
### Action taken
31+
What action did you take to avoid this in future?
32+
33+
Feature matrix document updated
34+
* [ ] Yes
35+
* [ ] NO
36+
* [ ] NA
37+
38+
Automation details - Mark `Is Automated` field as (Yes, Manual, Not Applicable) in corresponding JIRA task once the bug is automated.
39+
* [ ] BUnit, share corresponding MR.
40+
* [ ] E2E or Manual Automation using tester - Make sure all items are automated with priority before release which can be tracked in [automation dashboard](https://syncfusion.atlassian.net/secure/Dashboard.jspa?selectPageId=43396).
41+
42+
If the same issue is reproduced in ej2, what will you do?
43+
* [ ] Resolved. Provide MR link.
44+
* [ ] NO. Created task to track it. Share task link.
45+
* [ ] NA
46+
47+
Is this common issue need to be addressed in the same component or on other components in our platform?
48+
* [ ] Yes - Need to check in other components, tag `needs-attention-coreteam`
49+
* [ ] No
50+
51+
### Output screenshots
52+
Post the output screenshots if an UI is affected or added due to this bug.
53+
54+
### Blazor Checklist
55+
Confirm whether this feature is ensured in both Blazor Server and WASM
56+
* [ ] NA
57+
* [ ] Yes
58+
* [ ] NO
59+
60+
Is there any new API or existing API name change?
61+
* [ ] Yes. If yes, Provide API Review task link.
62+
* [ ] NO
63+
64+
Is there any existing behavior change due to this code change?
65+
* [ ] Yes. Add `breaking-change` label.
66+
* [ ] NO
67+
68+
69+
Do the code changes cause any memory leak and performance issue? (Test only if you suspect that your code may cause problem)
70+
* [ ] Yes
71+
* [ ] NO
72+
73+
## Reviewer Checklist
74+
* [ ] All provided information are reviewed and ensured.
Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,80 @@
1+
### Feature description
2+
Clearly and concisely describe the feature.
3+
4+
### Requirement and specification document.
5+
Share the JIRA task which is attached with the requirement and specification document or directly share the document.
6+
- Even for a small feature, draft a requirement and specification document and attach it in the task.
7+
8+
### API Review task
9+
Provide task link.
10+
11+
### Output screenshots
12+
Post the output screenshots if an UI is affected or added due to this feature.
13+
14+
### Feature matrix document
15+
16+
Feature matrix document updated against this feature and committed in this [common location] (https://syncfusion.sharepoint.com/sites/EJ2ProductOwners/Shared%20Documents/Forms/AllItems.aspx?viewid=ae81c682%2D3d0f%2D462a%2Db8ec%2D7358748d489d&id=%2Fsites%2FEJ2ProductOwners%2FShared%20Documents%2FGeneral%2FFeature%20Matrix%20%2D%20Documents) .
17+
* [ ] Yes
18+
* [ ] NO
19+
* [ ] NA
20+
21+
Provide the details about the areas or combinations which have been tested against this code changes.
22+
* [ ] Tested against feature matrix.
23+
24+
### Feature acceptance criteria (Test-case document)
25+
Draft the test cases in excel and attach it in the MR itself. The automation must be covered based on this positive and worst-case test-cases.
26+
27+
### Automation details
28+
Mark 'Is Automated' field as (Yes, Manual, Not Applicable) in corresponding JIRA task once the feature is automated.
29+
* [ ] BUnit, share corresponding MR.
30+
* [ ] E2E or Manual Automation using tester - Make sure all items are automated with priority before release which can be tracked in [automation dashboard](https://syncfusion.atlassian.net/secure/Dashboard.jspa?selectPageId=43396).
31+
32+
### Test bed sample location
33+
Provide the test bed sample location where the code reviewers can review the new feature’s behaviors.
34+
35+
### Feature completion checklist
36+
37+
UX changes got approval if UI is added or modified?
38+
* [ ] Yes. Provide Task link.
39+
* [ ] NO
40+
* [ ] NA
41+
42+
Drafted UG for this feature?
43+
* [ ] Yes, provide MR link.
44+
* [ ] NO, provide task link.
45+
* [ ] NA
46+
47+
Content team reviewed the UI content changes.
48+
* [ ] Yes. Provide MR or Task link.
49+
* [ ] NO
50+
* [ ] NA
51+
52+
Is this the common feature which needs to be addressed in the same component or on other components in our platform?
53+
* [ ] Yes. If we need to check in other components, tag "needs-attention-coreteam"
54+
* [ ] NO
55+
56+
Is there any existing behavior change due to this code change?
57+
* [ ] Yes. If So, add `breaking-change` label.
58+
* [ ] NO
59+
60+
### Blazor Checklist
61+
Confirm whether the ensured feature is in both Blazor Server and WASM.
62+
* [ ] Yes
63+
* [ ] NO
64+
* [ ] NA
65+
66+
Do the code changes cause any memory leak and performance issue?
67+
* [ ] Yes
68+
* [ ] NO
69+
70+
## Reviewer Checklist
71+
* [ ] Reviewed feature matrix document modifications and reviewed developer testing report against the feature matrix reviewed.
72+
* [ ] Testbed sample ensured.
73+
* [ ] Coverage report checked.
74+
* [ ] Ensured the code changes meet the coding standard.
75+
* [ ] Confirming script changes made in this merge request can't be achieved in C#.
76+
77+
Created task in Blazor to synchronize if the feature is not available and applicable.
78+
* [ ] NA
79+
* [ ] Yes, task link.
80+
* [ ] NO, share reason.

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /