-
Notifications
You must be signed in to change notification settings - Fork 1
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
[Dataverse] Additional filters - Cross filter #230
Comments
Estimation to be done the 17th, please prepare the technical specification |
Hey team! Please add your planning poker estimate with Zenhub @0xLodz @AnjaMis @ErikssonJoakim @lolottetheclash |
Please add your planning poker estimate with Zenhub @amimart |
Please add your planning poker estimate with Zenhub @ccamel |
Note that this ticket is of high complexity, and could take over a week of dev even with peer programming |
Feature: [Dataverse] Additional filters - Cross filter
Acceptance criteria
Scenario 1 : Cross filter
Given that I am an end-user navigating the portal using a desktop
And I want to cross filter
When I select an item on a filter,
Then the selectable items in the rest of the filters must meet the criteria of the first selected item and so on
And the items that doesn't meet the criteria are hidden
When I select an item in resources
Then only the applicable filter to the resources are to be shown.
Scenario 2 : Cross Filter application in dataverse
Given that I am an end user navigating the portal on
.../dataverse
pageWhen I select a criteria in a filter
Then the system should retrieve the current resources that have that criteria in their metadata in the ontology
And the system should detect according the first filter on the metadata, the possible criteria in all the other filter that could be selected
And display only the resources on the right hand-side of
.../dataverse
pageAnd the UI will hide the non-corresponding criteria as in #196 (comment)
Environment
Additional informations
None.
┆Issue is synchronized with this Wrike task by Unito
The text was updated successfully, but these errors were encountered: