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

Description PUBLIC, as decided, the sorting should be equal (the same) in all presentations Domain Order Management Bug Order Management Verified Closed Major JiraWorkItem 63574 OMT IOM Intershop Order Management 0 Pull Request 63267 Related iom/3.6.0.0

Description Actual behavior: REST API returns StatusCode 400 (Bad Request). An exception can be found in the log file as shown below. Expected behavior: Order is created in IOM. Steps to repeat: Setup IOM environment with version 3.4.3.0 Try to import order that has two or more different taxes on any

Description Description: ProcessBasket-MergeBasket throws NPE when using pipelet CreateAdHocLineItem Steps to repeat: 0. Migration from ICM 7.7.x to 7.10.30.2 1. Use pipelet'CreateAdHocLineItem (bc_requisition)' to create an AdHoc ProductLineItem for a Voucher in the basket. 2. There exists no product

Steps to Repeat Actual Behavior For both, shipping buckets and invoice addresses, when able to edit in OMT and the submitted country code is not configured at the shop, it's not pre-populated in the edit form. Domain Order Management Bug Order Management Verified Closed null Major JiraWorkItem 63522

Description API doesn't require this field and mappers are not filling it. -> must not be required in OMT. Steps to Repeat API doesn't require this field and mappers are not filling it. -> must not be required in OMT. Domain Order Management Bug Order Management New New null Minor JiraWorkItem 63521

Domain Order Management Bug Order Management New New null Minor JiraWorkItem 63520 Products IOM OMT 63521 Related 63945 References iom/3.1.0.0

Description Due to IS-30950 (starting with 7.10.30) the configuration for staging processors and decorators are gone from the staging properties. The deployment logic implemented in solrcloud_config\deployment\deploy.gradle (silently) does not work anymore. Business Impact Staging of SolrCloud Indexes

Description Description: The A/B Test Job "UpdateTrackEvents" returns an error message when MS SQL Server is used as Database. As a result, the A/B test statistics in the ICM remain empty. [2021-05-21 15:27:34.854 +0200] ERROR localhost ES3 appserver0 [] [] com.intershop.beehive.core.internal.job.JobExecutor

Description Description: Deletion of Promotion via batch process with active PromotionCodeReservation leads to Exception Please see IS-24973 Steps to repeat: Backoffice Create Promotion with Promotion Code Storefront Apply Promotion code to Basket Backoffice Disable Promotion Delete Promotion via batch

Description Actual behavior The values for "blocked" and "reserved" stock in IOM backoffice are "0" for articles that are imported into a parent shop blocked/reserved on a child shop Expected behavior Blocked/reserved stock is aggregated Note: the issue could only be reproduced for the reserved count

Description Actual behavior When creating an order via order rest API and a default ICM address model you'll get the following data in OrderAddressDO street: NULL streetName: street + houseNo houseNumber: NULL Expected behavior street is always present if streetName/houseNo are not both filled Impact