Bug 824370
Summary: | [RFE]: treeview should be sortable alphabetically | ||
---|---|---|---|
Product: | [Other] TCMS | Reporter: | Vladimir Benes <vbenes> |
Component: | Web UI | Assignee: | Yang Ren <ryang> |
Status: | ASSIGNED --- | QA Contact: | Nobody <nobody> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.0 | CC: | jcai, junzhang, ryang, vchen, xkuang, yuwang |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | 4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-07 05:52:53 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Vladimir Benes
2012-05-23 11:08:54 UTC
Not necessary for now viewing there is no such big tree present. (In reply to comment #1) > Not necessary for now viewing there is no such big tree present. is it really needed to close this bug? We plan to have all desktop components in one tree (~ 700) I was forced to create some branches but it may happen that more than 50 will be in one branch. Please keep in mind that the tree is still not complete just search in it is a bit difficult now and will be even worse later on. see: https://tcms.engineering.redhat.com/plan/5517/#treeview and go into KDE or GNOME branch.. there are more than one page of children in it. I think alphabetical ordering is even more appropriate than ordering by numbers in such case. We will consider to implement it on TCMS 4.0. The default order should be ID descending, as most of the user need it. We can consider a button to sort the plan by alphabetic. |