Plan views don't honor swim lane order

[shefalijoshi]

Summary

Plan (and Gantt) views should display swim lanes in the order they are received.

Expected vs Current Behavior

Provide a way of specifying swim lane order.

Steps to Reproduce

1. In the VIPER project changing the order of the LANES property does not result in redrawing of the Plan view to reflect the change.

Environment

• Open MCT Version:
• Deployment Type:
• 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?
• [x] 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

[shefalijoshi]

Testing instructions: In the VIPER deployment

1. View a plan and note the order of it's swimlanes
2. Using the couchdb fauxton interface, change the order of swimlanes in the Lanes property of a VIPER plan.
3. Ensure that the plan view reflects the change.

In a NON-VIPER deployment (like local)

1. View a plan that does not have a groupIds configuration.
2. Ensure that swimlanes are still visible.

[rukmini-bose]

This works for Plans, but Gantt Charts aren't translating the correct order from a plan imported into Open MCT.
Testathon 2/1/2024

[ozyx]

Verified for regular Plans, but Gantt Charts display swimlanes out of order by default

[charlesh88]

Testathon 2024-02-01: NOT fixed, Gantt view doesn't display the same order as the built-in Plan view, which appears to show the correct order:

Plan view:

Gantt Chart view: