Description Steps to repeat: Create an order that has the following properties via the Order API 2.1: Shipping charge (or any other charge) with value > zero. The charge needs to have two or more tax lines attached to it. Both tax lines need to have a value > zero. Expected behavior The charge taxes

Description The replication on XXX live fails during restoring the XXX_prod_lvXXX-O_SE-product-search-idx-sv_SE.1 the corresponding configset does not exists. [2021-06-13 03:02:55.348 +0000] [StagingProcessThread1940384401] INFO - deleteConfigSetIfNotUsed(): Config set 'XXX_prod_lvXXX-O_SE-product-search-idx-sv_SE

Description Description: If one uses the "AddRoleChannelAssignmentPreparer" (which is calling the "RoleChannelAssignmentPreparer" internally) but don't have the "RoleChannelAssignment.properties" in the right place the following will happen: The console states that everything went ok: Console [2021-06-03

Description Description: The replication does not check for already existing catalog domain names with different DomainID on the Live system (like it will be checked for system domains). As result the DOMAIN table entries from Edit will be replicated, but not the matching DOMAININFORMATION table data

Description Current Behaviour: When net and gross prices are given in parallel it's allowed that net is larger than gross. This case is substantially wrong as gross = net + tax, where all values are never negative. Second case is the amount vs. amountDiscounted in prices as amountDiscounted = amount

Description When sending this date in comparison to an existing ocr for that order: equal -> caught by constraint older -> caught by trigger younger -> should return no error The messages for 1 and 2 are different because handled differently. Imo the constraints (in the specification) of this date should

Description current behavior The order-level promotion prices are not distributed on the orderPosDOs, but directly on the OrderPosItemDO as item price and with a rounding on cent values (no handling of possible rest amount). e.g 2.747 /2 -> 1.37 as item amount, and 1.37*2 = 2.74 although 2.747 should

Description Current Behaviour: When creating an order negative position numbers are not allowed, the creation fails with 400. But this constraint is not specified in the order-YAML. Expected Behaviour: Whether order creation with negative position numbers is allowed or the constraint is documented officially

Description Description: In the pipeline ViewCart-HandleAddProducts (app_sf_responsive) the error handling is missing. For example, if something goes wrong in ProcessBasket-AddProducts, the error is not handled correctly. Steps to repeat: see pipeline ViewCart-HandleAddProducts Node GetProductsToAdd

Description It returns the shop's name of the EXPRESS method as type of the date. Additionally the shop's name is returned as null, but should be STANDARD see test IOM-11140-202, position 2 Steps to Repeat It returns the shop's name of the EXPRESS method as type of the date. Additionally the shop's name