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

[UBS Admin Cabinet] Payment Statuses #2897

Closed
YuliyaTymkiv opened this issue Jun 16, 2021 · 0 comments
Closed

[UBS Admin Cabinet] Payment Statuses #2897

YuliyaTymkiv opened this issue Jun 16, 2021 · 0 comments

Comments

@YuliyaTymkiv
Copy link
Collaborator

YuliyaTymkiv commented Jun 16, 2021

As an administrator, I want to see the payment statuses of the order so that I can organize and manage the order.

Assumptions & Constraints
N/A

Preconditions

  1. User is logged in as administrator.
  2. The administrator navigates to the Orders tab and/or has opened an separate order from current orders view table

Business rules

  1. Only administrators with access should be able to view Admin Cabinet
  2. When changing statuses - statuses are enabled in order of succession according to the state diagram.

Acceptance Criteria

  1. All payment statuses - Не оплачено; Оплачено; Частково оплачено; Оплату повернуто - are assigned to the order automatically

  2. The system assigns the appropriate payment status based on the comparison of order total “Сума до оплати” (confirmed or actual depends on the order status) and total payment “Замовлення оплачено в розмірі”

  3. The system compares mentioned above values when:
    a. the confirmed/actual order total (depends on order status) “Сума до оплати” has been changed
    b. the total payment “Замовлення оплачено в розмірі” has been changed
    c. the order status is changed to “Сформовано”; “Виконано”

  4. The system compares confirmed order total “Сума до оплати” (column “Підтверджена к-сть”) with total payment “Замовлення оплачено в розмірі” on the following order statuses: Сформовано; Узгодження; Підтверджено; Не виконано.

Confirmed order total "Сума до оплати" Comparison (order total with total payment) Total Payment "Замовлення оплачено в розмірі" Payment status
greater than 0 > (greater) equal to 0 Не оплачено
greater than 0 = (equal) greater than 0 Оплачено
greater than 0 > (greater) greater than 0 Частково оплачено
greater than 0 < (less) greater than 0 Оплачено
equal to 0 = (equal) equal to 0 Оплачено
equal to 0 < (less) greater than 0 Оплачено
  1. The system compares actual order total “Сума до оплати” (column “Вивезена к-сть”) with total payment “Замовлення оплачено в розмірі” on the following order statuses: На маршруті; Виконано; Привезе сам; Скасовано.
Actual order total "Сума до оплати" Comparison (order total with total payment) Total Payment "Замовлення оплачено в розмірі" Payment status Comments
greater than 0 > (greater) equal to 0 Не оплачено  
greater than 0 = (equal) greater than 0 Оплачено  
greater than 0 > (greater) greater than 0 Частково оплачено  
greater than 0 < (less) greater than 0 Оплачено  
equal to 0 = (equal) equal to 0 Оплачено Applicable with order statuses На маршруті; Виконано; Привезе самApplicable with order status “Скасовано” only if overpayment return “Зарахувати на бонусний рахунок” was chosen
equal to 0 = (equal) equal to 0 Не оплачено Applicable only with order status “Скасовано”
equal to 0 = (equal) equal to 0 Оплату повернуто Applicable only with order status “Скасовано” and only if overpayment return  “Повернути кошти” was chosen
equal to 0 < (less) greater than 0 Оплачено Applicable only with order status  На маршруті; Виконано; Привезе сам;  If this case is on the order status “Скасовано”, the system shows the pop-up with following error message for 8 sec (is autoclosed when time runs out or closed by X), doesn’t allow saving changes and returns administrator to the page with updated information to choose overpayment return type : “Для збереження внесених змін, оберіть спосіб повернення коштів клієнту”

Payment states

Out of scope

Epic link
E.g.: Epic #2195

Labels to be added
"User story", Correspondind Functionality (e.g. User), Priority ("pri: "), "Corresponding Epic"

Tasks

    • sample task.
@s1auka s1auka self-assigned this Dec 4, 2021
@s1auka s1auka added this to the UI S17.2 milestone Dec 4, 2021
@s1auka s1auka modified the milestones: UI S17.2, UI S17.4 Dec 17, 2021
@ViktoriyaRyazhska ViktoriyaRyazhska moved this to Ready for testing in GreenCity Jul 1, 2024
@borntoshine1 borntoshine1 moved this from Ready for testing to Done in GreenCity Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

3 participants