Sort / Filter / Search for advisories

helhum / TYPO3.IHS

Incident Handling System

4 stars 0 forks source link

Sort / Filter / Search for advisories #2

Closed t3sec closed 9 years ago

skurfuerst commented 10 years ago

I could imagine that this is based on a textfield with advanced conditions; like it is possible in Gerrit or Github.

Possible implementations:

http://documentcloud.github.io/visualsearch/ (maybe also alternatives)

helhum commented 10 years ago

something like visualsearch would be great, yes.

mberhorst commented 9 years ago

I got a question. I have a field named "vulnerability type" for issues. Currently that is a text-field. I could imagine that this field should be a dropdown or something in the future. Because I could create a facet for this field and it would be great to know how this field is handled in the future. Depending on that I have different implementations in mind for creating this facet.

Maybe we can discuss this tomorrow and my solution for this issue.

helhum commented 9 years ago

vulnerability type is a text field, yes. but it should act like a value object with one property (name) This means we can add new vulnerability types by adding a new name (which does not exist before) We could transform it to a real value object, if it helps to pre-fill the facet and add auto-suggest in edit view (instead of grouping all issues by vulnerability type and fetching the type field)