Skip to content

Review to Terminate UI Page #1438

Description

@ZenGround0

From #1352

  • Show every dataset currently requiring review.
  • Do not apply a profitability or alert-volume threshold in the first version.
  • Show the reason the dataset requires review.
  • Show when the condition began and how much review time remains.
  • Show revenue earned so far by the dataset, including settled and one-time payments.
  • Show projected future revenue for the dataset based on the applicable service rate.
  • Allow the SP to sort the review queue by:
  • Revenue earned so far.
  • Projected future revenue.
  • Identify the customer associated with the dataset.
  • Show the broader value of the customer's relationship with the SP, including:
  • The customer's total number of active datasets or services with the SP.
  • Total revenue earned across the customer's datasets or services.
  • Total projected future revenue across the customer's datasets or services.
  • Aggregate recurring or annualized revenue, where applicable.
  • Clearly distinguish the value of the dataset under review from the aggregate value of the customer's portfolio.
  • Allow the SP to inspect the customer's other datasets or services before terminating the affected dataset.
  • Link to relevant proving, retention, task, payment, customer, and service information.
  • Provide a deliberate, confirmed Terminate service action.
  • Present the customer-level context as part of the termination confirmation so that the dataset is not evaluated in isolation.
  • Clearly distinguish manual termination, scheduled automatic termination, recovery, and completed termination.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    • Status
      🐱 Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions