creatuity/magento2-order-status-adjust

Adjust Order Status to specific one if Criteria are met

magento2-order-status-adjust's Issues

[Feature] Start and End datetime

We need to have a way to activate and deactivate rules basing on dates. Example: we might want to enable rule for one month, during which special "prize" will be added to specific orders by Employee who'll browser for Orders with special status.

AC

• Start Date optional field with datetime input is created in rule create/edit form
• End Date optional field with datetime input is created in rule create/edit form
• Start and End date are displayed on Rules Grid
• Rules executed after End Date should not be processed
• Rules executed before Start Date should not be processed
• Start and End datetime should be validated against store timezone

Unit Tests

AC

• unit tests are written and all passing

QA

We need to perform full QA of the entire module.

During QA, please refer to README.md contents: https://github.com/creatuity/magento2-order-status-adjust/blob/main/README.md

[Feature] New attributes for rules creation

We want to allow more granular way for setting order status than it is now.

We want to cover following scenario: set order status to "suspected fraud" if base_grand_total >= $1000.00, order state is "Processing" and base_total_invoiced is NULL (so no invoice was created yet).

AC

• following fields from Order entity are eligible to be used in rule conditions and are mentioned in README.md documentation
  • base_total_canceled
  • base_total_invoiced
  • base_total_paid
  • base_total_refunded
  • base_shipping_amount
  • base_shipping_canceled
  • base_shipping_invoiced
  • base_shipping_refunded

[Feature] Allow addition of new rules by other modules via XML

We want to have possibility to add new condition types to rules in a per-project way, to allow f.e. external modifications to module without overwriting core of it.

AC

• Rule mechanism is refactored to allow plugin with new rules via XML that might be added by custom modules
• it might be used on per-project basis to create special rules crafted for specific project

Planned Feature List

Planned Feature List

• Admin
  • new menu in Stores -> Settings -> Order Status Adjust Rules which will open Grid
• Admin Grid
  • columns: Rule Id, Status, Rule Name, Set Order Status, Action
• Admin Form
  • fields: Enabled, Rule Name, Condition, Action (Set Order Status)
• Rules Configurator similar to Sales Rules one
  • used in Form for creation/edit rules
• Rules based on Order
  • base_subtotal_with_discount
  • base_subtotal_total_incl_tax
  • base_subtotal
  • base_tax_amount
  • base_grand_total
  • base_discount_amount
  • base_gift_cards_amount
  • total_qty_ordered
  • weight
  • payment_method
  • shipping_method
  • order_currency_code
  • store_name/store_id
  • coupon_code
  • total_item_count
  • customer_is_guest
  • customer_group_id
  • customer_taxvat
  • remote_ip

[Feature] Order History entry for applied rule

We want to have a trace that something was automatically done to particlar Order. One way to achieve this is to add information in Order History as new entry.

AC:

• you can enable/disable (by default: enabled) adding new entry to Order History
• if any rule is applied and feature is enabled, entry in Order History is added
  • Example: "Order Status was adjusted to XYZ, applied rule ZYX