Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
ISSUE #5271 - Ticket filters: jobsandusers select filter form #5391
Changes from 18 commits
7ac733d
1946be8
cda906f
a5b206b
eb0cbf9
57423aa
67a3e35
227f679
3148aff
076ffca
dcfe119
5b7c0cb
b5e2860
a95ee07
40af17d
3c96d63
e0bea9b
668afe6
9ff9d9b
7d328fc
a708671
43d44c9
a0fa774
2fe9203
0abecd0
4e7a125
4adfaf1
d213c11
b7f75d8
a061df0
8a5c185
4fa859e
b117264
da849d7
ddb7780
9d0d3bf
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
As you added the
type
"jobsAndUsers", candisplayValue
not be passed as part of the filter and be computed where needed instead?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.
The problem here is how to determine the type of a specific value in the filter chips without massively reworking how it currently is.
The chips receive the values as just an array of strings. A oneOf/manyOf can consist of multiple types (e.g. jobsAndUsers, riskCategories, custom strings). If the chips receive the values ['Santiago', 'Commercial Issue', 'BLAH'] there's no way of determining whether 'Santiago' refers to an existing user or if it's a custom string.
I suppose one way would be supplying an array of types where the indices correspond to the values, (e.g. ['user', 'riskCategory', 'custom']) but having values not explicitely tied to each other seems prone to bugs
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 don't think the Filter should be aware of the "displayValues"