-
Notifications
You must be signed in to change notification settings - Fork 40
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
ISSUE #5271 - Ticket filters: jobsandusers select filter form #5391
Conversation
…ists within select already
.../v5/ui/components/viewer/cards/cardFilters/filtersSelection/tickets/ticketFilters.helpers.ts
Outdated
Show resolved
Hide resolved
frontend/src/v5/ui/components/viewer/cards/cardFilters/filterForm/filterForm.component.tsx
Show resolved
Hide resolved
.../v5/ui/components/viewer/cards/cardFilters/filtersSelection/tickets/ticketFilters.helpers.ts
Outdated
Show resolved
Hide resolved
frontend/src/v5/ui/controls/assigneesSelect/assigneesSelect.component.tsx
Outdated
Show resolved
Hide resolved
frontend/src/v5/ui/controls/assigneesSelect/assigneesSelect.component.tsx
Outdated
Show resolved
Hide resolved
...mponents/viewer/cards/cardFilters/filterForm/filterFormValues/filterFormValues.component.tsx
Outdated
Show resolved
Hide resolved
… exist on tickets within the model
…y don't have a displayValue
...end/src/v5/ui/controls/assigneesSelect/assigneesSelectMenu/assigneesSelectMenu.component.tsx
Outdated
Show resolved
Hide resolved
.../v5/ui/components/viewer/cards/cardFilters/filtersSelection/tickets/ticketFilters.helpers.ts
Outdated
Show resolved
Hide resolved
/> | ||
<FormHelperText>{helperText}</FormHelperText> | ||
</FormControl> | ||
export const MultiSelect = ({ defaultValue = [], className, ...props }: SelectProps) => ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In src\v5\ui\routes\viewer\tickets\ticketsForm\properties\manyOfProperty.component.tsx
this component is being used.
manyOfProperty shows a different component depending on the values
prop . These components are all FormInputs and the change here changes that.
maybe you should change that reference to FormMultiSelect to keep the same logic?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I followed the code a little bit more and its using src\v5\ui\controls\searchSelect\searchSelect.component.tsx
which uses src\v5\ui\controls\inputs\select\select.component.tsx
which in turn uses formcontrol.
Created an issue #5448 to address this, so this comment dont need to be addressed.
…tor for a property type
This fixes #5271
Description
Adds the jobs and users circles input for when a value is solely jobs and users
If the property has jobsAndUsers and in addition to other values then the usual select will display.
Users will always be shown as their full name - not their username.
The owner property uses the jobs and users circle select
Test cases
Test out the 'Owner property'
Create templates that have a shared property path (module, property, and type are the same) but with different values one of which is jobs and Users