Skip to content

Avoid using a "N/A" as fee value on the Transactions listing #8286

New issue
New issue
Open
#8640
Open
Avoid using a "N/A" as fee value on the Transactions listing#8286
#8640

Description

@kalessil

kalessil
openedon Feb 28, 2024

Describe the bug

When the transaction fee is 0, the transaction listing page displays it as N/A instead of the expected number (the transaction details page handles the case correctly).

To Reproduce

  • Using a US merchant, assign wcpay-discount-100-off and refresh the client cache
  • Perform a test purchase (any payment method)
  • Check the transactions listing page and compare it to transaction details page

Screenshots

Screenshot from 2024-02-28 14-16-57

Screenshot from 2024-02-28 14-20-45

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    component: application feesIssues related to collecting feescomponent: transactionsIssues related to Transactionsfocus: payments acceptance & processinggood first issueThe issue is a good candidate for the first community contribution/for a newcomer to the team.needs prioritisationTriage finished and issues are ready for the following processing.type: bugThe issue is a confirmed bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions