-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
924383: Implement UG for Sankey Chart. #5216
base: 925942-sankey-ug
Are you sure you want to change the base?
Conversation
…ng node entry in the TOC.html file
The running CI Job is terminated due to changes committed on the source branch for this Merge Request and CI triggered for latest commit. |
CI Status: ABORTED ❌ |
Build Status: INQUEUE 🕒 |
Build Status: INPROGRESS 🔃 |
CI Status: FAILURE ❌ |
Build Status: INPROGRESS 🔃 |
CI Status: FAILURE ❌ |
Build Status: INPROGRESS 🔃 |
CI Status: FAILURE ❌ |
documentation(922418):Resolved conflict issue
Build Status: INPROGRESS 🔃 |
CI Status: FAILURE ❌ |
Build Status: INPROGRESS 🔃 |
CI Status: FAILURE ❌ |
Build Status: INPROGRESS 🔃 |
CI Status: FAILURE ❌ |
Build Status: INPROGRESS 🔃 |
CI Status: FAILURE ❌ |
Build Status: INPROGRESS 🔃 |
CI Status: SUCCESS ✅ |
Bug description
Root cause
Solution description
Reason for not identifying earlier
Guidelines not followed. If yes, provide which guideline is not followed.
Guidelines not given. If yes, provide which/who need to address.
Tag label
update-guideline-coreteam
orupdate-guideline-productteam
.If any other reason, provide the details here.
Areas tested against this fix
Provide details about the areas or combinations that have been tested against this code changes.
Test Scenarios
Is it a breaking issue?
Yes, Tag
breaking-issue
.NO
If yes, provide the breaking commit details / MR here.
Action taken
What action did you take to avoid this in future?
Feature matrix document updated
Automation details - Mark
Is Automated
field as (Yes, Manual, Not Applicable) in corresponding JIRA task once the bug is automated.If the same issue is reproduced in ej2, what will you do?
Is this common issue need to be addressed in the same component or on other components in our platform?
needs-attention-coreteam
Output screenshots
Before Fix :
After Fix :
Blazor Checklist
Confirm whether this feature is ensured in both Blazor Server and WASM
Is there any new API or existing API name change?
Is there any existing behavior change due to this code change?
breaking-change
label.Do the code changes cause any memory leak and performance issue? (Test only if you suspect that your code may cause problem)
Reviewer Checklist