[TRACE-X] Make parts table mass data ready #1173
Labels
ic
represents features/dependencies to the industry core
Prep-R25.06
trace-x
Feature/Bug for Trace-x component
Overview
As a user I want to easily filter all parts which interests me for tracing down even a large data sets.
Explain the topic in 2 sentences
The current approach filtering is cumbersome and not convenient, when a user wants to trace down a bulk of parts which for example might have quality issues. That is why we need a more advanced approach to filter including filtering with the goal filter even with large filter criteria like a set of hundreds of ids.
What's the benefit?
What are the Risks/Dependencies ?
Detailed explanation
It is important reorganize the current filter options in an user friendly way. We want to propose multiple enhancements like an advanced search filter menu, an optimized search bar and optimized user information like the display of the current filter in a user friendly as well as caching and persistence of last filters.
Current implementation
Non consistent approach of quick filters, global and local table filters.
Proposed improvements
Advanced Search

Optimized Search Bar
Search with a large set of ids via clipboard or import
Explain current applied filter
Saved last search
Feature Team
Cofinity-X
Contributor
UX-Design:
@Cofinity-UX
@sophiepotyka
Committer
User Stories
Acceptance Criteria
Test Cases
Test Cases (Gherkin)
Feature: Global Search Bar Paste Functionality
Scenario: User pastes text into the global search bar
Given the user is on the parts page
When the user copies a text value from a text, excel or csv file
And the user pastes the copied text into the global search bar
Then the pasted text should appear in the global search bar
And the search should be performed upon user action
Scenario: User imports search values via file upload
Given the user is on the parts page
When the user uploads a valid file containing search values
Then the search values should be extracted from the file
And they should be populated in the global search bar
And the search should be performed upon user action
Scenario: User accesses advanced local filters with a button click
Given the user is on the parts page
When the user clicks on the advanced filters button
Then the advanced local filtering options should be displayed
Scenario: Advanced local filtering integrates with global search
Given the user has performed a search in the global search bar
And the advanced filters panel is open
When the user applies a local filter
Then the search results should be refined according to both the global search and local filter criteria
Scenario: Application handles more than 100 search values
Given the user is on the parts page
And the user has entered more than 100 search values
Or the user has uploaded a file containing more than 100 search values
When the search is executed
Then the application should successfully process all search values
And the correct results should be displayed without performance issues
Architectural Relevance
The following items are ensured (answer: yes) after this issue is implemented.
In the context of the standards 126 and 127, typically only one is applicable, depending on the specific use case. Please cross out one of the two standards that does not apply.
Justification: (Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)
Additional information
The text was updated successfully, but these errors were encountered: