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

Ticket filters: base components #5257

Open
2 tasks
sanmont3drepo opened this issue Nov 19, 2024 · 0 comments
Open
2 tasks

Ticket filters: base components #5257

sanmont3drepo opened this issue Nov 19, 2024 · 0 comments

Comments

@sanmont3drepo
Copy link
Contributor

sanmont3drepo commented Nov 19, 2024

Description

Product issue: https://github.com/3drepo/3D-Repo-Product-Team/issues/521
For advance ticket filtering we need to be able to show the list with all the properties from the templates select one and add the filter.

In this issue we should have to tackle two components: the property selection list and the base filter form.

Property selection list The property selection list includes all the properties for all the templates for which there are tickets in the container/federation. For example if there are two templates for a teamspace, one has "height" as number, the other has "colour" as string. And the only tickets that where created for that federation/container are the one with the "height" property then "colour" will not appear on the property selection list.

The property selection list also lets the user select other elements which are not necessarily "properties" per se, these are; 'title' (string), 'ticket id' (string), 'Description'(string), 'owner' (select-list), 'Created At'(date), 'Updated At'(date), 'Status'(select-list, 'ticket template' (select-list) and 'asignees'(select-list) (TBD @carmenfan I don't see any design for user selection in filtering should we add these?) :

image

The properties within a module are depicted as 'modulename:propertyName': image

There are some properties that will not show in the property selection list. The exemptions are the properties with type image, viewpoint, imagelist, coordinates or pins.

The property selection list can be searched using the same method as most of the forms in v5.
After a filter was added to the list the property will no longer appear in the selection list as this is for adding a filter only.

Different types of properties has different icons on the left hand side; the types are string, number, date, select (a list of fixed elements, like with 'status'), and boolean. Tickets templates will show as a select list, but the icon is a bit different.
Examples:
image

Filter form (string)

The filter form shows the property name with the criteria and the values

image
This form can be triggered from two places: 1 - After selecting a property from the property selection list 2 - Clicking on a chip the bar: this will show the filter with the existing data in the filter form.

For this issue we are only focusing on string (maybe if it is too much just a base form without the criteria and value)
Filtering criteria depends on the type of property, for strings the available criterias are these:
image

After selecting the criteria and values 'apply' button will became enabled, after clicking it the form will close and the component consuming it will either add the filter to the list or change the filter that already exists.

FAQ

What happens if there are two templates with the same property name but with different types?

  • The property appears twice in the list (one for each type)

Goals

  • As a user I want to be able to see the be able to select a property for filtering custom tickets

Tasks

  • will be filled by assigned dev.

Related Resources

MockUp

@sanmont3drepo sanmont3drepo changed the title Titcket filters: base components Ticket filters: base components Nov 21, 2024
Amantini1997 added a commit that referenced this issue Nov 27, 2024
Amantini1997 added a commit that referenced this issue Nov 27, 2024
Amantini1997 added a commit that referenced this issue Nov 27, 2024
Amantini1997 added a commit that referenced this issue Nov 27, 2024
Amantini1997 added a commit that referenced this issue Nov 27, 2024
Amantini1997 added a commit that referenced this issue Nov 27, 2024
Amantini1997 added a commit that referenced this issue Nov 27, 2024
Amantini1997 added a commit that referenced this issue Nov 27, 2024
Amantini1997 added a commit that referenced this issue Nov 27, 2024
Amantini1997 added a commit that referenced this issue Nov 27, 2024
Amantini1997 added a commit that referenced this issue Nov 27, 2024
Amantini1997 added a commit that referenced this issue Nov 27, 2024
Amantini1997 added a commit that referenced this issue Nov 27, 2024
Amantini1997 added a commit that referenced this issue Nov 27, 2024
Amantini1997 added a commit that referenced this issue Nov 27, 2024
Amantini1997 added a commit that referenced this issue Nov 27, 2024
Amantini1997 added a commit that referenced this issue Nov 28, 2024
Amantini1997 added a commit that referenced this issue Nov 28, 2024
Amantini1997 added a commit that referenced this issue Nov 28, 2024
Amantini1997 added a commit that referenced this issue Nov 28, 2024
Amantini1997 added a commit that referenced this issue Nov 28, 2024
Amantini1997 added a commit that referenced this issue Nov 28, 2024
Amantini1997 added a commit that referenced this issue Nov 28, 2024
Amantini1997 added a commit that referenced this issue Nov 28, 2024
Amantini1997 added a commit that referenced this issue Nov 28, 2024
Amantini1997 added a commit that referenced this issue Nov 28, 2024
Amantini1997 added a commit that referenced this issue Dec 3, 2024
Amantini1997 added a commit that referenced this issue Dec 3, 2024
Amantini1997 added a commit that referenced this issue Dec 3, 2024
Amantini1997 added a commit that referenced this issue Dec 3, 2024
Amantini1997 added a commit that referenced this issue Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants