kinow
commented
8 years ago At the moment, the API returns the following for the navigation tree template:
[{"ancestor":"1-1","descendant":"1-1","length":"0","node_id":"1","node_type_id":"1","display_name":"Project A","created_at":"2016-06-02 07:06:31","updated_at":"2016-06-02 07:06:31","children":[{"ancestor":"2-1","descendant":"2-1","length":"0","node_id":"1","node_type_id":"2","display_name":"Test Suite A","created_at":"2016-06-02 07:06:31","updated_at":"2016-06-02 07:06:31","children":[]},{"ancestor":"2-2","descendant":"2-2","length":"0","node_id":"2","node_type_id":"2","display_name":"Test Suite B","created_at":"2016-06-02 07:06:31","updated_at":"2016-06-02 07:06:31","children":[{"ancestor":"2-3","descendant":"2-3","length":"0","node_id":"3","node_type_id":"2","display_name":"Test Suite D","created_at":"2016-06-02 07:06:31","updated_at":"2016-06-02 07:06:31","children":[{"ancestor":"3-2","descendant":"3-2","length":"0","node_id":"2","node_type_id":"3","display_name":"BB C01","created_at":"2016-06-03 09:06:06","updated_at":"2016-06-04 22:49:21","children":[]},{"ancestor":"3-3","descendant":"3-3","length":"0","node_id":"3","node_type_id":"3","display_name":"tc00001","created_at":"2016-06-04 10:06:37","updated_at":"2016-06-04 10:06:37","children":[]}]}]},{"ancestor":"2-4","descendant":"2-4","length":"0","node_id":"4","node_type_id":"2","display_name":"Test Suite C","created_at":"2016-06-02 07:06:31","updated_at":"2016-06-02 07:06:31","children":[]},{"ancestor":"2-6","descendant":"2-6","length":"0","node_id":"6","node_type_id":"2","display_name":"TD 000","created_at":"2016-06-03 08:06:28","updated_at":"2016-06-03 08:06:28","children":[]}]}]We would need a field (e.g. metadata) to hold extra information per node. So projects could have labels, and test cases labels + execution_type, and so it goes. Setting it to epic as this change needs more consideration, so we don't introduce something that we would regret in some years.
That would help users to easily find items, and organize their test suites.