ISSUE #5299 - Ticket Filters in Tabular View

[The-Daniel]

This fixes #5299

Description

• Added ticket filters to tabular view
• Tickets card in the viewer should work the same as before

Acceptance Criteria

• Make sure the properties selection list includes all available options from all ticket template, regardless of status (active or deprecated), except this property: ticket template.
• Once the filter is applied, that property option is not available in the properties selection list anymore.
• If the filter is removed, that property option should reappear in the properties selection list.
• User able to add/remove/update filters.
• Applied filter should appear on the filter bar as a pill.
• Make sure the filtering displaying on the pill is correct.
• If the number of pills exceeding the length limit of the filter bar, user should be able to view all pills using scrollbar.
• The filter bar is collapsible.
• Update the table or all tables if grouping applied when applying/removing/updating filters.
• Make sure the filtering works as intended such that the filtered tickets inside the tables match with the result.
• Make sure the "Clear all" button removes all pills and updates the table or all tables if grouping applied.
• Existing functions which update the tables such as add/remove models, group by, filter completed tickets, add tickets must continue to work as before while the tables are filtered.
• Refresh the page/Re-enter the tabular view should restore everything back to default state. (e.g. Display all tickets of the selected ticket type with selected models and no grouping/filtering.)

[Copilot]

Pull Request Overview

This PR introduces ticket filter functionality to the tabular view, ensuring that the properties selection list is updated based on applied filters and integrates smoothly with existing ticket table updates.

• Added ticket filters in tabular view with corresponding filter pill UI and collapsible filter bar
• Updated selectors, sagas, and components to support filtering across both container and federation models
• Refactored and cleaned up related styles and helper functions

Reviewed Changes

Copilot reviewed 33 out of 33 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
frontend/src/v5/ui/routes/dashboard/projects/tickets/ticketsTable/newTicketMenu/useSelectedModels.ts	Introduces a new hook to conditionally select model IDs based on viewer context
frontend/src/v5/ui/routes/dashboard/projects/tickets/ticketsList/slides/ticketSlide.component.tsx	Minor cleanup by removing an extra blank line
frontend/src/v5/ui/routes/dashboard/projects/tickets/ticketsContent.component.tsx	Passes an extra parameter to fetchTemplates for enhanced detail fetching
frontend/src/v5/ui/routes/dashboard/projects/tickets/tickets.styles.ts	Renames container component and adjusts spacing along with removing unused chip styling
frontend/src/v5/ui/routes/dashboard/projects/tickets/ticketsContent.component.tsx	Updates API usage in saga to support multiple model IDs
Multiple UI components and helpers	Adjust imports and update logic to support new filter functionality and models selection

Comments suppressed due to low confidence (1)

frontend/src/v5/store/tickets/card/ticketsCard.sagas.ts:65

• The code calls isFederation as a function (isFederation(modelId)), but isFed is obtained from a selector and likely returns a boolean instead of a function. Update the logic to check the boolean value directly (e.g. use (isFederation ? API.Tickets.fetchFederationTickets : API.Tickets.fetchContainerTickets)).

const fetchModelTickets = await isFederation(modelId) ? API.Tickets.fetchFederationTickets : API.Tickets.fetchContainerTickets;

[The-Daniel]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[Didi-Kwan]

Round 1 testing is complete. Here is the test summary report with bug report inside.

[sanmont3drepo]

Here I think it should be getNonCompletedTicketFilters but as a hook.
useSetDefaultTicketFilters currently uses the routing for the viewer.

So rename getNonCompletedTicketFilters to useSetDefaultTicketFilters

Rename useViewerTicketFilterParams to useBindTicketFiltersData make it receive any param like the one from needed in the tickets table to reuse that in both places. Add any necessary logic (like the filtersInitialised) the idea is to have a hook that orchestrates how tickets filters data is fetched.

and rename
useSetDefaultTicketFilters to useViewerTicketFilterParams

[sanmont3drepo]

There can be up till 3 horizontal scrolls. The idea is that only just one should be there and if scrolling is necessary should be showing, not scrolling all the way to the bottom to scroll to the right.