Actions
Bug #16537
closedNode never updated because of nonEmpty in place of isEmpty
Status:
Released
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
During upmerge of parent task, a nonEmpty replaced a isEmpty leading to never actually updating nodes.
Actions