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

Improve filter UX when Transaction list page is linked from Payment Activity Widget #9894

Open
jessy-p opened this issue Dec 6, 2024 · 1 comment
Labels
category: projects For any issues which are part of any project, including bugs, enhancements, etc. component: reporting Issues related to Reporting focus: reporting needs design The issue requires design input/work from a designer. priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: enhancement The issue is a request for an enhancement.

Comments

@jessy-p
Copy link
Contributor

jessy-p commented Dec 6, 2024

Describe the bug

When linking from Payment Activity widget [prerelease - not launched, enable feature flag to test], and using exact type filtering, the filters are not easily visible on the page.

Discovered while reviewing #9871 and disussed in #9871 (review)

To Reproduce

  1. Enable Payment Activity Widget and click on one of the View Report links.
  2. Observe that the Transaction list page is filtered exactly by the required transaction types but that is not obvious to the user.

Expected behavior

The transaction types selected and any advanced filters used should be displayed to the user.

Additional context

  • We cannot go back to using search box because that is not an exact search as explained in paJDYF-fT7-p2
  • There might be other issues related to timezone etc that still need fixing - paJDYF-bWn-p2#comment-27196. Will raise separate defects for those.
@jessy-p jessy-p added component: reporting Issues related to Reporting focus: reporting type: bug The issue is a confirmed bug. labels Dec 6, 2024
@haszari haszari added category: projects For any issues which are part of any project, including bugs, enhancements, etc. needs design The issue requires design input/work from a designer. priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. priority: medium The issue/PR is medium priority—non-critical functionality loss, minimal effect on usability labels Dec 8, 2024
@haszari
Copy link
Contributor

haszari commented Dec 11, 2024

Marking this as low for now, since it's not affecting users. If we revisit payment activity card we'll need to prioritise this as part of the project.

As I understand it, the problem here is that:

  • The payment activity card needs use specific kinds of filtering.
  • These filters are different from the defaults for the relevant list views.
  • AND
  • The list views don't have a UI that allows a user to perform this filtering manually, or see that it's applied.

To fix this we'd need to take another look at the overall flow (i.e. design):

  • Can we implement a more powerful filtering UI that supports what the payment activity card needs?
  • OR
  • Can we change the defaults & filter settings of the list views to better match the links from payment activity card?

I'm also switching this to an enhancement. It's manifesting as a bug, but will likely need new feature/changes to UI to resolve. The payment activity card is an enhancement, and we need to enhance the list views/filtering to make it work well.

@haszari haszari added type: enhancement The issue is a request for an enhancement. and removed type: bug The issue is a confirmed bug. priority: medium The issue/PR is medium priority—non-critical functionality loss, minimal effect on usability labels Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: projects For any issues which are part of any project, including bugs, enhancements, etc. component: reporting Issues related to Reporting focus: reporting needs design The issue requires design input/work from a designer. priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: enhancement The issue is a request for an enhancement.
Projects
None yet
Development

No branches or pull requests

2 participants