Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | |||||||||||
| 0048989 | |||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||
| design defect | [POS2] Restaurants | minor | have not tried | 2022-04-06 16:04 | 2022-04-23 21:18 | ||||||
| Reporter | Felixaka | View Status | public | ||||||||
| Assigned To | Triage Omni OMS | ||||||||||
| Priority | normal | Resolution | open | Fixed in Version | |||||||
| Status | acknowledged | Fix in branch | Fixed in SCM revision | ||||||||
| Projection | none | ETA | none | Target Version | |||||||
| OS | Any | Database | Any | Java version | |||||||
| OS Version | Database version | Ant version | |||||||||
| Product Version | SCM revision | ||||||||||
| Review Assigned To | |||||||||||
| Regression level | |||||||||||
| Regression date | |||||||||||
| Regression introduced in release | |||||||||||
| Regression introduced by commit | |||||||||||
| Triggers an Emergency Pack | No | ||||||||||
| Summary | 0048989: JIRA 2679 - Inactive Allergen stay visible on POS | ||||||||||
| Description | On FS test, when the allergen is inactive and linked to a product, we expect that it is not displayed on WEBPOS. But, it is the case. | ||||||||||
| Steps To Reproduce | . Create an allergen and uncheck the active - Link allergen to a product used on - Go to Sales POS and look for the previous product. - Add it on the receipt - See that the allergen is displayed on the receipt while it is inactive. | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0136655) cberner (developer) 2022-04-21 10:06 |
This was commented with Víctor, it seems it will not be easy to handle, as allergens are directly related with product characteristics. We've moved this issue to design defect and reasigned to Omni team. Commented by Víctor: "As you have seen, allergens are based on product characteristics. From a general POV (without allergens) whenever there is a change in a product characteristic, it is needed to run the Update Characteristic process for this product to synchronize it properly. The requirement of deactivating an allergen (or a Product Characteristic) is weird and you should clarify first the use case behind. Then we should decide, with the PM team involvement, if it is needed to implement something here, and in any case do it for the Product Characteristic directly (so allergens are also supported)." |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2022-04-06 16:04 | Felixaka | New Issue | |
| 2022-04-06 16:04 | Felixaka | Assigned To | => Retail |
| 2022-04-06 16:04 | Felixaka | Triggers an Emergency Pack | => No |
| 2022-04-20 17:12 | AugustoMauch | Assigned To | Retail => meriem_azaf |
| 2022-04-20 17:12 | AugustoMauch | Status | new => scheduled |
| 2022-04-21 10:03 | cberner | Status | scheduled => acknowledged |
| 2022-04-21 10:04 | cberner | Assigned To | meriem_azaf => Triage Omni OMS |
| 2022-04-21 10:04 | cberner | Type | defect => design defect |
| 2022-04-21 10:06 | cberner | Note Added: 0136655 | |
| 2022-04-23 21:18 | guilleaer | Summary | JIRA 2769 - Inactive Allergen stay visible on POS => JIRA 2679 - Inactive Allergen stay visible on POS |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |