Plans in Time Strip don't always calculate row spans correctly

[charlesh88]

Summary

1. Putting a Plan in a Gantt view and hiding rows will cause row spans to be calculated incorrectly when placing that Gantt view in a Time Strip.
2. Some Plans just by themselves are also showing this problem. Is this possibly a flaw in that particular Plan? Do plans include metadata like rowNumber that can be out of sync with the actual number of rows?

Bad calcs on row spans

ERT-10_005 is a Plan and is messed up, but so is ert-467_107 and it's fine. GC Test is a Gantt view where I hid 6 of 8 rows.

Steps to Reproduce

1. Put a Plan in a Gantt view and hide some its rows.
2. Put that Gantt view in a Time Strip.

Environment

• Open MCT Version: 4.1.0-next
• Deployment Type: openmct-events
• OS:
• Browser:

Impact Check List

• Data loss or misrepresented data?
• Regression? Did this used to work or has it always been broken?
• Is there a workaround available?
• Does this impact a critical component?
• Is this just a visual bug with no functional impact?
• Does this block the execution of e2e tests?
• Does this have an impact on Performance?

Additional Information