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

Implement Filters on Contracts Page #589

Open
2 of 3 tasks
Tracked by #592
AbdullahMuk opened this issue Jan 3, 2024 · 1 comment
Open
2 of 3 tasks
Tracked by #592

Implement Filters on Contracts Page #589

AbdullahMuk opened this issue Jan 3, 2024 · 1 comment
Assignees
Labels
component/edc-ui affected software component goal/improve-caas-usability improves the UX and usability of sovity products kind/enhancement New feature or request kind/epic Epic which groups several user stories task/ui-ux Requires UI/UX input. Create a Mock-up / Low Fidelity Prototype.

Comments

@AbdullahMuk
Copy link
Collaborator

AbdullahMuk commented Jan 3, 2024

Feature Request

Description

As a user who is using the Contracts page,
I want to be able to filter search results,
So that I can find the most relevant information quickly and efficiently.

Which Areas Would Be Affected?

  • edc-ui > Contracts Page

How does this tie into our current product?

This request aims at improving the user experience around contract management as an attempt to increase user satisfaction.

Requirements

to be aligned with @simritbhatia:

  • Make tags filter-friendly @AbdullahMuk what exactly do you mean by this?
  • Direction (Providing, Consuming)
  • Validity (Valid, Expired)
  • Language (English, German...)
  • Contract Policy (not sure yet what this could entail)
  • Content Type (JSON, DT...)
  • Date (filter by year & month)

Acceptance Criteria

  1. When I perform a search, I should see an option to apply filters to my search results.
  2. I should be able to select one or multiple filters from a list of predefined filter options.
  3. After selecting a filter, the page should refresh and display only the search results that match the selected filter(s).
  4. I should have an option to clear all applied filters and reset the search results to their original state.
  5. The system should remember my filter selections during a session, even if I navigate away from the page and return later.

Solution Proposal and Work Breakdown

@simritbhatia and Julian K. to define.

Tasks

  1. goal/improve-caas-usability task/ui-ux
    simritbhatia
  2. 0 of 2
    component/edc-ui goal/improve-caas-usability status/blocked
    kulgg
  3. 0 of 4
    kind/enhancement scope/ce
    ununhexium
@AbdullahMuk AbdullahMuk changed the title Implement Additional Filters on Contracts Page Implement Filters on Contracts Page Jan 3, 2024
@AbdullahMuk AbdullahMuk added the kind/epic Epic which groups several user stories label Jan 4, 2024
@AbdullahMuk
Copy link
Collaborator Author

@simritbhatia regarding "Make tags filter-friendly", proposal: when user clicks on these tags the UI should update to only show the matching cards.

Image

@AbdullahMuk AbdullahMuk added goal/improve-caas-usability improves the UX and usability of sovity products and removed goal/improve-user-satisfaction labels Jan 9, 2024
@simritbhatia simritbhatia added the task/ui-ux Requires UI/UX input. Create a Mock-up / Low Fidelity Prototype. label Jan 17, 2024
@AbdullahMuk AbdullahMuk added the clean-backlog requires backlog cleaning label May 2, 2024
@AbdullahMuk AbdullahMuk added the component/edc-ui affected software component label Sep 2, 2024
@SebastianOpriel SebastianOpriel removed the clean-backlog requires backlog cleaning label Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/edc-ui affected software component goal/improve-caas-usability improves the UX and usability of sovity products kind/enhancement New feature or request kind/epic Epic which groups several user stories task/ui-ux Requires UI/UX input. Create a Mock-up / Low Fidelity Prototype.
Projects
None yet
Development

No branches or pull requests

4 participants