Test Suite Execution Order into Test Plan

The current random behavior while adding the existing Test Suite(s) with correspondent Test Case(s) into a Test Plan seems to not be the desired one.
Unfortunately, the Execution Order inside of a Test Suite should be taken into consideration while adding this Test Suites into a Test Plan. The importance of the order is priority and should not be optional, like in this case (cross-check with the ISQTB Procedure Scheduling)

For example, we have two test suites with cases:

• Test Suite "A": TC 1, TC 2, 3

• Test Suite "B": TC 7, TC 8, TC 9

Adding this Test Suites (A and then B) into Test Plan, our desired behavior should be:

• Test Suites: "A", "B" (in order)

• Test Cases Order: TC 1, TC 2, TC 3, TC 7, TC 8, TC 9

In ETM, in Test Case section we will have this behavior:

• Test Suites: "A", "B" (they will be ordered correctly)

• Test Cases Order: TC 3, TC 1, TC 2, TC 9, TC 7, TC 8 ( or other random values)
  

We know you have a normal order while trying to run this Test Suite(s) into Test Plan, but we use the REST API and this order of Test Cases (from TP section) is essential for our frameworks to work properly.

Picture description by steps:

• adding_suites_into_test_plan -> Add Existing Test Suite

• incorrect_oredered_ids_2 -> Test Suite(s) data (test cases execution order)

• incorrect_oredered_ids -> Test Cases Section from Test Plan ( test cases ids seems to be mixed up randomly and not kept in the same order as in Suite)