FAQ
Following are the issues and resolutions for Tree Structure.
Inappropriate Display of Caret Symbols for Folders Without Subfolders
Starting this release, the carte icon will not appear when there are no folders and respective subfolders.
Loss of Selected Folder State
The folder ID will be stored in the query parameters to maintain context with each refresh action. When the page is refreshed, the system will retrieve the following:
The hierarchy is directly associated with the selected folder.
Only the first-level subfolders of the selected folder.
The first-page subfolders of the selected folder's parent are loaded by loading the current folder's subfolders.
Instead of re-fetching the entire tree structure, the folder's state will be preserved using a reducer. This method will efficiently maintain the folder's state across navigations and refreshes. This improves the user experience by minimizing load times and preserving the state across page refreshes, thereby streamlining navigation within the system.
Refetching of fetched data
Enhanced data fetching and display mechanism when you click the caret symbol next to a folder
If data for that folder has already been fetched, the caret should toggle (hide/show) the subfolders.
If the data has not been fetched, fetch and display all subfolders upon this interaction.
Clicking on the checkbox associated with a folder should only toggle the selection or clear the folder. It should not trigger data fetching.
If you click anywhere else in the folder row (excluding the caret and checkbox), The data for that folder has not already been fetched.
This approach aims to streamline interactions and reduce unnecessary data fetching, improving efficiency and user experience when navigating through folders.
Inconsistent Tree Sorting Across Interfaces
To ensure consistency and improve user experience across various interfaces, the backend sorts trees in Requirements, Test Repository, and Test Execution based on the "Last Updated" timestamp. This approach ensures that the most recently modified trees are placed at the top of the list, displaying the latest worked-on items first.
Display of Folder Data on the Test Execution Page
The system can now display up to 2600 subfolders without extra pagination control.
Unassigned Folders Displayed in Test Execution Tree View
Users must show only folders directly assigned to the user by:
Including each folder's direct parent's name to avoid confusion.
Introduced pagination to display a large number of folders.
Display nodes under each phase to simplify test execution presentation.
Top Node Selection Fails to Map Unloaded Child Nodes
The new implementation ensures more accurate mapping of requirements to test cases across dynamically loaded tree structures, addressing concurrency issues. The proposed solution involves significant modification to better manage node selection within partially loaded trees due to pagination.