Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TRACE-X] Make parts table mass data ready #1173

Open
1 of 21 tasks
rogocof opened this issue Jan 31, 2025 · 1 comment
Open
1 of 21 tasks

[TRACE-X] Make parts table mass data ready #1173

rogocof opened this issue Jan 31, 2025 · 1 comment
Assignees
Labels
ic represents features/dependencies to the industry core Prep-R25.06 trace-x Feature/Bug for Trace-x component

Comments

@rogocof
Copy link

rogocof commented Jan 31, 2025

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?

  • More convenient searching
  • Making the table ready to filter even for large input criteria sets
  • Make the filtering understandable and repeatable

What are the Risks/Dependencies ?

  • Search performance for large datasets to be analyzed
  • No 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
    Image

  • 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

Committer

User Stories

Acceptance Criteria

  • I can copy and paste values from other applications directly into the global search bar
  • I can import search values via file upload into the global search bar
  • I can access advanced local filters with a button click
  • The advanced (local) filtering is added to the filtering of the global search bar
  • The application can handle more than 100 search values

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

  • I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer)
@rogocof rogocof moved this to Inbox in Release Planning Jan 31, 2025
@rogocof rogocof added Prep-R25.06 trace-x Feature/Bug for Trace-x component labels Jan 31, 2025
@rogocof rogocof changed the title [TRACE-X]Make parts table mass data ready [TRACE-X] Make parts table mass data ready Jan 31, 2025
@rogocof rogocof added the ic represents features/dependencies to the industry core label Feb 27, 2025
@rogocof rogocof moved this from Inbox to Backlog in Release Planning Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ic represents features/dependencies to the industry core Prep-R25.06 trace-x Feature/Bug for Trace-x component
Projects
Status: Backlog
Development

No branches or pull requests

3 participants